Update version wast, lost of work and time consuming...

Hello,

This thread simple to leave a trace about my last update of the Unity platform that was going bad...

I was on the 2019.4 0f1 and have been update to the 2019.4 10f1.

Where I have lost my work!

And more problemetic haven't been in the state to reload properly the package before 2 days after the update and spend like 20 hours to save and reload the assets!...

The best is that it seems to have an new update for the 2020... I just don't have get the proposal up to date about the lasted version.

I think is a little bit inappropriate to not get sync with Unity version and got problems about that one.

I guess the better I have to do is to not change the version till I get my work done.

Best regards,

A.V.

 

What do you mean lost.
Where is your Unity installation directory?
And where do you save your project?

Or the problem you have, is after opening project in new Unity version?
But then there is clear warning message on Unity, something In the line of: if you understand implication of update and if you made backup.

You need be more specific on the problem please.

 

No. What you need to do is learn to use version control. Once you do you'll never lose work again.

 

I never upgrade my project to a new version (even a minor update) without making a backup of the project somewhere else. Been burned too many times, it's like second nature working in Unity like this now.

 

USE version control

This should be probably stickied somewhere in the docs.

 

No one would ever find is. It is not really a point.
If anything, should be embedded to Unity messaging / warning / info system.
Specially during update and Unity installation, for every version.

 

What are people using for version control these days? I was getting sick of git on Visual studio online because every now and then I'd have an update that was too large and it was a big pain to get it to sync. I'm using git on a Synology nas right now.

 

I use git with Fork as a GUI, and Azure for hosting (free). I've pushed a lot of huge files and haven't had any issues beyond sometimes timing out, but pushing again generally gets it through without any further issues.

 

This is my exact experience, too. However, we don't usually have many large assets in any one push.

I think someone mentioned that Azure Repos has a 1 gig limit per push, so for projects with lots of high-res art assets I can imagine hitting that. In a project with that kind of commit size Git wouldn't be my first choice, though, I'd look at Plastic and/or Perforce.

 

Or the good old SVN... never had a problem with that!

 

Use version control. Make backups. Any loss of work is user error. If you have a specific question, please post in the proper forums with specifics. "Unity broke my stuffs!!" is not addressable. Closed.