Climbing on and Riding a dragon bug (Fixed)

[Filip97x]

During the Dragonborn DLC when I get Bend Will in this playtrough I have a bug where when I try to climb on a dragon he just flies off and my character just stands there stuck to the ground in the pose of riding the dragon, my camera gets stuck and I can't move or anything all I can do is just press the shout butten that makes the dragon shout from where I even even tho it is flying around and I am stuck to the ground.
I have read that there is a fix by deleting the "skeleton.nif" which is located in data/meshes/actors/dragons/characterassests
The problem is I do not have that file
(I tried extracting meshes again with the BSAopt to add that file and delete it and it still doesn't work)
I tried deleting the Mod Realistic Ragdolls and Force and it still doesnt work even vereficiating game files which still didn't help
Also tried turning off every skelet mod and dragon mod and still nothing
Anybody know how I can fix this ?

Solution:

Ok after trying out everything even reinstalling Skyrim completly with all the same mods but this time using Mod Organizer 2 it was much easier on a clean save where I gave myself with console commands the shout to see what could be cosing the issue and the thing at issue was the mod "character behaviour enhanced"
Removied it and it worked well
So for anyone who has the same issue and where the case is not the skeleton.nif or the realistic ragdoll mod or any dragon mod this is another mod that can couse it

[Ilja]

Have you previously turned off any mods for ongoing game? While this is usually skeleton.nif issue for dragons, it might be a Papyrus issue as well. Rare one, but plausible.

[Filip97x]

Originally posted by Ilja:

Have you previously turned off any mods for ongoing game? While this is usually skeleton.nif issue for dragons, it might be a Papyrus issue as well. Rare one, but plausible.

Yes I did try to turn off all the Mods besides the esential ones that are esential for my save but it still has the same bug (It might be a Papyrus problem or script issue coz I also had a problem when I went to Solsthaim for the first time the boat didnt come with me and I was stuck there but fixed that wih console commands by skipping that part)

[Ilja]

That does start to sound like something went wrong at some point. Game bakes script data to save files, so if any mod using custom scripts got removed or broken (without you noticing it got somehow broken), then Papyrus might be a mess.

Easy to check. Make these changes to your skyrim.ini file in Documents > My Games > Skyrim. (Or in your ...Mod Organizer > Profiles >ProfileName.)

bEnableLogging=1
bEnableTrace=1
bLoadDebugInformation=1

This will create a Papyrus log in to your C:\Users\<UserName>\Documents\My Games\Skyrim\Logs\Script folder, when you run the game. Play once again the part, where you fail to ride the dragon.

The Papyrus log is not a crash log. It monitors script behavior. We can use it to see, if game is dumping stacks due to script issues.

Edit: You can remove those edits in Skyrim.ini, once log has been created. They will just create extra stress to system, if left active.

[Filip97x]

Originally posted by Ilja:

That does start to sound like something went wrong at some point. Game bakes script data to save files, so if any mod using custom scripts got removed or broken (without you noticing it got somehow broken), then Papyrus might be a mess.

Easy to check. Make these changes to your skyrim.ini file in Documents > My Games > Skyrim. (Or in your ...Mod Organizer > Profiles >ProfileName.)

bEnableLogging=1
bEnableTrace=1
bLoadDebugInformation=1

This will create a Papyrus log in to your C:\Users\<UserName>\Documents\My Games\Skyrim\Logs\Script folder, when you run the game. Play once again the part, where you fail to ride the dragon.

The Papyrus log is not a crash log. It monitors script behavior. We can use it to see, if game is dumping stacks due to script issues.

Edit: You can remove those edits in Skyrim.ini, once log has been created. They will just create extra stress to system, if left active.

Ok thanks made the log so what do I look for now what went wrong coz there is a lot written in there

[Ilja]

It is easiest to read with Notepad++, or similar tool that allows you to read such data in correct format. Standard Notepad just makes a mess out of it.

Use search feature and look for dumping stacks. If that is present in the log, then game is trying to process too many script actions at once. This may happen due to presence of too many active scripts at once, or lack of script source (removed mod.)

If such line is present in Papyrus Log, then we know that scripts are not running correctly and that is preventing you from riding the dragon.

If not, then this might still be a skeleton issue, where one of the dragon skeleton.nif files got overlooked.

[Filip97x]

Originally posted by Ilja:

It is easiest to read with Notepad++, or similar tool that allows you to read such data in correct format. Standard Notepad just makes a mess out of it.

Use search feature and look for dumping stacks. If that is present in the log, then game is trying to process too many script actions at once. This may happen due to presence of too many active scripts at once, or lack of script source (removed mod.)

If such line is present in Papyrus Log, then we know that scripts are not running correctly and that is preventing you from riding the dragon.

If not, then this might still be a skeleton issue, where one of the dragon skeleton.nif files got overlooked.

Well there is no dumping Stack but there is errors and freezing

[Ilja]

VM... stuff is related to Virtual Machine. Those appear in to log, when system prepares to stop, actually stops or starts again. This happens, when you open the game menu and scripting system stops in the mean time. Those are not a problem.

Reading errors is a bit of an form of art. Papyrus writes everything that is missing as an error. This happens for soft dependencies as well, so to know what is an actual error is a matter that just requires knowing what is a relevant error.

The important part was that there were no stacks getting dumped. That would mean that we are still likely dealing with a skeleton issue and Papyrus itself has not broken.

In short: your current game sounds like it is in playable state, once the problem gets solved. If Papyrus would have been dumping stacks, then I would have recommended starting a new game entirely. No need for that now.

Hmm... what the heck could be wrong then? Could you post your load order for us? We might spot a mod potentially causing the problem.