Skip to content

Troubleshooting

Tony edited this page Sep 28, 2023 · 8 revisions

This is a page dedicated to known troubleshooting and workarounds. This may be updated occasionally as I figure out solutions, in the future.

Disclaimer: I Am Not Your Tech Support

Game developers like you and me are not sysadmins, engineers, or tech support! While I can test and offer Godot-related solutions in Windows, I cannot provide technical support advice. The software is provided as-is, and by using the software you agree that I am not liable for issues (see the LICENSE files for details). I can recommend general stuff like "hey contact Microsoft Support for help updating your operating system" or "contact the graphics driver manufacturing company for help updating your graphics drivers." But I will never suggest that you "wing it" in your DNS, System32, registry, etc. Performing actions in those areas can cause huge computer issues, so I will always advise seeking a qualified professional to help you make those changes.

Crash or Softlock Related Issues

4.0.2 Softlock

Issue: When I downloaded the game template for the first time, Godot stalled out and a second window that opened stalled out, too. What happened?

Solution: I reproduced this issue in Godot 4.0.2 in the main branch. I believe that it has something to do with import files and other files from the .godot folder that automatically generates as you work on a project. Because we no longer include files from the .godot folder in our project, they need to be regenerated. Godot 4.0.2 seems to softlock (either permanently or for much longer than I'm willing to wait) while generating these files. This issue does not occur in 4.1.1, however. What seemed to work for me is force exiting the application, launching Godot again, and reopening the project. This should resolve the crashing issue. Because of this crash issue, I intend to move the project to 4.1.1.

Known Error Related Issues

4.1.1: Condition "!named_globals.has(p_name)" is true

Issue: When I enabled the plugins, I received the following error: Condition "!named_globals.has(p_name)" is true. When I enable the GDDialog plugin, the Dialog Records button does not appear in the bottom bar.

Solution: In Godot 4.1.1 (and also Godot 4.0.2), this is another issue that, according to some users, seems to be caused by missing files from the .godot folder (because they are not included). After opening the project for the first time, the files should be generated by now. Go to Project > Quit to Project List and then reopen the project. The errors should stop appearing, at that point. Until I find a way to prevent this issue from occurring, this is the offered workaround.

Download Related Issues

4.0.2+: No Dialog Records Back Button

Issue: When I edit a record, there is no back button icon in the top left corner. I can locate the button, but the icon is not properly displayed.

Solution: This occurred on exactly one device, so I think this is a one-off case, but just in case, I recommend downloading the project again and reopening it.

Clone this wiki locally