Wow. Woo Hoo!
This looks so good!
Are there any plans for improved support with netcode for gameobjects for the new system?
Wow. Woo Hoo!
This looks so good!
Are there any plans for improved support with netcode for gameobjects for the new system?
You mentioned IK several times in your post and there are several shots in the RoadMap video presentation on YouTube that most likely show IK. But will there be any sub-broadcasts on the IK system?
Iām leaning heavily on only having āONEā animation solution on U7. Thatās means I donāt want to see Mechanim & legacy anim as an option in U7. But Iām not sure how this will impact āTimelineā. Since Timeline requires you to have Animator (playable) on the GameObject you want to animate, that means you canāt axe Mechanim right? Unless you change Timeline underlying API to use the new tech, or you have equivalent of Timeline & playable from the new system? That would be most ideal scenario, unifying the animation tech stack.
Hello again.
Thanks for jumping in so early with the detailed questions, unfortunately I/we canāt answer just yet. But I absolutely will in time. Not only that, but we will try and incorporate answering these types of scenarios in an upcoming post. I hope his does not dampen your enthusiasm.
This is still on our to do list, and I honestly canāt say 100% if we will have time to address this (along with the numerous other animation window requests)
I kind of mentioned earlier, but to be clear. We are no longer investing in improving Mecanim, Humanoid or the Animation Rigging package, however they will absolutely continue to be supported. Instead we are focusing on the new universal character system, which will be capable of so much more, and no longer need any of the above.
Whatever improvements are made in Netcode, we should be supporting them.
Good callout, but a bit like my answer to Yoraiz0r I canāt answer that one just yet, but will do so in an upcoming post at some point.
I edited my original post to include a link to the Roadmap video, but thought to add it here as well.
This all looks insanely impressive! Congratulations to you and the whole animation team. I canāt wait to sink my teeth in the new system!
Thatās a shame, but happy this is planned at some point.
That would be awesome. In general, anything that would allow complex rigs and animations to be made directly in Unity.
Accompanied of course with improvements in Unityās keyframe animation toolset.
Right now, we need to bake animation and bring it in Unity using heavy animation files. The same data is mere fraction of the keyframes in our DCC and a fraction of the file size.
In the exported animation files there is a keyframe for every frame, even if you optimize it as much as possible it still is large. A good chunk of game installation size is thousands of large baked animation files.
Ask @keesrijnen about that. This guy has made one of the best universal rigging systems out there. Puppetshop/CAT for 3dsmax.
What I understand from the new system is, the system itself was IK driver. It not separate IK from animation logic system anymore. Every kind of logic to animate transform component is and could be under animation system. And IK or any kind of rigging will flow into the graph node then we need to have blending graph to decide which should be in control
And I assume IK will be the built in node of this system
I create animations in Unity, and I prefer to make character animations directly in Unity rather than in Blender or Maya. This way, I donāt have to switch between different software, and I can directly preview how my character looks in my scene with Unityās rendering. For character animation, HumanIK/FullBodyIK is extremely important; itās much better than simple Rigify, as it makes animation creation more convenient. I personally created an animation tool in Unity using Final IKās FullBodyIK and keyframed it in the Timeline, and I used a motion path from the Asset Store to make the animations smoother.https://vimeo.com/1011713813
So, in Unityās new animation system, will there be similar features that facilitate animation creation, like FullBodyIK animation layer parent constraints? Iām really looking forward to this!
Looking good! Main thing Iām looking forwards to is the record-and-playback debugging tool, that will make an incredible difference. Now if we could only get that for every other systemā¦
Iām looking forward to being able to try a beta of this! The new UI seems somewhat overwhelming, but I assume itāll not be too bad once weāre used to it.
Great to hear that we can also just play an animation and bypass the system entirely, for those āI just want a door to openā cases.
The big remaining question is āwhat happens to timelineā. A system for syncing unrelated kinds of animation-like things on a bunch of different objects is very useful. Sadly, Timeline was built during the āUnity will do everything 3Dā era of JR, so itās more concerned about creating films than itās concerned about creating cutscenes. Iād love for a rework thatās better at handling things like branching and waiting for player input. That being said, just having this new animation system as a track in a Timeline would be a good stopover.
Lean data centric architecture.
GameObject as a plugin.
I believe in you Unity!
Make it happen!
I honestly asked as the demos shown off looked like they were in FK, not IK. Problem Iāve had with Unityās built in systems was that it lacked dedicated character animation tools, especially with the lack of tools for making humanoid animations which require you to look for either a github tool or something in the asset store that can help with IK stuff. The new system has potential, but itās unknown to me if thereās any IK scripts or if theyāre putting some of the Animation Rigging stuff directly inside the new system.
One very important question for me is how do you reference parameters from script in the new system?
I know itās always a complex topic but Iām honestly tired of relying on string references everywhere in my project.
I can always take care of it myself with a custom of class and using Animator.StringToHash()
like @CortiWins recommended to me last time (link).
But since this tool seems to be built for scalability i would guess it might have a built in solution.
Iām probably repeating myself at this point, but the generated C# class from the input system feels like the perfect tradeoff for me.
Would something like this be possible, or do you have another solution in mind?
Either way Iām very excited for this tool. Iāve been waiting for this for years and itās even better that I expected!
Even if it takes a while Iām very excited for when this will be available.
I also feel this doesnāt get enough attention and then it spirals into āThere isnāt enough documentation!ā. The legacy particle system comes to mind in terms of just having finicky logic and setups to execute core tasks. The code requirements arenāt TERRIBLE but there are several things from naming conventions to organization and some irregular syntax for enabling different things. They all add up to make interfacing with the system kind of a headache.
Another example: It always seemed weird to me that we have to create a duplicate variable (I know iām butchering the jargon) just to then adjust the settings of a particle system
var particleSys = particleSystem.colorOverLifetime;
particleSys.enabled = true;
Iāve created some custom scripts to change the emission rates, color gradients, or restart particles or whatever, but why isnāt the internal logic out of the box more approachable and refined? Itās like spending years rebuilding an old car but leaving the exterior unpainted and exposed to rust. Itās such low hanging fruit to put that really nice coat of paint on it and make it presentable.
Iām kind of a scrub when it comes to code and when Iām creating custom tools to be able to do basic functions with these systems it feels as though something is āoffā.