Jittery animation / movement in shooter 2.50

[jasonweise]

Since updating to 2.50 I have noticed that animations seem to be very jittery.
I had thought at first it might be the invector camera controller so swapped out for Cinemachine camera and found the same issue.

It is quite easy to reproduce and does it with the standard Invector Shooter Melee player prefab and have tested on 2019.3 and 2020.1a with same results (it was fine before I updated to 2.50).

To reproduce, grab the invector Shooter prefab (character) and Invector Camera (either prefab or add the camera controller to main camera).

Now orbit the player whilst walking forward or running and you will see the sholders and arms jitter. If you slow the walk speed down to 1.0 you notice it even more.

I thought it might be my project so created a completely blank project and imported invector shooter 2.50, as soon as I added character to the demo scene straight away you see the jitter once playing.

Any ideas on what might be causing this?

I own OOTII MC as well and imported it to the same project afterwards to be sure it wasn't something odd with any of the projects and it was buttery smooth.
I only want to use Invector so thought I'd see if anyone else has experienced this?

[Invector]

Are there any errors in the console? you can record a video showing the issue?
It seems to be buttery smooth here... just imported from the store and we didn't receive any complains lately, in fact, it should be MORE smooth than before since we update the move character method

[jasonweise]

Dec 23, 2019 23:17:57 GMT Invector said:

Are there any errors in the console? you can record a video showing the issue?
It seems to be buttery smooth here... just imported from the store and we didn't receive any complains lately, in fact, it should be MORE smooth than before since we update the move character method

@invector, I have tried again by installing fresh with brand new clean projects in 2019.3.0f3 and 2020.1.0a17 (not using alpha version but thought I'd test it anyway), both show the jitter still I am referring to.
I have found that it appears to be most pronounced after setting to "default walk" and lowering the walk speed to 1.0f (2.0f is too fast for my game).
When I first opened the demo scene and hit play it did look nice and smooth and thought, hmm Invector was right.... but then I hit stop changed to default walk and speed to 1.0f and BANG, twitching started straight away.
If you have a look at the video you can see the shoulders / upper body and legs twitch, I recorded this instantly after changing walk and speed and nothing else was done.

Hope you can provide some advice.. cheers and Merry Christmas.

PS. I don't believe this will be fps related as the scene was running at ~148fps in that video.. just in case you were wondering.

[Invector]

Very strange... I just test here and it's working fine on both 2018.4 and 2019.3... not jittering issues whatsoever.
I've noticed that your video has a different set of colours and no skybox, did you change any graphics settings?

[jasonweise]

Hi @invector
Thanks for the speedy response, the pink material and sky is just because it is a HDRP project and did a quick upgrade materials so it wasn't all pink LOL.
I have used HDRP with invector for quite some time now with no issues. Do you think this might be the problem? I will try in a standard project as well and report back.

[jasonweise]

@invector
Here is another clean project I just created in standard renderer 2019.3.0f3
Imported shooter 2.50, did nothing other than change to "Walk by default" and drop walk speed to 1.0f.

Jitter happens when walking in circles immediately. It is sooo strange, this only started with 2.50. I thought it was because I originally upgraded my current project to 2.50 but as explained and as per videos, it is happening with 100% fresh projects (both HDRP and as shown here, standard renderer)

[Invector]

I did your exact same test, import on a clean project from the asset store, set to walk by default, speed to 1 all in the shooter demo scene and it's working as expected... It's very curious and we would probably receive more complains if that was an ongoing bug, but at the same time, it doesn't seem that there is anything wrong with your project as well.

How many FPS does your scene run?

[shockwavegamez01]

Dec 23, 2019 3:39:47 GMT jasonweise said:

Since updating to 2.50 I have noticed that animations seem to be very jittery.
I had thought at first it might be the invector camera controller so swapped out for Cinemachine camera and found the same issue.

It is quite easy to reproduce and does it with the standard Invector Shooter Melee player prefab and have tested on 2019.3 and 2020.1a with same results (it was fine before I updated to 2.50).

To reproduce, grab the invector Shooter prefab (character) and Invector Camera (either prefab or add the camera controller to main camera).

Now orbit the player whilst walking forward or running and you will see the sholders and arms jitter. If you slow the walk speed down to 1.0 you notice it even more.

I thought it might be my project so created a completely blank project and imported invector shooter 2.50, as soon as I added character to the demo scene straight away you see the jitter once playing.

Any ideas on what might be causing this?

I own OOTII MC as well and imported it to the same project afterwards to be sure it wasn't something odd with any of the projects and it was buttery smooth.
I only want to use Invector so thought I'd see if anyone else has experienced this?

In your ragdoll you have to select disable colliders. this should fix the problem.

[jasonweise]

Dec 26, 2019 23:12:05 GMT Invector said:

I did your exact same test, import on a clean project from the asset store, set to walk by default, speed to 1 all in the shooter demo scene and it's working as expected... It's very curious and we would probably receive more complains if that was an ongoing bug, but at the same time, it doesn't seem that there is anything wrong with your project as well.

How many FPS does your scene run?

@invector, the HDRP scene was average 148fps and the standard renderer 144fps (interesting HDRP appears to be higher everywhere now days).

Rig is i9@4Ghz
Single 1080Ti
64 GB Ram
1TB M.2 + others
Win 10 Pro

I'm pretty sure it isn't FPS related

shockwavegamez01
Thanks for jumping in as well, it is appreciated. I will have a look when I am back at my PC but I would presume the demo scene should already be configured correctly as I have now tested multiple times in brand new clean projects.
I appreciate the advice though and will doulbe check that and report in as soon as I am able.

[sjmtech]

Looks like the insidious issue which occurs when you are in play mode and the player gameobject is selected.
Make sure you have not selected the controller during play mode.

[Invector]

Dec 27, 2019 0:09:30 GMT shockwavegamez01 said:

In your ragdoll you have to select disable colliders. this should fix the problem.

Dec 27, 2019 8:39:06 GMT sjmtech said:

Looks like the insidious issue which occurs when you are in play mode and the player gameobject is selected.
Make sure you have not selected the controller during play mode.

I tested both and didn't make any difference here , it's still very smooth

[Invector]

One thing that makes the controller very jittering is playing with the Game window not maximized, but that's expected because the editor will consume a lot of power, always hit play with the game window maximized to test performance, or better yet export a build to have real results

[sjmtech]

Tested now in my old home pc...all smooth but selecting the player i see the same issue reported by jasonweise

[Invector]

Dec 27, 2019 16:45:35 GMT sjmtech said:

Tested now in my old home pc...all smooth but selecting the player i see the same issue reported by jasonweise

Yes but like I said this only happens if you don't maximize the game window, the editor will affect the performance and the fps goes crazy 

[sjmtech]

Yes, but the cause is the inspector tab which is hidden by maximizing the game windows...the issue disappears just closing the inspector tab.