Hi Dorian,
Congratulations on a fantastic update.
I’ve come across an issue, the camera frustum culling doesn’t work if the camera uses a trackTo constraint. The cause is your use of active_cam.rotation_euler in update_factory.py (lines 1839, 1859, 1880 and 1899). It returns the cameras rotation ignoring the constraint.
These need to be replaced with:
rotmode = active_cam.rotation_mode
order = rotmode if rotmode not in {'QUATERNION', 'AXIS_ANGLE'} else 'XYZ' # 'XYZ' would be default
ng.nodes["rotation"].vector = active_cam.matrix_world.to_euler(order)
I’ve come across an issue, the camera frustum culling doesn’t work if the camera uses a trackTo constraint.
Thanks a lot for the report and for the quick fix ( altho it is supposed to be my part of the job tho ) I’ve pushed it to master, and will do few more tests, the fix should be available for 5.1 release
*edit: issue is more generic than this, parenting was not supported.
Hello
Thanks for the report
Could you please give me an example file? Are you using botaniq perhaps?
It is likely that this issue is not from our plugin, we do not change anything shader-related and geometry node is not supposed to change this data, an example file would be welcome.
Btw, please avoid doing bug-report at two places at once
There is some strange error in Scatter 5. I can’t see any system added to scene. It works only when I create new project. Looks like some strange settings are stored in my project. Please help!
The guys at botaniq are using the object display color ( from object info node ) as a major factor driving their leaves shaders. The problem is that display color is not necessarily an accurate representation of the final render color. ( that’s what is leading to our issue, in Scatter5 display colors are for viewport viz)
If you need to change the trees shader color, you will need to change the system display color as demonstrated in the gif below
It is a either a new feature for botaniq users or an annoyances depending on your view
I have found some other issue - this what I see in Viewport Shading is different to this what I can see at Rendered Viewport (Cycles) Scater 5 - Viewport difference - YouTube
It looks like a subdivision issue, do you have a painted vertex-group and a subsurf modifier on your terrain activated only during render time? Blender vertex-group and subdivision will cause this, (this is not linked with the plugin)
if not, please send me a file sample via DM,
If you encounter more personal issues please use DM instead of the public space forum
D, sadly Link Imports is not working. The biome stuff is not linked at all, and thus my .blend files are f**king gigantic. Will this feature be working soon? I desperately want to be able to use Scatter without having .blend files that greedily scarf down the 500GB of my NVMe jobs drive…
Just tested, it’s working fine with me, both biomes and asset browser scattering.
What’s your OS? Did you tried from a fresh new .blend with no imported objects already?
) I’ve pushed it to master, and will do few more tests, the fix should be available for 5.1 release
