Official New Standard Asset Characters - Third Person

I know some contract issues with the people making this were mentioned at some point in this thread, so perhaps that's why this is happening

 

I'm always wondering why this asset are outsourced, not handled by internal unity dev team

 

Another theory is that they've decided they'll focus most of their resources on DOTS from now on. At least when it comes to new stuff they're making. Based on their roadmap talk from last week, it does kinda seem to be the case (everything is becoming DOTS). And the character controller from the DOTS physics examples & DOTS samples seem to be shaping up nicely. DOTS Netcode as well seems to be going in the right direction; a much better-designed & more powerful networking API than UNET.

Personally, I think focusing on DOTS would be the best decision if true, but I know many won't agree. I really can't blame Unity if they decide to half-abandon the monobehaviour world, because after having used DOTS for over a year, I can see how unfathomably vast of an improvement it is over the old tech stack. Not just in terms of performance, but also (most importantly) in terms of making it extremely easy to write robust and scalable code, and having source code access for nearly everything. I really can't get excited for monobehaviour-based projects anymore, because I know they'll only stay relevant to me for a year or so. Probably even less

So yeah. Maybe this would explain many of Unity's "abandoned projects". Maybe they've decided it's better to wait for a proper tech stack to become available. I'm pretty confident that DOTS Netcode won't meet the same fate as UNET for example, because now they're working with tech that's actually good. And sure, it's not fun to have to go through this transition period, but it has to happen at some point

 

That's awesome. I had a paragraph about all the unfinished networking solutions in my post because they're the prime example of this practice in my opinion, but I removed it because the post was already whiny enough.

UNET is the only official networking solution I actually tried out for one of my projects. I will definitely look at Mirror the next time I want to try networking again.

As for my specific example upgrading the Unity Labs project doesn't really benefit me in any way and getting acquainted with and upgrading someone else's messy project to a state that I'm happy with can be quite an undertaking. And I already have the project and is free to pick and choose whatever code or assets I need from it for my own projects. This was more about hoping that Unity would realize the potential value in some of the projects that they're constantly deprecating and the value of letting new and future Unity users have access to some of the actually great projects they produce.

I'm already hosting a few old Unity projects on my website because there is no trace of them in the official channels so I'm no stranger to the concept, but it's something that I only do when I find the motivation for it.

And as for this thread I'm fortunate enough to be capable enough to make the character controllers I need for the projects I want to make so I don't really need anything on offer here, but once in a while it's neat to be able to quickly plop in something for prototyping or look at how other (official) developers create projects and functionality.

But I get your point. It's really cool that so much more of the stuff Unity is making is open source and it's cool that they're making so much more stuff in general than before, but it just feels so fragmented, as if it's the work of dozens of separate minds rather than coming from a group of people with a clear vision for the future. And I of course think it is very unprofessional and reflects poorly on Unity both as a company and as a product.

 

