1.27 update constant crashing

[xKanekix]

High there y'all,

Been playing in Vanilla and been getting constant crashing with this new update from my main save file that was module 1.6 to whatever this new update is. I tried Uninstalling, verifying file integrity as well as turning off my antivirus but to known avail. Can anyone help me trouble shoot this, would rather not have to start a new campaign after all the work I've put in for this campaign.

[Duh]

We are working on some stability fixes that will hopefully be pushed out relatively soon. If you would like to continue your current campaign without delay, you may consider opting into the 1.1.6 steam beta branch - assuming that was the last stable version for this save (right click the game in library > select properties > betas > v1.1.6).

[mikendall77]

Been having the same issue since the last update. Have jumped through all these hoops as well. Nothing stops the crashing. Glad to hear fixes will be pushed out soon though! Really wanting to get back to my campaign!

[CZ-SK | Armen]

I have the same isssue during entering smithy ... crash every 20 minutes

[RaccoonDoggo]

Same here, entering smith crashes game - even for fresh new game

[Clovis Sangrail]

I've been popping in and out of the smith for several days now, and not a single problem. Multiple locations, only one of which I actually owned, and everything is copacetic.

New game after mainlne update to 1.2.7 with no mods ever.

[Elite665]

no issues here with my game. And it has 4 mods that all carried over from the most recent beta.

[TheMooneyClan]

Originally posted by Duh:

We are working on some stability fixes that will hopefully be pushed out relatively soon. If you would like to continue your current campaign without delay, you may consider opting into the 1.1.6 steam beta branch - assuming that was the last stable version for this save (right click the game in library > select properties > betas > v1.1.6).

Please inform your Dev team to stop regularly changing function names..etc that mod's use. Why are you constantly refactoring your code base in a way that nearly every single mod requires updating due to you screwing with established code base.

I understand about refactoring code to an extent but this game has the player base it does due to the modding community. You can refactor code without breaking what's already been established.

Also please inform your team to look to the modding community for idea's on new features to be added to the base game. The mod's turn this from a great game into an amazing one.

[Cassian]

Originally posted by Clovis Sangrail:

I've been popping in and out of the smith for several days now, and not a single problem. Multiple locations, only one of which I actually owned, and everything is copacetic.

New game after mainlne update to 1.2.7 with no mods ever.

good for you?

why do always post the most useless unhelpful statements.....

obviously because the Great Clovis doenst have a crash it must not exist.....

[catbox99]

In other words, for the best, most stable game experience, take the DEVELOPERS ADVICE and stay away from their update. Rollback to before the annoying shield garbage. *sigh*

[Ruffio]

Originally posted by catbox99:

In other words, for the best, most stable game experience, take the DEVELOPERS ADVICE and stay away from their update. Rollback to before the annoying shield garbage. *sigh*

He said roll back to the most stable version for your "save".... Been playing on the 1.2.x beta branch since it was released, and have no issues with my saves. If it's a issue with your save, then either roll back or start a new game.

[xKanekix]

Originally posted by Duh:

We are working on some stability fixes that will hopefully be pushed out relatively soon. If you would like to continue your current campaign without delay, you may consider opting into the 1.1.6 steam beta branch - assuming that was the last stable version for this save (right click the game in library > select properties > betas > v1.1.6).

Thank you for the advice, game runs without issues now. Shame I can’t play the newest update at the moment but hopefully that fix comes soon so I can experience it!

[srtosco]

Why even update it if its not properly tested? Constant crashing is expected in a beta why make that the live version at all?

[Stevie Lee]

Originally posted by xKanekix:

High there y'all,

Been playing in Vanilla and been getting constant crashing with this new update from my main save file that was module 1.6 to whatever this new update is. I tried Uninstalling, verifying file integrity as well as turning off my antivirus but to known avail. Can anyone help me trouble shoot this, would rather not have to start a new campaign after all the work I've put in for this campaign.

I've had crashes entering smithy twice, having never experienced any crashes previously.

[Normski]

I was having the same issue but managed to fix it by removing mods I had manually added. Even running with all mods turned off (in game) resulted in crashes so I deleted the stuff in Modules and then verified my game cache and it resolved it.

[Cantung]

Originally posted by Clovis Sangrail:

with no mods ever. [/q

Originally posted by Cassian:

Originally posted by Clovis Sangrail:

I've been popping in and out of the smith for several days now, and not a single problem. Multiple locations, only one of which I actually owned, and everything is copacetic.

New game after mainlne update to 1.2.7 with no mods ever.

good for you?

why do always post the most useless unhelpful statements.....

obviously because the Great Clovis doenst have a crash it must not exist.....

But he is so pure ... so unsullied by mods... Bend your knee to his purity, and feel shame.