I recently discovered that a project of mine was causing blender to crash to desktop without any error message when moving in and out of its main menu scene, the apparent reason being the ‘enemy’ object. Upon reflection, I had noticed it being referenced in “Zombie Object” warnings on the console when debugging.
Thinking this was the problem, I sifted through the forum a bit, and found out that the warning is standard when an object with a debug property is deleted. Sounds all good and well, and rather easy to fix, but…
- The object causing the trouble has no properties marked for debug (no objects do),
- No object in the scene experiences deletion during testing,
- The warning appears even when the ‘enemy’ object remains on a hidden layer, and
- Zombie Object warnings are said to have no effect on performance or stability, yet seem to have at least some correlation to the crash-to-desktop event.
Perhaps I have not grasped the full definition of the “Zombie Object” warning, but I can’t see any way in which this object is causing this much fuss. The only current workaround is deleting one cross-object actuator that the enemy needs to operate.
Any tips on how to diagnose or fix the aforementioned, or create a workaround, would be appreciated. I plan to upload a demo soon.
Edit: Okay, here’s the file: TGTEAGs_Iteration3.blend (1.53 MB)