max1mum_d3ath

joined 1 year ago
[–] [email protected] 1 points 1 year ago

I ended up resolving this by manually editing the scene files and removing references to PackedScenes in certain scripts. I had seen mention of 4.x having issues with cyclically referenced scenes, so that's likely the issue.

[–] [email protected] 1 points 1 year ago (15 children)

Were you hoping for the acquisition to be denied? I'm curious to hear if/why people think this going through will be bad.

[–] [email protected] 2 points 1 year ago (1 children)

It shouldn't be too difficult to redo, especially if I use the original tscn content for reference. It's the main menu UI and the only error I saw was related to textures I'm using for the buttons. I have a sneaking suspicion that it could be the TextureAtlas I created for the UI. I hadn't thought of launching from command line, that's a good idea!

[–] [email protected] 1 points 1 year ago

For further context, I am using git and the only change that happens after the upgrade is a string changed from 4.0->4.1 in the project file.

 

I have a simple GUI app I made in 4.0.3 and I have tried upgrading it to 4.1 but there always seems to be a scene that it says is corrupted. I have tried the upgrade a couple times and there's always one scene that doesn't work but the others will sometimes work and sometimes not.

Fixes I've tried:

  • Deleting .godot directory before upgrading/re-importing
  • Manually removing references to external resources that caused errors (textures) in the scene file
  • Re-importing textures

Any other ideas would be appreciated. It's not detrimental but I'd really like to make use of the exported Arrays of custom types.