Please don't add features before you get the existing features fleshed out. As @Severin already said - slow down, perfect, and have patience.
Please don't add features before you get the existing features fleshed out. As @Severin already said - slow down, perfect, and have patience.
Bug fixes and BETA TESTING lighting rigs.
Renamed project
camera_and_lighting_rigs.py
@Severin I have an addon which turns non-manifold geometry in to manifold and then execute boolean operation, this is where I use "Make Normals Consisten" operator, so in my case I cannot manually check each object for bad normals.
Automatic tries to select best choice based on detected hardware and known GPUs that are failing for a given method, but it cannot be perfect, esp. when each new driver version may change things.
@Severin this is not the issue here. The question is, that algo is supposed to recompute normals outside, and in this case it fails.
@alm, even though I agree with Bastien that this could/should be improved, I think you can get the desired result by doing the normal correction on each mesh island separately, so you select one by mouse hovering it and pressing L, correct normals, then the same with the other one. You can then use the "Inside" option for the one that doesn't look correct. For me this seems to work fine.
As discussed with @gaiaclary , merged writePhong and writeConstant to write_phong_or_constant,
and shifted the bool is_shadeless up one Level
Ok just tried that, it was set at automatic.
I think thats default ?.
When manualy set to "openGL oclusion queries", it does not happen.
In the other mode it crashes blender. ..
Related, a crash in the following deprecated scene, when toggling from Edit mode to Object mode, seems to cause a crash with Boolean modifier (depending on selection on not).
@brita_ I was just making a point to @sybern's statement about the bounding box changes shapes. I didn't need this for my specific scenario
@razvanc87 I would also programatically do a grid and place scaled objects there. So all good..
as to have to update the dimensions every frame, are your hexagons changing? It is totally scenario dependent.
I'll get this in when we're back at bcon1 (I was without internet before, sorry about that).
Closed by commit rB2058505da4e5.
Confirmed, this happens for the Curl and Wave modes. Probably similar to roughness issues we had in the gooseberry branch: Kink/roughness/blah features must only depend on ORCO coordinates of the child/parent, otherwise any deformation or transform of the object leads to a change in hair shape.
Did you try changing the select method in UserPreferences, System tab, and see whether one of the two do not crash?