I worked in the editor for a solid 5 hours yesterday and it didn’t crash once and gave minimal error log messages.
Anyone else having this problem?
It crashed on me twice today, so no, I don’t have that problem. 
2023 is supposed to crash. Use LTS if you don’t like this feature.
Don’t worry I got your crash luck
I quit Unity and instead of closing it decided to crash for some reason. Task failed successfully?
I found the newer version had less issues than the LTS version, a BIT more crashing, but less progress crushing editor log messages.
If you used LTS, some one might give a damn if you’re crashing.
JakkOS, I could not give less of a sh*T if you give a damn, no one asked. I never made posts about Unity crashing, I’m mostly grateful for these tools, I made this post to low key thank Unity for making their engine more stable (am I a bit frustrated with the instability of late? Sure). For the record, I WAS crashing in LTS, but found the enhancements of the slightly more crash prone newer version to be worth migrating to.
This current iteration of the engine is superior to the LTS as I’ve experienced it so far. I know they have a largely thankless job and wanted to express that their improvements have not gone unnoticed.
LoL.
Thats funny too.
I
I used to play this game with my friends. We would see how dry our humor could get… …and the first one to take it seriously would laugh with yhe rest of us.
But it is funny, as in peculiar, that earlier tonight I was thinking of starting a thread asking why use LTS?
Because newer versions get better goodies and performance, (sometimes performance in one area but loss in another), and bugs appear, yes, but they also get fixed, as LTS bugs are identified and fixed.
So I dunno, my upgrades have been usually painless, maybe a couple days headache, if I chance upon a new bug…
…and of course, this was all inspired by reading about 2022s LTS foibles.
I responded because you sound like a beginner coder who doesn’t understand what the “warranty void” sticker means, and you could use some ground rules. If your Unity crashes, it is your own fault.
Likewise if your problem is coughing and you’re smoking a pack of cigarettes a day, don’t vent it at Marlboro.
By the way I am using 2021.
I’m stuck in a Unity will delete all layouts and rebuild them infinite loop with 2023.1.5… so no, mine is working just about as intended (p.s., if anybody has a clue what to do about this, drop a line…)
Yes I have a clue what to do about it. Enjoy it.
I can see how my post could be seen as someone just wanting to sh*t all over unity and whine about crashes, I also didn’t need to escalate this conversation so quickly, my bad there.
No need to be a j*rk to random bystanders just venting a little frustration, if you truly have an idea how to help do it and maybe something positive can come from this devolving thread.
The truth is Unity has been really buggy, more than usual, a bit of concern and raising these issues publically is needed so people can know what they’re getting into. You are correct, if possible people should use older LTS builds.
Edit: Oh and quick edit, I’m not a fantastic coder. I don’t know how to “get myself into trouble” with fancy bits of code that hook deep into Unity and change internal logic. Which makes it all the more unusual there are so many things breaking all over.
Seriously, get off the 2023 unless crashing is what you want. Read the release notes and understand you are on a branch that is known to crash in several occasions. This is cos of Unity normal development cycle.`
Importing FBX files crashes. Ok? Who needs those?
These crashes were known when they released it. It is a part of the package. Live with it if you want to use it.
Whining here doesn’t help Unity to fix those bugs. If you want to be on this branch, then help them debug this stuff.
Again, the newest version of Unity is far more stable and my project is largely isolated from these bugs. I made this post mostly as a “keep up the good work”. I’ve acknowledged you are right about the stability of Unity, I’ve tried to reach out and make amends so this post could be positive for those engaging. Oh well, have a good one.
The stability of Unity is perfectly fine. I develop daily and get very minimal issues, and out of those issues I suspect I am the culprit for most.
I don’t think I have ever come up with a persistent editor issue that wasn’t quickly fixed with a patch. I have reported some bugs and Unity has replied to actually all of them that these bugs are known. Then they got fixed in the next patch. These issues were mostly minimal - in certain situation a window renders incorrectly, or things of that magnitude.
This is not out of luck, but because I am experienced enough to know to only depend on stable branches. Applies to all software, not just Unity. I suggest you do the same.
And it’s not just here in Unity - when junior coders are made architects, they wire their dependencies to open ended versions instead of absolute versions, so their dependencies get auto-updated at completely sudden times. You come to the office on Monday and nothing works cos your library auto-updated. Then once they figure out what’s happened, they start blaming the developer of the module.
When your software has any dependency (such as the Unity platform), you manually choose each absolute version, and do upgrades in a controlled manner. When choosing the module version, you look at it’s maturity. You do investigation first to determine which version is mature enough that you can trust it. And if it ends up being the wrong choice - tough luck! Your investigation was wrong. Monday wasted on pointless crashes and you are to blame!
If you depend on development branches, this means you want to be their beta tester and help them out.
Try using cloth component, you will get a crash…
Very helpful, yes.
It does help alert them to these bugs… as in this case, my issue is NOT on the list you helpfully provided. You start the editor on a new project (URP - Core) and it says:
If you hit continue, things blink for a moment and it goes back to this message. If you hit quit, it quits.
It’s possible there is a conflict with other versions of Unity I have on my system. I’m an experienced Unity user, and was wondering if anybody else was experiencing this particular issue. Given that I was installing it so I could assist an instructor in reviewing the lectures on Shadergraph he’s recording (and he chose to use Unity 2023), I had some expectation that it would at least load. I apologize for annoying you by inquring about this.
You’ve likely already tried it, but have you deleted your Library and temp folder? You could also try deleting the most recent file in UserSettings>Layouts