The dreaded T pose....

[amenshawn]

I started a new mod list with a fresh install of SkyrimSE, but despite running FNIS after loading animations, I keep getting major issues when starting anew game.  The wagon ride intro sounds all play as normal, but the camera POV is down at the fllotboard of the driver's area of the wagon, and there are no NPCs in either of the wagons as they make their way down the hill.  After trying to rerun FNIS several times, I used the free cam to look around at everything in the area to see what else was behaving wrong.  The animals are all fine, but all the NPCs in Helgen are frozen in place in a T pose, so I know I did something to the physics somehow.  All my mods are current versions and Vortex has green lights down the list for all mod conflict resolutions.  I've double checked all my mod requirements.  Given my brain is crap I've probably overlooked something simple and just can't remember it.  Anyone else run into this, and if so, how did you fix it?

[travelmedic]

try posting a pic of your fnis output, maybe we'll see something you've missed

[KoolHndLuke]

And FNIS gave you no missing animation file warnings? Strange. Did you do a consistence check? Hard to tell anything without your mod list/load order. Best guess would be you're missing a master somewhere.

[Shadowbroker3495]

You should run FNIS before creating new game.

 

Try to run FNIS with HKX file check option activated.

 

Try to post load order list. Mod load order does matter.

 

While debugging, you should use Live Another Life mod to avoid slow default game intro.

 

[anjenthedog]

In addition to what Shadowbroker3495 said, make sure to check the skeleton arm fix in FNIS, just in case.

 

And make sure your skeleton is up to date (and using an SE skeleton of course)

[amenshawn]

Got it sorted out.  FNIS creature pack 7.6  is the problem.  Had to roll back to 7.0 and now everything loads and runs as it should (so far anyway).

 

Apparently I'd been staring at it for too long to figure out what the issue was.  FNIS generated a warning and it just didn't register with my brain that FNIS has to be problem free to work.  Wetware issue as opposed to a software issue.  Happens a lot to me and I should learn to just walk away until I can recognize the problem, especially when the solution is a simple fix. 

 

Thank you guys for the replies.