You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is easily reproducible, if you add an empty to a scene, and have it instance a collection using LOD , it fails to update the instance when you pull the camera back causing Blender to crash.
If the collection being "instanced" is visible in the scene, then this crash does not occur.
Please see the below Blender file, if you hit Ctrl + F and fly the camera backwards, Blender crashes. You make "Collection 2" in the example file visible, then the crash does not occur.
*Note on Workaround
I have been working around the issue, and keeping all my collections visible, however I now suspect this is causing crashes to happen at runtime. Specifically if the active camera is near an instanced collection and the collection is on an inactive layer or its visibility is culled.
Thank you!!! <3
The text was updated successfully, but these errors were encountered:
It is easily reproducible, if you add an empty to a scene, and have it instance a collection using LOD , it fails to update the instance when you pull the camera back causing Blender to crash.
If the collection being "instanced" is visible in the scene, then this crash does not occur.
Please see the below Blender file, if you hit Ctrl + F and fly the camera backwards, Blender crashes. You make "Collection 2" in the example file visible, then the crash does not occur.
Collection_Crash.zip
*Note on Workaround
I have been working around the issue, and keeping all my collections visible, however I now suspect this is causing crashes to happen at runtime. Specifically if the active camera is near an instanced collection and the collection is on an inactive layer or its visibility is culled.
Thank you!!! <3
The text was updated successfully, but these errors were encountered: