Cant open level out of nowhere?

I finished a level I was working on a while ago and came back to it not even an hour later and now its saying it wont open cause it being saved in a higher or upgraded version, but im using 4.10 and I havnt updated it to anything higher when I made it.

I had exact problem. I have been forced to update engine to 4.12.

Hello,

I’ve never seen this occur before other than when it actually applies, as in when people try to open a project saved in a newer version with an older version of the engine.

Can you think of anything that changed that could’ve possibly caused this? Possibly content added from another source? Have you tried making a copy of your project and updating it to the next version (the next hotfix or 4.11) to see if the message does go away at that point?

We haven’t heard from you in a while, The Alpha Maiestro. Are you still experiencing this issue? If so, could you provide the information I requested in my previous comment? In the meantime, I’ll be marking this issue as resolved for tracking purposes.

I too am having this same message on a level i spent a TON of time on. Please somebody help

Hello ,

Without information there isn’t really anything I can do. Have you tried what I mentioned in my comment to? What version of the editor are you having this issue in?

Sorry for the delay. Email issues. I originally used save as, and the level was inoperable. I had access to the original. So maybe it’s an issue with the save as feature? The level was originally from a previous project that was also 4.10.

Does this mean that any time you save a level with “Save As” it becomes corrupt, requiring a newer version of the editor to be able to open it?

It’s only done this once and I’ve used save as approximately 8 times since then and the problem hasn’t persisted.

Thank you for the information, The Alpha Maiestro. I’ll be marking this as resolved as the issue seems to be fixed on your end. , if you’re still experiencing this issue, please try responding with some more details on the nature of the issue so I can try to reproduce it.