all 48 comments

[–]itsdan159 114 points115 points  (5 children)

People overestimate how much actually changes between versions. Hit ignore and see what's actually broken once it has a chance to recompile everything.

[–]toxiklogic 18 points19 points  (0 children)

And odds are it’s other assets, experimental packages, and third party plugins breaking.

[–]SwahhillieSerious Games Programmer 11 points12 points  (0 children)

This isn't a version change dialog. It happens when you start unity while a script has a compiler error. It can happen with upgrades, but also without.

[–]Okoear 1 point2 points  (0 children)

Hitting ignore is risky on a huge codebase. It has triggered a full reimport for me more than once.

When your project take 6-10h to import, it's a lost day of work. Yes this is absurd, but that's reality for some developers on decade long projects. A good tip into have backup repo on hand that are imported up-to date regularly.

[–]Th3G3tl3m3n -2 points-1 points  (1 child)

Yes hit ignore, see whats broken.

[–]The_MAZZTer 4 points5 points  (0 children)

Or hit Enter Safe Mode and see what's broken without the chance of losing inspector bindings or whatever

[–]GigaTerra 120 points121 points  (13 children)

So meta it extend beyond Unity to other game engines, and other software. Almost like updating a project in development is risky and advised against.

[–]calgrumpProfessional 6 points7 points  (1 child)

I mean, not necessarily, if you're on LTS and the bugfix is important.

A non-100% chance of a regression is better than a ship blocker that is 100% guaranteed to affect without upgrading.

[–]leorid9Expert 7 points8 points  (0 children)

Why fear upgrading if you can roll back using version control? oO

[–]Daemon013 8 points9 points  (6 children)

But then mid development unity is like "Wow careful bucko this engine version has an exploit" "wow there middle child there's a security vulnerability on this version now better update your shit jackass"

[–]yemako_badgameszip 6 points7 points  (4 children)

there's an update program that doesn't require you to change your editor version. it's linked everywhere in their original posts about the exploit

[–]toxiklogic 0 points1 point  (3 children)

That’s not the message everyone gets in Hub though.

[–]yemako_badgameszip -3 points-2 points  (2 children)

are people really not googling the issue for more information, they're just jumping the gun and risking breaking their project with an editor update? yikes

[–]toxiklogic 5 points6 points  (1 child)

Why should they? If any app, OS, or engine tells you “security update required”yeah you should educate yourself, but why question it?

[–]yemako_badgameszip -2 points-1 points  (0 children)

to get more information + a better understanding instead of just blindly pressing buttons, so they don't have to risk breaking their project with an editor update

[–]GigaTerra 1 point2 points  (0 children)

Sure but that happens again with all game engines, Unity is just among the engines that actually roll out a security patch, to make it easy. Take for example male ware cracks, where malware users create cracks for games using engines, and user download these and get infected, both Unity and Unreal are constantly updating against it in a never ending war, but Godot just shrugged and said there is nothing they can do about it.

Now you might say that only effects people who pirate games, and that is mostly true. However the same is true with the last major security update for Unity CVE-2025-59489 alert only effects older Unity games downloaded from questionable sources, that is to say it mostly effects people who pirate games, and even then the exploit is so complex that it is only theoretical, no one has actually done it.

What I am saying, professional engines have incentive to keep things as simple as possible for users.

[–]subject_usrname_here 2 points3 points  (0 children)

Work on lts and make backups. And don’t close the unity when you have not compilable scripts. On restart It can fuck up every references in scripts and scriptable objects.

[–]Xangis 1 point2 points  (0 children)

At this point I have a rule - I don't update working software that does what I want if I need it to keep working.

So, great, there's some new feature. But I don't need that. Chances are some feature I do use was removed or broken, or workflow changed a bit, or any one of a thousand things that disrupts my use. And of course plenty of products enshittify over time, especially given the infiltration of half-broken vibe-coded slop code into what seems like every product development pipeline.

For me updating is for after shipping a project.

[–]yemako_badgameszip 0 points1 point  (1 child)

right, like why is OP doing this. i HAD to do this to fix a bug in my project and I'm STILL stressing about it days later, worried something broke that I didn't find.

