Encountered a test window crash issue while creating an object. Here’s the setup causing the problem:
Object’s BaseSettings Configuration
Activation condition in node: Enable when approached
Respawn condition after disappearance: Respawn when 30+ units beyond the camera
Issue Details
When approaching the object to enable it, the object spawns with state actions: ① Change variable ② Wait 1 second ③ Self-delete
The test project crashes immediately after, with no error message.
Workaround
Changing the respawn condition to “on scene switch” fixes the issue, and the object functions normally on re-approach.
Has anyone experienced a similar crash or have insights on what might be causing this? Any help is appreciated!
Justus
June 26, 2025, 3:30am
2
Is there a minimal project that can reproduce the issue?
Found the issue: the absence of an objectRoot node prevents the game object (act node) from functioning, causing the app to crash.
Justus
July 17, 2025, 12:29pm
4
If it inevitably causes a crash, it should be considered a bug. Can you create a minimal reproduction project?
Justus
July 18, 2025, 11:28am
6
It can be confirmed that a crash occurs after waiting for a few seconds after running. This bug has been reported.
Justus
July 22, 2025, 9:13am
7
The crash issue no longer seems to occur after version 1.0.14. Please verify this.
Yes, meow. Now it only requires the papa2d parallax node to generate and respawn away from the camera, including respawning under a parent object in the scene.