- User Since
- Jan 3 2003, 6:23 PM (841 w, 5 d)
This is a known limitation, the subsurf modifier has to use the same viewport and render levels when used before a cloth modifier. If you need to have extra subdivision for render it should be done after the cloth modifier.
The volume density that the task above refers to so far is for shaders, and there it is an attenuation coefficient with unit 1/m. There may be other settings in the smoke simulation that need different units, that would need to be figured out property by property. There may be one that has unit kg/m³, or maybe the density is specified indirectly through other properties.
As far as I'm aware, this bug was already fixed in the latest versions.
We indeed follow the monitor V-Sync, by design.
For commits like this, please use the Cleanup: prefix.
Please test the latest daily build to see if it has been fixed already:
The default behavior was changed, you have to go to the Material properties > Settings and change the Displacement Method.
Thanks for the report, but note the reporting guidelines, this is outside the scope of the bug tracker:
The main thing for the units is for them to be convenient to users, if they can be SI units even better but I don't think it's a hard requirement.
Thanks for testing, let's consider this resolved then.
I'm going to assume this all these recent macOS bugs are about the same issue.
There's a new build, the previous one was from 5 days ago:
I wasn't able to confirm this myself, but marking as high priority.
Closing due to missing information to investigate the problem, can be reopened if that is provided.
Seems fine, just minor comment.
Ok, thanks for testing, will consider this resolved for now then. Transparent shadows indeed are tricky for realtime rendering.
Agree, modal handlers were never meant to be used from execute, it's for use together with invoke.
This will crash if there is no local scene with rigid body settings, since BKE_rigidbody_remove_object assumes the scene is not NULL.
I don't think it was solved for the report author.
Different issue than the one I fixed, but we already have a report for this one.