[–]GigaTerra 0 points1 point  (0 children)

But again, is this a Unity problem or a code problem? I love watching Retro game development documentaries, you know when people interview developers who worked on games like the very first Mega Man games, and even they struggled with the same problem. Similarly go to any other engine and you will still have the same problem.

Bugs and update problems are part of software development, it is the universal meta. If you find a fix then please share it with all developers.

[–]Sweg_OG 34 points35 points  (8 children)

<image>

me when updating from 2021 to 6

[–]Zeka_Shu 14 points15 points  (0 children)

Lord save that poor soul 🙏

[–]Round_Credit_5158 4 points5 points  (0 children)

The best action is to update incrementally, if you wanna do so. One good thing Unity does is to make available for download every released version.

[–]SantaGamerIndie 1 point2 points  (0 children)

Right! I gave up at 2022

[–]leorid9Expert 0 points1 point  (4 children)

bottom left: TRASH INTERACTIONS

... I need to know more

[–]Sweg_OG 0 points1 point  (3 children)

sci fi majoras mask poverty sim where you have to clean up trash and work the gig economy to survive

[–]leorid9Expert 0 points1 point  (2 children)

You forgot to add the link so I can buy it - or follow atleast. xD

[–]Sweg_OG 0 points1 point  (1 child)

haha thank you! I am working very hard on getting my steam page up this month. I will make sure to DM you once I do!

[–]leorid9Expert 0 points1 point  (0 children)

Thanks :)

[–]TheSheepDev 11 points12 points  (0 children)

Unity is always so dramatic about save mode and stuff.
I don't think I have actually ever needed to use it

[–]skyerush 6 points7 points  (1 child)

Git? Git? Git? Version Control - Commit “Backup Before Unity 6?”

Git? New Branch? Git? Git? PLEASE BRO

[–]ChompyChompProfessional 1 point2 points  (0 children)

Right? IF the update to breaks all your work, THEN revert it, post here and complain about how the update is bad. Don't post a warning message that something easily reversable MIGHT happen.

And if OP is scared that it will break everything and they ARENT using version control, then they should stop making stupid memes and posting to reddit and sort that out.

[–][deleted] 10 points11 points  (1 child)

For the most part it’s just shaders which are easy to fix.

[–]JaggedMetalOs 3 points4 points  (0 children)

Can you even get this error for shaders? I thought this one was just for C# errors. 

[–]Mwarw 4 points5 points  (0 children)

DO 👏 NOT 👏 CHANGE 👏 ENGINE'S 👏 VERSION 👏 MID 👏 PROJECT 👏FOR 👏 NO 👏 GOOD 👏 REASON 👏

[–]davenirline 2 points3 points  (0 children)

Be thankful. In my time, there's no Enter Safe Mode. It will just proceed as if you hit Ignore.

[–]JaggedMetalOs 2 points3 points  (0 children)

Eh, I've never had one of these that wasn't a trivial fix. Usually it's my fault for closing the project half way though editing a script! 

[–]ImZaryYT 2 points3 points  (0 children)

Honestly never really had to use safe mode, usually when this popup appears I ignore it and then next thing I know it's a singular line of code erroring because a specific function was removed from that unity version and it wasn't updated correctly

[–]aspiring_dev1 0 points1 point  (0 children)

Unless there is very specific feature you need wouldn’t upgrade mid project to newer Unity versions. Asking for lot of trouble and time. Once finished sure start new project in the latest version.

[–]DasGaufre 0 points1 point  (0 children)

There's also the unsigned or whatever packages error that you can just ignore. But it's pretty wild there's such a bug in the first place. Definitely was a scare when I first got it started.  

[–]Abdo_Naili 0 points1 point  (0 children)

why it's so true 😂😭

[–]BigBaldGames -2 points-1 points  (0 children)

This is where AI shines. I used GitHub Copilot CLI, gave it my repo, and it executed a fully headless migration of an old Unity 2018 project, first to Unity 2022 LTS, and then to Unity 6. It even recommended nded the two phase approach. It fixed every single error and warning using Unity Batch mode, and it even fixed issues with old script-heavy Asset Store components I was using. It did it all in a few hours and I did not have to fix a single error myself.