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.

  • Ste@programming.devEnglish
    2·
    1 year ago

    I didn’t have issues upgrading from 4.0 to 4.1. the only small problem was the one related to the textures that I then find out I just needed to delete the .godot folder to fix it

  • laenurd@lemmy.lemist.deEnglish
    2·
    1 year ago

    Back when 4.0 was still in development, I regularly compiled the latest version to test new features etc. on a rather large project. There were many more breaking changes back then than there are from 4.0 to 4.1.

    What nearly always helped with import or scene corruption errors was deleting the “.godot” folder in the project, which makes it re-import everything.

    You should back up everything before though.

  • simple@lemmy.worldEnglish
    2·
    1 year ago

    I had no issues upgrading to 4.1, not sure why it doesn’t work for you. Try upgrading to 4.1 on another device if you have one and upload to git, otherwise wait for the next hotfix and hope they fixed it.

    Also would be great if you can create an issue on github in case this isn’t a known issue

  • NocturnalMorning@lemmy.worldEnglish
    1·
    1 year ago

    I stopped using Godot 4 bcz they weren’t taking feedback seriously about how cavalier they are with API changes constantly occuring.

  • russ@programming.devEnglish
    1·
    1 year ago

    I upgraded without issues… i wonder what kind of scenes these are that aren’t working.

    I’d expect manually editing the tscn files could fix it, but wouldn’t know what to change without more info. Is there any detail/errors on why they are corrupted? Sometimes i launch godot on the command line to try to see more error info from the logs/output, tho the same should show up in the editor after startup.

    Worst case you might have to recreate them… maybe that’s not too much work? I had to recreate tilemaps in the 3.x -> 4.0 migration, was pretty annoying

    • max1mum_d3ath@lemmy.worldOPEnglish
      2·
      1 year ago

      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!

      • russ@programming.devEnglish
        1·
        1 year ago

        yup! you can do something like godot -e from the same directory as your project.godot to launch the editor for that project directly

  • max1mum_d3ath@lemmy.worldOPEnglish
    1·
    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.

  • max1mum_d3ath@lemmy.worldOPEnglish
    1·
    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.

  • ArelloEnglish
    1·
    1 year ago

    Hmm, not sure if a bug or a bug fix but this slightly broke one system of mine. I had layers of sprites and when I scaled them the offset used to be synced with changes, but not anymore.

  • KapiteinPoffertje@lemmy.worldEnglish
    1·
    1 year ago

    I had some issues with scenes complaining about being corrupted, reloading the project fixed it for me. I am on 4.1 but I did move files so it could definitely have had something to do with that.