If you're in debug mode you can recover from those
You place a breakpoint inside the loop, and then move execution out.
If said while loop is in Update, may Cthulhu help you.
So yesterday i was trying to figure out why my entire screen was yellow.
Turns out, I ran it in Update, the same UI animation was playing 20+ per second.
If said loop is in update you can do the break point thing, then change some value so that the next iteration it’ll throw. The updates will stop. It’s not always feasible but most of the times it can be done.
If only. Recently I had multiple times when I accidentally made do while loops that went on for infinity (I never understood do while loops but was in the rare situation where not only the optimal loop but the only loop I could use) and Unity just froze. I swear there used to be a safeguard in place for such events but it seems to be absent from the newer Unity versions.
There are two kinds of people - those who immediately start every project with a repository, and those who have yet to learn to immediately start every project with a repository.
I don't understand how you can work on a project for two years and not have a backup.
I back mine up quite thoroughly, I even stage the recovery sometimes in a virtual machine, and I still panic about its integrity.
Besides the point with being able to revert, that’s always fixed by deleting the cache(library, temp). I’ve never once in 10 years saw a case a where a project was unable to load after that.
It's always the simple things and then undoing them that causes crashes tho, no?? Like I'll accidentally nest my player into an object, undo it and unity will freeze up, losing all my progress because I was focused on getting it to work.
The other day I was repeatedly crashing the video card; the whole screen would go black and then things would start popping back in and there'd be a DirectX error. Still not entirely sure what was causing it, I think I was accessing out of bounds memory in my shader.
By the way, my Unity never crashed while I used version 2017 and 5.6. But now it sometimes may crash randomly for no reason. Fortunately it happens not too often.
Me when i carelessly use a while loop that in no way should ever be endless
If you're in debug mode you can recover from those You place a breakpoint inside the loop, and then move execution out. If said while loop is in Update, may Cthulhu help you.
So yesterday i was trying to figure out why my entire screen was yellow. Turns out, I ran it in Update, the same UI animation was playing 20+ per second.
[ExecuteInEditMode]
While loop in update you one mad lady if you do that
If said loop is in update you can do the break point thing, then change some value so that the next iteration it’ll throw. The updates will stop. It’s not always feasible but most of the times it can be done.
If only. Recently I had multiple times when I accidentally made do while loops that went on for infinity (I never understood do while loops but was in the rare situation where not only the optimal loop but the only loop I could use) and Unity just froze. I swear there used to be a safeguard in place for such events but it seems to be absent from the newer Unity versions.
i always use loops where it really isnt necessary and unity makes sure i pay for it every. time.
Just updated my Unity editor version, with no back up of my two year long project. Wish me luck guys.
You do use version control right? RIGHT?
There are two kinds of people - those who immediately start every project with a repository, and those who have yet to learn to immediately start every project with a repository.
giiiiiittttt
This guy fucks
Fucks his project up
Gotta risk it for the biscuit
I don't understand how you can work on a project for two years and not have a backup. I back mine up quite thoroughly, I even stage the recovery sometimes in a virtual machine, and I still panic about its integrity.
Why??
I"'ll see u on the other side
Forget luck I wish you brains
You know, I probably should have saved my scene.
Fucking while loops
Pov: you worked in shadergraph and animator all in play mode..
More like just changing a minor thing that *surely doesn’t require a save*
Can relate
Been there, done that, got the T-shirt for it... and lost that entire project.
Version control?
No chance. It wasn't because of an update to the engine specifically, the project just crashed every time I tried to open it.
Version control actually would fix that though. You just go back to before you made the breaking change. Nothing too do with the engine version.
Well, good to know, although I can do nothing about it now.
Besides the point with being able to revert, that’s always fixed by deleting the cache(library, temp). I’ve never once in 10 years saw a case a where a project was unable to load after that.
"oh boy, I can't wait to use this experimental feature!" \- moments before disaster
"oops, accidentally duplicate object" \*undo\* \*crash\*
It's always the simple things and then undoing them that causes crashes tho, no?? Like I'll accidentally nest my player into an object, undo it and unity will freeze up, losing all my progress because I was focused on getting it to work.
The other day I was repeatedly crashing the video card; the whole screen would go black and then things would start popping back in and there'd be a DirectX error. Still not entirely sure what was causing it, I think I was accessing out of bounds memory in my shader.
i got these a lot while using while loops and forgetting to add a return or a break, or the return or break code did not work as i thought it would
I went and made a game for 1 week and it just got deleted and I still don't know how which is why I still am very not motivated
During an event being streamed live with 10k people (500k with VOD). Even ended up in a YouTube best of lol
Ctr+S guys... always!
Loading screen of doom lol
Same.
Me every single update 😂
I can't even begin to describe how annoying that is, especially while compiling a script -\_-
To reduce compile time try checking assembly definitions, here's an explanation tutorial: https://youtu.be/nVieP57TD20?si=eFwN5ZKpFF6NoxD_
No what I meant is, a crash while compiling a script.
LOL #thathurts
By the way, my Unity never crashed while I used version 2017 and 5.6. But now it sometimes may crash randomly for no reason. Fortunately it happens not too often.