Search options (Page 4 of 20)

Then Legacy is the only way to animate it (it won't mirror on 2P side otherwise).

Unfortunately, that means your cloth physics won't work as good now. 

I suggest having a look at Dynamic Bone add-on.  I've had some good success with hair and cloth rigged using it.  You do need a bit of setup to get it working, but it's a nice simple implementation of basic dynamic physics.

Conceptually, yes.  You would only need to alter how it displays (last section in first post), since it's not using the new Unity UI system.

Yeah, with Mecanim you'll need to adjust some values for the imported animation files.  I find the values listed in this post best.  Have a test and see how it goes, that should resolve the feet and rotation issues.

360 issues are usually due to Quaternion / Euler differences when creating rotations.  Since you're using Blender, this is actually fairly easy to avoid.  Just make sure you set your Transform's Rotation Mode to Euler instead of Quarternion (which I think is default?).

It does work. But it's better when using Mecanim animation, instead of Legacy.  Since Mecanim mirrors the humanoid animation while Legacy flips the model completely, potentially inverting the polygons in the process.

Check your Input Options.  Look for inputs that are duplicated across both players.

If you're using cInput, also check your configuration in the Options menu while running the game.

Generally, it's a better idea to avoid Root Motion and instead control your character's movement via Self-Applied Forces.  But if you have a good animation, you may want to use it as you will get the full intended motion the animator has created (like for cinematics).

There are 3 things to make sure Root Motion works:

1) Your character Hitbox Setup needs to have a bodypart hitbox that is assigned to the root of the rig.  If using the Blender Human Meta-Rig, the object "metarig" should be your Root bodypart.  I believe 3DS Max's is "bip", but I'm not 100%.  The rigs in these packs have "motion" object as the Root bodypart.

2) The animation in question needs to have the correct import settings so the Root Motion still takes place.  I've found the following works best:

3) Lastly, in the Move file's Animation options, set Root Motion on and ensure the same Root bodypart assigned in step 1) is used for your Root node.

If these settings don't work for you, then it's possible the animation's root node isn't correctly set up (usually common when you have an animation created separate from the model).  Try assigning the root node in the import settings, under the Motion drop down.

There's a few things to check, but since it's active for so long (which rules out most of the FPS related stuff), my guess is you have 3D hitboxes on and the bodypart it's attached to isn't 0 in z axis?

Oh, that's actually a good question.  I don't have the time to try it now myself, so sorry I can't be help at the moment.  I'll probably get a chance to revisit this in a few weeks.

My gut says it should all go in CharacterSelectScreen.cs (or your versions of it), but Im' not 100%.

Yes.  Stance Changes.  Just make the new Stance has moves to change back (if you need to).

It's pretty awesome.  I'm disappointed in myself I hadn't heard of it till now.  It's still in Alpha (for 5+ years?), so can crash.  But it also auto saves every 30 seconds or something, so even with the crash there's not much lost.

UFE doesn't save Story Mode wins to PlayerPrefs.  You would need to set this up yourself.  Shouldn't be too hard - when the UFE.WonStoryModeBattle() function is called, just save the current matches to your PlayerPrefs.

I would then also create a Continue option for Story Mode, which you should override the regular StartStoryMode with when there is a current Saved Game (or give the option to start Story Mode again).  Don't forget to ensure the UI is updated to suit.

I also recommend using PlayerPrefsX, since that allows you to save arrays.