Open iamgreaser opened 3 years ago
Thanks for your report.
This doesn't appear to have anything to do with the Debug Line Node but rather the Global Transform Node. Which the log snippet correlates.
Please submit entire log files too, we need information that occurs elsewhere in the log file to fully diagnose your issue.
Pinning down exactly where the bug "should be" is a somewhat difficult philosophical issue, and the bug may actually be that you can store a slot in a dynvar, then delete it, and the dynvar still points to the deleted slot which now no longer tracks back to Root.
I'll get you a suitable log the next time I'm on Neos.
Another screenshot:
The object that it's referring to was set up by dragging its reference into the EmptyObject inspector, and the object itself was deleted with the red trash can in its own inspector.
Logs:
...and apparently GitHub doesn't support 7zip.
There's an Updating Relay there, so sorry for the sheer amount of spam in the log.
Describe the bug?
OK, there's an interesting chain of events here and no title for this issue would be particularly good.
Relevant issues
2219 covers various cases where error output nodes show up.
To Reproduce
See the screenshot for more details.
The chain that I'm going for is this:
Once you have this set up, delete the relevant slot. The Timer node will go red.
A workaround for this is to check to see if the slot's parent is not null. This workaround is visible in the screenshot.
Expected behavior
Two things.
Log Files
Here's the relevant backtrace. It comes from the log file that isn't
Player.log
.Screenshots
Exact case with workaround applied:
How often does it happen?
Always
Does the bug persist after restarting Neos?
Yes
Neos Version Number
2021.10.21.64
What Platforms does this occur on?
Linux
Link to Reproduction Item/World
No response
Did this work before?
I Don't Know
If it worked before, on which build?
No response
Additional context
No response
Reporters
GreaseMonkey.