Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UPBGE 0.4.1: instances of Collections that use "LOD"cause crash. #1865

Open
Feral3d opened this issue Dec 3, 2023 · 0 comments
Open

UPBGE 0.4.1: instances of Collections that use "LOD"cause crash. #1865

Feral3d opened this issue Dec 3, 2023 · 0 comments

Comments

@Feral3d
Copy link

Feral3d commented Dec 3, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant