Exporting a project with the option `Convert Text resources to binary on export` causes undefined behavior

[HungryProton]

Different issues happen depending on the Godot engine version, but only when Convert Text resources to binary on export is enabled.

• On 3.4-beta4: exporting a project with this option causes either missing textures or missing models on the geometry handled by a scatter node.
• On 3.3.1 stable: the export process crashes before the end.

[MJacred]

This is just a hunch stemming from my experience with modular mesh assembly, but Godot probably thinks those resources (model / texture) are not needed and thus does not export it or it's only accessible by finding the file in the .import folder, where it received some obscure file suffix

Might be a bug with Godot and its thoughts about export optimization or some logic that eludes me

[HungryProton]

That's good to know! Thanks for the lead, I'll investigate it

[basdp]

Had this same issue. Got a lot of these messages when exporting:

 Another resource is loaded from path 'res://dummy0' (possible cyclic resource inclusion).
 Another resource is loaded from path 'res://dummy1' (possible cyclic resource inclusion).
 Another resource is loaded from path 'res://dummy4' (possible cyclic resource inclusion).
 Resource was not pre cached for the resource section, most likely due to circular reference.
 Resource was not pre cached for the resource section, most likely due to circular reference.
 Resource was not pre cached for the resource section, most likely due to circular reference.
 Resource was not pre cached for the resource section, most likely due to circular reference.
 Resource was not pre cached for the resource section, most likely due to circular reference.
 Resource was not pre cached for the resource section, most likely due to circular reference.

Issue was solved (or rather worked around) by disabling Convert Text resources to binary on export.