I am developing a game where I switch between different objects: exploration objects during normal gameplay, and combat-specific objects by using an “object change” mechanic during battles. Each object contains a large number of actions and animations, so I wanted to distribute the processing load.
Until version 1.42, this switching mechanism worked fine, but since version 2.00, it has consistently caused crashes. The same issue occurs in both versions 2.04 and 2.05.
The system works correctly when I specify a relatively lightweight object as the target for the switch.
Could you please make it possible to switch back to heavy objects as it used to work before?
If needed, I can send you the project files.
Thank you very much for your assistance.
Addendum:
In the editor’s test play mode, the crash is reproducible every time. However, in the built version, it runs normally once every few attempts. Additionally, in the built version, the application always crashes when moving to another scene via a portal. This does not happen in the editor’s test play mode.
This situation makes it impossible to enjoy the game even after completion, which is quite troubling.
Thanks for the report! A crash definitely shouldn’t happen, especially since this worked in 1.4.2. Could you send your project to pgmmv-support@gotchagotcha.jp so we can look into it? It would help to include which scene to start in and what triggers the Change Object, and the same for the portal crash in the build.
In the meantime, what if you tried Generate Object for the battle object and then Remove Self on the exploration object in the next state, instead of Change Object?
Thank you. I have sent the file along with a description of the process leading up to the crash.
Since then, I made various adjustments, and for some reason, the crashes in the portal no longer occur. I apologize for not being able to identify the cause. Please let me know if the issue recurs with the portal.
Regarding your alternative suggestion: after “Object Creation,” add “Delete Self.” It seems like the frequency of crashes has decreased slightly, but they still happen with a high probability.
Also, this is unrelated to the crashes, but sometimes the custom action “Initialize Specified Property” that I created before the v2.00 update does not work properly. It seems to resolve itself upon restarting, so the condition is unclear, but it is also quite troublesome.
Thanks for sending the project! I followed your steps in the editor on 2.0.5 and couldn’t get it to crash. ザンカ探索 changed into ザンカ and I was able to finish the fight. I tried it a couple of times.
Since it crashes on your PC, could you send the log from right after a crash? Paste %APPDATA%\Agm\app_userdata\チュートリアル2\logs into the File Explorer address bar and send the newest godot.log file. I’m hoping it shows where the crash happens.
The Windows Event Viewer entry would help too. Open Event Viewer (イベント ビューアー), go to Windows Logs (Windows ログ) and then Application (アプリケーション), and look for an Error from “Application Error” at the time of the crash. A screenshot of that is perfect. Your PC specs (CPU, graphics card, and RAM) would also help.
For Initialize Object Property, which object and state is it in, and which value doesn’t reset when it fails?
Thank you for checking. I’m still experiencing crashes in my environment, so I have attached the log from when it occurred, a screenshot from Event Viewer, and details about my PC environment.
The “Initialize specified properties” feature didn’t work for the switch “Guard” located at the beginning of the “Neutral” state of the object “GreenOni0”. Depending on the scene, the initialization failed to work for this switch. Currently, I’ve added a separate action to turn off the “Guard” switch (default is off) in addition to initialization, which resolves the issue. However, if I disable this extra action, the initialization sometimes fails again. The failure occurs in the “Forest Battle 1” scene, where multiple instances of “GreenOni0” appear, whereas it works fine in “Forest Battle 2”, where only a single instance appears. This could possibly be due to some configuration error on my end; if so, I apologize.
Thanks for sending the logs! They show the crash happening at the same spot on both of your PCs, but I still can’t get it to crash on mine. Version 2.1.0 came out on November 4, so could you update and try the Change Object again? If it still crashes, please send the newest godot.log from the same folder.
For Initialize Object Property, I was able to confirm the bug and have reported it. When a scene has several copies of the same object, setting the target to itself only resets the oldest copy, so the other 緑鬼0 keep ガード on. That’s why it works in 森バトル2 with just one 緑鬼0. I’d keep using the action you added that turns ガード off directly until it’s fixed.