#also you literally cannot put a 2D canvas inside a moving 3D object in unity without creating a MASSIVE cpu sink which is ENTIRELY
Explore tagged Tumblr posts
Text
Also worth noting that Unity absolutely sucks for anything with very large numbers of moving/interacting elements unless you're willing to put a lot of code time in to roll your own solution around Unity's proposed one. Games like Pikmin or Katamari Damacy implemented with the developer guide best practices would have extreme CPU-bottlenecked performance issues just due to how the engine works. If you see a citybuilder or strategy game or management sim chugging like hell under Unity (Oxygen Not Included being a standout example) just know that the engine was never intended for that sort of game and the developers had to learn that lesson painfully some time into development.
Please unionize development already. This isn't the first time this shit has happened with Unity and it won't be the last. If you happened to notice the huge spike in EA/announced VR projects being abandoned at the start of 2019, know this was another thing Unity did we couldn't do anything about. It sucks.
In the advent of Unity's new bullshit, I remind you:
MOST COLLEGE VIDEO GAME DESIGN CLASSES TEACH UNITY AND UNITY *ONLY.*
A GREAT DEAL OF THE GAMES YOU AND I PLAY EVERY SINGLE DAY ARE UNITY GAMES.
THE VIDEO GAME INDUSTRY *IS NOT UNIONIZED* AND THEREFORE DEVS HAVE VERY LITTLE ABILITY TO FIGHT THIS.
If you see your favorite games vanish suddenly, it's NOT bc the devs don't want you to play them. It's because Unity is a dick.
If I see you get mad at the indie devs that are being forced to either delete their work forever or cough up money they don't have, I'm biting you and your arm is coming with me.
#also you literally cannot put a 2D canvas inside a moving 3D object in unity without creating a MASSIVE cpu sink which is ENTIRELY#unnecessary; and this is one of the prime reasons why most Unity VR games with anything attached to the hands perform like ass
13K notes
·
View notes