At first I thought I was just running low on RAM, but it’s now been weeks and the Unity Editor is still running the game at what I’m pretty sure must be sub-20 fps. Totally fine in build mode, it’s just the editor that’s completely fucked.
-
Show this thread
-
In the past, it’s been really bad—I expect something more like 40 fps, which is bad enough that you can’t really reliably test animations without doing a build—but this is just a whole other level. Doing anything feels like trudging through molasses.
1 reply 0 retweets 16 likesShow this thread -
Anyway, can’t wait until this gets posted in some Unity internal Slack and I get three different Unity Technologies engineers saying “do you have a slow gizmo running? is the inspector open?” in my mentions even though OBVIOUSLY I wouldn’t, waste more of my time, and fix nothing.
1 reply 0 retweets 16 likesShow this thread -
Honestly I only tweet about this stuff in the hopes that maybe someone who was considering using Unity will look at it, and spare themselves from an entire dev cycle of misery. Please. If you can somehow avoid using Unity despite its strangehold on the industry, SAVE YOURSELF.
4 replies 4 retweets 56 likesShow this thread -
Replying to @christinelove
I always wondered, why you decided for Unity and not Unreal? (I'm a noob with both engines so I have no clue)
1 reply 0 retweets 0 likes -
Replying to @WinterwolvesG
Because as much as Unity is hell to work with, at least I get C#. I don’t know if I’d ever get anything done if I had to work in C++ :(
1 reply 0 retweets 3 likes
ah OK makes sense. I used C++ and I'd never go back to that either :D
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.