DOTS is great. I really like the direction they're taking with it and can't wait to work with it. I also exclusively use MonoBehaviours in my project. Why? Because although it's great, it's simply not there yet for production use (i.e. Unity's arch nemesis). If I pause my game in Play Mode, I can click on a misbehaving GameObject and use the Inspector to find out what's up with it. Entities cannot be selected with a click. I can create GameObjects with the Editor and drop them in my scene. I cannot create entities with the Editor, there's some kludge that converts them from GameObjects at scene start but you're still forced to use GameObjects for that workflow.

The list goes on and on. I would love to not have to deal with magic method names, behind-the-scenes reflection magic, an insane amount of legacy, one single thread, but the alternative is simply not there until 2022.4 or something.

 

As a hobbyist who only occasionally works with Unity and as someone who isn't getting any younger the thought of having to learn something brand new is scaring me to the point of not wanting to work with Unity at all anymore.

I'm just hoping that the day DOTS arrives or becomes default or when the old way is deprecated or whatnot that there are rock solid tutorials and examples and that all the stuff I already know translates over. In my pessimistic opinion I feel like it will be similar to how everything has been so far. DOTS is introduced in state where we're lacking everything we took for granted in our existing workflows and we’re left to find workarounds or alternate solutions while we’re waiting for Unity to fix things, but they're already busy working on the next big thing.

But to be perfectly honest I have no idea what DOTS is. I see it mentioned everywhere, but I'm not even bothering to look at it until I'm forced to. I get that it's super performant or whatnot, but most devices these days are super powerful and for the games most indie developers make performance hasn't been a problem in a long time. I just hope Unity doesn't forget how important it is for the engine to be fast and easy to learn and prototype with while they're working on all this new stuff.

And you don't need to explain any of it to me in this thread. I don't want to derail it further. I’ll look into DOTS when it piques my curiosity or I have to, and I'll make the decision of whether or not Unity still is the engine for me at that point in time. But what you're saying makes sense. If Unity is focusing on an architecture rewrite then working on the old stuff doesn't really make sense and it's probably not very interesting or fun for the developers involved either.

 

If they’re focusing on DOTS and the character controller from the sample then it wouldn’t hurt if they officially told us so. Then we can make informed decisions as to where to take our projects. Also, it would help if they made a URP version of the DOTS sample project. @PhilSA how’s your own DOTS controller coming along? I’m using KCC right now but keen to try out DOTS.

 

My project is wedded to the MxM Motion Matching asset, which I’m using with KCC and really loving. But it’s not DOTS compatible so I would need for the dev to upgrade it (probably a huge amount of work) or wait for Kinematica - the beta is apparently to be released in April. In other words, a DOTS controller is one thing to worry about, then there’s also all the other stuff that I have integrated with the controller that will also have to be rewritten. Nightmare.

 

Please note that development on this is at the user's own discretion, and support from Unity on it may be some time coming (if at all on the same codebase).

 

@peteorstrike
Thank you for giving updates. Bad perception of the scope was the one thing that created the confusion. It would be great it you also define the scope of the included "actions" that the controller will cover, so you don't get any more people expecting "fighting, swimming, climbing, etc ". My guess is that it would be jumping and walking on various slopes (also tell if it can be used on "planet"), this need to be stated.

 

Thanks for the update @peteorstrike . All of that makes sense.
Agree with @neoshaman but think swimming and climbing should at least be included as part of the learning materials and tutorials if not in the default version.
Also, an optional integration with Game Foundation would be really nice and maybe learning materials for using it as a navmesh agent with AI Planner.

 

Let's not starting this again please, this is what causing the scope to expand. Everyone have their own needs of what is "should at least be included" let them finished the core first

 

“should at least be included...as part of the learning materials and tutorials” if you want the full quote.

ie. I wasn’t making a request for features so much as suggesting stuff for the “learning materials and tutorials” section, in case there was any confusion as to what I meant. Just as KCC has a tutorial walkthrough. If it’s intended as a learning tool, I’d like to learn how to do those things with a simple prototyping controller. And this shouldn’t impact on the development of the controller as these tutes can come later.

 

i left out that part in purpose, because suggesting a learning material for something that hasn't been released are still adding more backlog on the team. KCC has a tutorial walkthrough but i doubt if that tutorial are released before KCC even released yet. So please lets just let them finished the core and released the package first.

 

Any idea of timing of this updated version: weeks, months ? Thanks.

 

I wonder how this might effect many of us that are sort of keeping their feet on say traditional/realistic Unity environment and at the same time are struggling with DOTS prototyping.
On the DOTS side we also have Character Controllers in development and KCC developer PhilSA just recently told me that by this summer he should be out with his implementation in DOTS, besides what we should hopefully soon (???) see in a new DOTSsample controller.
I understand your scope in now more oriented towards a stable general entry system rather than a next generation one, but some of us were hoping to use it as a base for the transition period, maybe adding some DOTS to it little by little like DreamersINC has done with his project https://github.com/DreamersIncStudios/ECS-Motion-System.
I believe that many of use will not be waiting two more months to see what we expected in 2019.
Unless of course we will be forced by futher delays in DOTS.
I believe you should at least let us know if and what breaking changes you plan versus the current implementation, that actually seemed to many a good starting point to work on. Are you going to do major changes or mostly adding features? And so no.
thanks

 

I hope they make a new 3d game kits with mario 64 meet botw character controller that would put aside the need to be overtly generic and at least address some people, the current 3d game kit is a bit lacking in terms of character control.

 

Seriously, this is one of the major gaping flaws of the Unity user experience. Let's say you're a user with a game in mind.

Unity - start a new project: You can choose between 2D, 3D, 3D with Extras (what are the extras? The info box tells me it has "presets" and "example content" - I have no idea what the former is, the latter sounds somewhat useful but I won't get to know what the "content" is before I make that new project), or HDRP, or URP. What are those? The info box says HDRP is focused on high-end graphics, and URP's description talks about 2D a lot. So I'm guessing HDRP is the new 3D and URP is the new 2D? But then what's the difference between 3D and HDRP; and 2D and URP? So off I go to Google these I guess, or I can just jump in and hope that I chose the right one. (I'm aware of what they are but this is from the perspective of a new user. Also if you pick something that you really didn't want then switching in any direction that's not 2D/3D->SRP is virtually impossible). Chances are I'll pick the "newer" ones and then I'll only later find out that most assets and past knowledge that's on the web doesn't work with them. Assume I have made a decision, and I did make my project, I'm either presented with absolutely nothing, or a bunch of non-interactive objects in a scene where I can fly around with the camera with no collisions. Cute but very minimal. I need to roll everything else myself and we experienced users know that Unity is very thin on features with anything even remotely serious save for a few exceptions (Cinemachine is pretty nice) is going to be a paid asset. Want a character controller? Sorry, the best we can do is a fancy capsule collider but there are at least 3 major ones in the asset store! Hope you pick the right one for your needs and it remains supported! The cherry on top is that a lot of engine features are not in the engine itself and I will first need to SOMEHOW learn that for something that I'm struggling with there's either a package (chances are it's going to be preview so hidden by default) or an unadvertised GitHub page (looking at you, NavMeshComponents).

UE4 - start a new project: It asks me if I want to create a game or some other kind of product like film or architecture. I know that! I want to make a game! *click* Oh, it's now asking me what kind of game I want to make! I know that, too! *click* Only at this point do we get to the "difficult" questions, but the window helpfully tells you for each of them that if you change your mind how can you change your settings to the other one. The defaults are also set to what you're probably going to use. (The others like BP vs C++, you can't get it wrong, it's just how your project is set up initially. Every UE4 project supports BP and C++ at the same time). Once I've made my decision, my project opens up and (assuming my selection was not Empty) I have a minimal game already set up for me! There's a sample character that I can control, the camera works, there's a level, I can run around, jump, etc. and the animations are already set up. Sweet! Something that I can build on and later tweak to my needs or replace if I so desire! Want a character controller? Sure thing buddy, the default one that you already have in your level supports running, flying, crouching, jumping, and also has this nice feature that you can use to transfer control to another object like a vehicle if you get in it.

Why are the Unity standard assets not standard, coming with the engine out of the box? Even if it's an automatic download after I create my project if you're so worried about the installer size.

 

Unity used to come with Standard Assets that did work out of the box and were pretty decent for the time period. Things started to downhill after Unity 4.6 and the move into Unity 5.xx. They offered a new Standard Assets for Unity 5 and had the potential to develop these further, but for some reason abandoned supporting them (maybe to do DOTS conversion). All of this with no good replacement in place to fill that gap. Maybe they expected Asset Store developers to fill that need and that they could drive users to purchases in the store instead?

 

Nothing more friendly than "spend more money to make our engine usable for the absolute basics" when on the other side of the fence you get a more mature engine for pretty much free that does come with working samples and with unlimited Megascans. This is supposed to be the part where you get the users hooked and locked in so they spend money later.

 

There is a free controller in the asset store that's already everything they promise in the revised lowered ambitions. That is it would redundant.

 

getting a ton of errors when importing this for the input system. when I try to install the input system on the package manager I get an error and it wont let me install it to unity. Anyone know what to do?

 

*Sigh* I was so looking forward to a new Standart "Prototyping" FPC and/or TPC to soon be available with the Input System in mind so we can finally ditch the editor time or splash screen only key rebinding.

Now we're ditching the FPC for the TPC only?

Oh well, guess I'll see if I can still use the GitHub beta content to rig a working controller with what we have so far.

Hey guys? Maybe when you do get around to making a new Prototype FPC, you might want to think about making sure the Player can Crouch? It's one of those features that almost all First Person POV games have and yet the Old Standard Assets FPC just doesn't have out of the box.

FoV Kick, Head Bobbing, Jump + Landing Bob all made it into the FPC, but basic crouch was left out?

Oh well, I'm getting to the point where I can actually code my own FPC from New Script.

 

Now that Unity 2019 LTS is out, any news on this front?
Any update on what is happening would be helpful.
thanks

 

From what I heard the C# class has been created. It means a lot.

Kidding (sadely)

 

Hi all, I'm new to this thread.

I love this 3rd person controller! So nuanced and responsive. It is so rad that you included animations for women. I'm always wanting that and in my experience, it's rare. Thank you

I'm trying to extend the controller to enable triple jumps. Have any of you attempted that? Any tips? Thanks in advance!

 

2020.1 is also out. any news here?

 

This Project is dead. Admit it.

 

How do I stop the Third Person Camera from dipping when I walk forward? I've changed the CM FL Run, Walk, Exploration all to (none) and that doesn't appear to do it. The camera dip is a big problem getting onto the platforms/lifts in the SimpleMovingPlatforms Scene, one moment you're looking at the platform to walk onto it and next you can't see it as the camera view has shot up. (I've set the Offset to 0,1,-1 as a work around so I'm looking down)

How do I make the camera orbit behind the character as they are running? if I run to the right/left I end up looking at the side of his head, then the camera whips around after I stop running. Even when using the right controller stick to move the camera behind the player it will suddenly whip in some direction when I stop. I don't want to be able to run towards the camera.

Thanks.

 

no news is bad news ....

 

So the last real update was 5 months ago now? The project started in April 2018

Based on this blog https://blogs.unity3d.com/2020/08/13/the-road-to-2021/ it wouldn't be surprising if it's been cancelled.

I can understand if projects are canned or delayed, but lack of communication is really annoying.

Anyway if it was me I'd just hire @PhilSA and pay him whatever he wants, I'm sure he'd do a great job.

 

Yes, @PhilSA is a great guy. Maybe when his DOTS KCC will come out they will think about it.
Lack of any response is really a shame for a serious company...

 

Can anyone explain how the third person controller is supposed to be extended? I've had some success building on it, but my additions feel hacky and I'm not sure if I'm extending it the "right" way. Is that what the "extensions" on CinemamachineStateDrivenCamera is for? What's the proper method of adding new actions, animations, etc?

 

Having spent time implementing on top of this several features on my own I have sadly abandoned hope in its real support by Unity, so I would advise you to look elsewhere unless you are able to get some feedback from Unity.
As you can see in many posts above up to now we had very little luck on this matter.
Id is very sad, as this was a promising controller, at least for third Person, with native support for the new Unity Input System and Cinemachine.

 

@willgoldstone any chance to have those character assets to asset store? currently unity lack of basic template for character controller. Just split this packages so people can using it as a basic for prototyping or as a base for character control module.
Basically split it into multiple assets ie :
- Base Male and Female characters with the animation assets.
- Protoland scenes
Not sure about the basic character controller script, and the packages in the thread are not something basic anyway.

 

The latest Humble Unity bundle has a 3rd person controller that looks decent. I'll probably just use that for now when I need something quick.

 

Amazing to finally see someone at Unity active here. Thanks for the comeback.
Hope that we will not have to wait other 6 months to get some update on this.
Let's avoid over-engineering and come up with a good solution, possibly with samples and documentation.

 

This is sounding a lot like what the New Input System went through. If it follows a similar trajectory then I suppose we'll see it released as a "verified" package for Unity 2022 LTS that still doesn't cover all the functionality that existed in the character controller(s) which came with the standard assets a decade ago in Unity 3.x.

 

Is this new project going to be based in or around Visual Script code? -- or possibly be converted to VS later?

Seems like a perfect candidate to test how modular of a system can be made using Unity's incoming VS solution (and also how easy it would be to modify). Seems like the "over-engineered" portion could be done away with if it involves a setup like this.
I would honestly like to see an ECS-like setup to the systems, making them A LOT easier to modify / expand upon.

 

Certainly the problem here is trying to do any one size fits all approach. Seems like a better plan would be to build some movement core, that was modular, and could extended to vsrious use cases. Then out of the box you provide 2d controller, simple3d controller, and advanced3dController.

By trying to make 3 flavors with the core API, it will force you to evolve it, and make sure it has a nice api surface, additionally the 3 examples will go a long way to help us understand how to extend it. Finally, you can go to town on the advanced 3d controller, as devs who donta need it, can just ignore it, focusing instead on the simplified arcade / arpg / sm64 style controller.

 

I had a quick look at this, as I've been working on developing a 3rd person Controller for a mobile game. (My workplace already have a few released titles with character controllers, we're looking to improve on that front though)

Out of the box, the movement seems fluid and responsive.

However, the code seems extremely over-engineered and intimidating. I'm an experienced developer but I have a pretty good character control script in about 100 lines of code, using the built in character controller and root motion, mostly relying on blend trees. The idea of switching to a controller with thousands of lines of code spread over multiple components and complex animation trees is not appealing from a code maintenance/extensibility point of view.

Eg if we come across a situation that this package doesn't cover, we need to then figure out thousands of lines of code to determine the best way to extend/customise it without breaking anything. Performance is also a concern, as this is for a mobile game which may have 30+ active characters.

As with some of the above suggestions, I would like to see a modular system which can be adapted to different approaches, rather than a one size fits all approach. This has been the issue with most asset store/existing controllers I have looked at too. They will contain wall running, jumping, crouching, rolling, and many other things which may not be required for a lot of games.

Our game simply needs a realistic character that can run around. It's not an action game, but we do want a responsive and realistic human controller.

Also, it really needs a good example of using foot IK. Providing an out of the box solution for characters and then ignoring foot placement is not going to be enough for anyone trying to make a high quality game.

 

I'm always wondering about this part, Unity do have IK system but they never include it in their character controller demo/packages

 

You'll probably need to start looking into Kinematica / Motion-matching if you want this level of quality. It's in preview, so it's worth a look.
Having a Character Controller that can access Kinematica (or not) would be quite handy, and worth a little "over-engineering" -- in the sense that it remains modular and entirely removable.

This is why I suggested a more ECS-oriented / modular approach that would work best in a Visual Scripting solution using the "Tag/Trait" components I keep suggesting in those threads. This is as modular (and as easy to understand) as something can get.

Components (as they currently exist on a gameobject) are terrible and obfuscate behavior that you need to see (and understand) at a glance. Simply calling a component "Third-person movement" doesn't tell me whether it handles only forward/backward, up/down, strafing, jumping, flying, dodging, taking cover, or whatever -- In general, I need to see the script for that.

HOWEVER -- I would rather not have to go even that far.

I would prefer to look at something like this:

Spoiler

This is my Tag/Trait prototype btw:

Just my two-cents.

 

Hmmm... hireing takes months, building good functional team takes months. Then the team vants to start from scratch when everyone in the team wants a rewrite. And now its nearly 2022, it may or may not work with other overenginered stuff i Unity...

If you at least tell everyone this is abandoned, then that would encurrage other developers to create and sell their own. And people would also buy them instead of waiting and hopping for your telease tgat never comes or will not fit their project. And they would not hsve to relying on porly maintained assts because you are suposed to replace them.

Have a nice day.

/Mattias

 

I've analyzed a few character controllers from standard assets, examples and microprojects and the most annoying part is that if you got 6 different controllers made by Unity themselves, you get 6 different solutions and each has it's own "unique" way of solving "problems" like "oh, theres still a little bug with ground detection, instead of using the built in isGrounded, lets hack in a custom isGrounded that only works for this demo". This is not unique to Unity and its examples and the Unity examples are actually above average. I regularly get examples for industry software and components that are written in a way that no one would ever do in a real world application. It's shockingly common.

 

While I agree with you -- a "standard" way to solve a problem has never been Unity's approach.

Instead, Unity's only "standard" is that it throws the toolbag at the developer (with little to no hand-holding and next to no documentation / information) and says "Get to work." -- and we do.

This needs to change, at least in some measurable way.
But to be fair to @Unity, a character controller can be done a thousand different ways. Only "6" different approaches is actually a really small sample size of all the possible kinds of character controllers out there. For Unity to take this on is something I commend them for -- from the outset it has to be a really solid, flexible, performant design (that can be easily modified) -- otherwise you simply scrap it and make your own (as is the "standard" now).

What it sounds like you want (as well as everybody else -- including me) is something far-reaching that anyone can still (easily) modify in the editor/inspector to do their bidding. Preferably without digging into the code.


The best way to do something like this is with a well-designed Visual Scripting system (that works from top-down) that can expose controls/values and even entire systems in the editor / inspector so that beginners and veterans alike can use the system and modify it at will -- with little programming knowledge.