I have already read it some time ago: Compilation fails when you link the same external event to multiple scenes, and I can reproduce it, but I’m pretty sure it was already fixed in the past, maybe it’s a regression… It’s a C++ error in the GD events engine core, so we’ll have to wait for @victor or @4ian
I posted several logs about this kind of bugs : i had a critical one in 4.0.92, it’s corrected in 4.0.94 but i face a new one.
To keep going working : just dont use external event for now, or just use them and link them at the end before compiling an external executable. Only the scene editor crash from my own experience.
I was opening a new issue on GitHub, making sure the problem was native related only, when the bug magically disappeared and everything was working correctly , the only change I made had to be the cause: empty external events.
Checking the issues list again found that this issue is already open https://github.com/4ian/GD/issues/166, so avoid to use empty external events and everything should go well
Have you tried the “Events Groups”? I used to do the same as you (I have some old tests with this format I think) until groups where added, I mean, they where made for it and are very handy
I’m not 100% sure what happened, but while I was using the physics 2.0 behavior, it came up with this red warning that said it was missing something in my code called Box2D. I wasn’t using JavaScript, and just visual scripting, but I would love to know if this is my fault, and how to fix it.
Hi, please don’t resurrect old posts (this one is last posted to 8 years ago), especially if your post is unrelated to the old thread. Start a new thread instead.