Fatalities crashes

[mhallo21d]

Anybody else having this trouble? Game runs fine (heavily modded) in single player, unless I'm in a fight that triggers a Fatalities Event or animation, in which case it crashes every single time. Ideas?

[Roxpace]

Many have the same problem, including me, I found out if I run fast long away from my base I it would stop crash the server. But I need to use my base also ;)

[Estevan Valladares]

This problem might be related with the stacking problem.
When you are fighting, it is usually happening "damange" and changes in the "hate list".
Both things are poorly coded right now, so when they fill up, the system keeps adding to them and the game crashes.
However, this can also happen by any out of date mods using hard edits on outdated assets too.

[Xevyr]

Originally posted by mhallo21d:

Anybody else having this trouble? Game runs fine (heavily modded) in single player, unless I'm in a fight that triggers a Fatalities Event or animation, in which case it crashes every single time. Ideas?

Yes, you most likely have a mod that has either the player character asset directly saved or the NPC asset.

[mhallo21d]

Thanks everyone for your replies, and sorry I didn't respond sooner, work travel. So I don't know nearly as much about the code as you all do (and hats off to you!), so could you give me and idea on the best way (short of trial and error) to figure out which mods might be the problem?

[Estevan Valladares]

Start by checking in the main game menu > Mods which mods have a check mark and which does not. Probably the ones which do not have are not updated.
I dont think the launcher list shows it. Only the ingame list I know does.

[Arath Hunter]

If it's still a problem you can at the very least disable Fatalities in the options under combat. Doesn't solve the problem itself, but at least you'll avoid crashes that way as a option.

[Abood]

I have this problem or something similar, turns out its the Crassus mod (idk if spelling is right, but its mod where u can put corpses ona cross or pole).

[mhallo21d]

Thanks everyone for your help. Those of you who really take the time to dig into what makes the game tick are a godsend to those of us who are more casual players (or, frankly, just not as bright)! And a special thanks to [QMX] Abood: you nailed it, for whatever reason Crassus seems to be the culprit! Guess I'll just have to live without decorating my castle with my fallen foes...

[Arath Hunter]

Originally posted by mhallo21d:

Thanks everyone for your help. Those of you who really take the time to dig into what makes the game tick are a godsend to those of us who are more casual players (or, frankly, just not as bright)! And a special thanks to [QMX] Abood: you nailed it, for whatever reason Crassus seems to be the culprit! Guess I'll just have to live without decorating my castle with my fallen foes...

Glad you got it sorted out! Shame for that mod, looks like it hasn't been updated for a year, and no one has had luck with contacting the mod author

[BondageSpider]

Can this error happen if I'm subscribed to workshop mods but not actually using any at the moment?

They're all deselected in the launcher at the moment, because I haven't visited my friend's heavily modded server in a week, I've gone back to my vanilla solo game worlds to catch up on some Journey stuff. Whenever I attempt a Fatality, I get a weird error about "Emote 0" not being found, and then I can't draw or use weapons anymore, until I exit and restart.

I can post a screenshot of the error if it helps.

[BondageSpider]

This is what I kept getting last night every time my character attempted a Fatality.

https://steamcommunity.com/sharedfiles/filedetails/?id=3240346121

EMOTE: 0 NOT FOUND IN THE DATA TABLE - TARGET: BASEPLAYERCHAR_C_1

edit: Verified files and now Fatalities seem to be working again, because reasons?

I'll update if it happens again.

[Lunar Purge]

Originally posted by BondageSpider:

This is what I kept getting last night every time my character attempted a Fatality.

https://steamcommunity.com/sharedfiles/filedetails/?id=3240346121

EMOTE: 0 NOT FOUND IN THE DATA TABLE - TARGET: BASEPLAYERCHAR_C_1

edit: Verified files and now Fatalities seem to be working again, because reasons?

I'll update if it happens again.

Getting this as well, verifying files did not work for me nor do I have mods, so not sure what to do about this yet.

[Estevan Valladares]

Verifying files work sometimes in some errors not because it is the solution, but because any problem that results from stacking up of errors will "reset" because files were verified, and therefore some aspects of the game "cleared", but they will eventually come back, the same way they started happening after a while.
Verifying files is not a "magic solution" as some people seem to imply.
Reinstalling does a broader "reset", but essentially not solve any problem that might occur in the course of playing the game because you were playing the game. Meaning changes to the game data that occur because you are playing the game, not flaws in the installed original file.

For those, you need to get the logs and learn what problem it specifically is. You might have the exact same action causing an error 3 times, and all of them for different reasons, for example.

There needs to be known what is the error specifically, and if that error is "always" the same.

[Lunar Purge]

Originally posted by Estevan Valladares:

Verifying files work sometimes in some errors not because it is the solution, but because any problem that results from stacking up of errors will "reset" because files were verified, and therefore some aspects of the game "cleared", but they will eventually come back, the same way they started happening after a while.
Verifying files is not a "magic solution" as some people seem to imply.
Reinstalling does a broader "reset", but essentially not solve any problem that might occur in the course of playing the game because you were playing the game. Meaning changes to the game data that occur because you are playing the game, not flaws in the installed original file.

For those, you need to get the logs and learn what problem it specifically is. You might have the exact same action causing an error 3 times, and all of them for different reasons, for example.

There needs to be known what is the error specifically, and if that error is "always" the same.

So for me this seems to only happen indoor areas, Dungeons and the like. Outside it's perfectly fine and working, in dungeons I get that same error someone posted a image of before. Test more then 3 times to make sure, only dungeons so far.

[Estevan Valladares]

Originally posted by Lunar Purge:

Originally posted by Estevan Valladares:

Verifying files work sometimes in some errors not because it is the solution, but because any problem that results from stacking up of errors will "reset" because files were verified, and therefore some aspects of the game "cleared", but they will eventually come back, the same way they started happening after a while.
Verifying files is not a "magic solution" as some people seem to imply.
Reinstalling does a broader "reset", but essentially not solve any problem that might occur in the course of playing the game because you were playing the game. Meaning changes to the game data that occur because you are playing the game, not flaws in the installed original file.

For those, you need to get the logs and learn what problem it specifically is. You might have the exact same action causing an error 3 times, and all of them for different reasons, for example.

There needs to be known what is the error specifically, and if that error is "always" the same.

So for me this seems to only happen indoor areas, Dungeons and the like. Outside it's perfectly fine and working, in dungeons I get that same error someone posted a image of before. Test more then 3 times to make sure, only dungeons so far.

Gotta see the logs to see what specifically happen.
There are 4 things that one needs to know to be more certain what happens:
- Script Stack
- The numbers of the last registers (the bunch of lines below the script stack list)
- The block which the error was triggered (also in the bunch of lines below the script stack list)
- And the error itself, which is in bunch of lines labeled "fatal error".

It is generally the last two dozen or so lines in the log at the time of the crash.