Why are there new errors after exporting the project ?

Inces

I exported my game to Windows Desktop, and it crashes or freezes at times it never did before. At that moments I'm getting errors, that I haven't seen while playing it in the editor. For example : No loader found for resource: res://pawns/pawnwack.png. At: core/io/resource_loader.cpp:285 SCRIPT ERROR: builder.unload: Invalid get index 'Mossi' (on base: 'Nil'). At: res://scripts/builder.gdc:140 SCRIPT ERROR: builder.initiate: First argument of yield() not of type object. At: res://scripts/builder.gdc:81

How is this possible ? Are there any differences in code compilation in exe or something ? I suspect exe no longer tolerates upper/lower case string differences, while editor let it go ? Are there more ? It looks like my JSONS sheets were not parsed correctly in exe. How can I simulate exe situation in editor so I can debug it effitiently ?

TwistedTwigleg

Welcome to the forums @Inces!

My guess is that the file loader isn't seeing the files, specifically an image file in the case of the error above. One thing that may be causing the issue is that the image file path has an extra . after png, which could be causing the issue.

I'd also recommend checking to make sure the filename is written exactly the same in both the Godot project and the JSON/Code, just to make sure they are the same. I know that sometimes Windows can have issues with file pathes whose case (uppercase/lowercase) is different than the file itself. I'm not sure if that is the issue here, but it may be something to look at.

I'm not sure if there is a way to have the editor play in release/export mode, but you can try exporting the game and then running it in the console, then it may print errors to the console that help indicate what is going on.

Inces

Thank You for fast answer :)

I really freaked out, because I expected exe to work just as good as in the game in editor, I never knew new errors can occure due to exporting. That wasn't in all the tutorial back there.

I had some misspelling with those pngs, I was able to fix this part easily. However JSON file throws error in parsing in very first line in debug console in exe. It looks like it is not mistake in spelling its indexes, they seem to be the same everywhere, path to its file is also identical. This is very first error I get in exe : ERROR: File must be opened before use. At: core/bind/core_bind.cpp:2023 ERROR: parse: Error parsing JSON at line 0: At: core/bind/core_bind.cpp:3220

I am really lost here, since I don't recognize these paths, core ? bind ? I can see some options revolving binaries or filters of JSON files in the export tab of editor , is this connected to it, should I change something there ?

Next error is about yield argument not being of type object. I can understand that, since I cheated yield function making it object by yielding inside on short timer. Still it worries me that editor let it go before and that it will require ridicolous amount of time to find all of the new bugs.

Inces

I found it at last, It was about those filters after all ! I added *.json to filters and all of the errors went away, even those seemingly unrelated !! :)

TwistedTwigleg

Awesome! I'm glad you were able to figure out the issue :smile: (Sorry about the delay in replying, have been really busy as of late)