

Because animating + moving ground + wind + moving platform is a hell lot of reference to translate and sync. And I stopped when I realized I had to implement moving/rotating platform too, and differentiate between force applied by environment () or the input for the animation. In a world with no up direction that's a nightmare. But generally individual features I do.Īlso the kind of gameplay I want to do always involve obscure stuff nobody can help, My last encounter with unity's physics let me running in literal circle during 3 years, because it was a 6dof platformer, where you crawl freely on a surface with a camera similar to zelda games (direction of cam and character aren't the same). I do, it's just putting many features together that collapse, also there is a size there I can't track code, and hen I abuse encapsulating code into function, it make tracking bug a nightmare, after a few inception scroll and I forget what I was doing. There's plenty of savings to be had if you figure out specifically what your unique case needs and build something custom that only does that, in the most efficient way possible. We did have a bunch of ideas to push the limit up further, but since we'd already exceeded our spec'd requirements we didn't get to try any of those out.īasically, Unity's built in stuff is great, but it's built to meet broad and generic requirements. Rendering wasn't the bottleneck in either case. A simple test with a mockup of our custom system had several tens of thousands on the same hardware. In our tests, for our needs Unity's built-in systems topped out at around 6,000 units on our target hardware. We did it by making a custom system built specifically around the types of interactions we needed. In my project rendering wasn't really a concern, but we still had to handle all of the "physics" side of things. I've done something similar myself, albeit less graphically focused.

Those tools simply aren't built for this kind of use case. Click to expand.People saying it's impossible to do this kind of thing in Unity are almost always referring to using the built-in, general purpose tools.
