Essentially, the game crashes roughly 5-10mins after I load a new game OR start from a saved game.
What I've done (Based on my previous kenshi experience)
1) Reinstalled the game
2) Deleted all saves and did a new game
3) Did an import prior to deleting all saves.
I've attached the crash report.
Game crashes roughly 5mins after playing new game or Saved game.
- Attachments
-
- crashDump1.0.68_x64.zip
- Crash Dump
- (518.79 KiB) Downloaded 243 times
Was able to narrow down the cause of the crash. When I attempt to build a storm house it always crashes at the same point:
Log shows the following:
15:43:59: WARNING: Storm_House_01_Door.mesh is an older format ([MeshSerializer_v1.40]); you should upgrade it as soon as possible using the OgreMeshUpgrade tool.
15:44:02: Mesh: Loading Storm_House_01_Interior.mesh.
15:44:02: Texture: construction.dds: Loading 1 faces(PF_DXT5,64x64x1) with 4 custom mipmaps from Image. Internal format is PF_DXT5,64x64x1.
15:44:02: Mesh: Loading Storm_House_01_Interior_Floor.mesh.
15:44:02: Mesh: Loading Storm_House_01_InteriorStairs.mesh.
15:44:04: Mesh: Loading ringo2_sheath.mesh.
15:44:04: WARNING: ringo2_sheath.mesh is an older format ([MeshSerializer_v1.8]); you should upgrade it as soon as possible using the OgreMeshUpgrade tool.
15:44:05: Mesh: Loading cleaversword.mesh.
15:44:09: Mesh: Loading jitte01_sheath.mesh.
15:44:09: WARNING: jitte01_sheath.mesh is an older format ([MeshSerializer_v1.8]); you should upgrade it as soon as possible using the OgreMeshUpgrade tool.
15:44:09: Mesh: Loading jitte01_bare.mesh.
15:44:09: WARNING: jitte01_bare.mesh is an older format ([MeshSerializer_v1.8]); you should upgrade it as soon as possible using the OgreMeshUpgrade tool.
15:44:12: Mesh: Loading arkhaircut01F.mesh.
15:44:12: Skeleton: Loading arkhaircut01F.skeleton
15:44:12: WARNING: arkhaircut01F.mesh is an older format ([MeshSerializer_v1.8]); you should upgrade it as soon as possible using the OgreMeshUpgrade tool.
15:44:12: Texture: Scorch_F_B_006.dds: Loading 1 faces(PF_DXT5,64x64x1) with 4 custom mipmaps from Image. Internal format is PF_DXT5,64x64x1.
15:44:14: Mesh: Loading FoxTyoutyuo01new.mesh.
15:44:14: Mesh: Loading nodachi_sheath.mesh.
15:44:14: Mesh: Loading nodachi_bare.mesh.
15:44:14: Mesh: Loading Burst Ranger.mesh.
15:44:14: Mesh: Loading Burst Ranger_Loaded2.mesh.
15:44:14: Mesh: Loading Burst Ranger_Unloaded2.mesh.
Log shows the following:
15:43:59: WARNING: Storm_House_01_Door.mesh is an older format ([MeshSerializer_v1.40]); you should upgrade it as soon as possible using the OgreMeshUpgrade tool.
15:44:02: Mesh: Loading Storm_House_01_Interior.mesh.
15:44:02: Texture: construction.dds: Loading 1 faces(PF_DXT5,64x64x1) with 4 custom mipmaps from Image. Internal format is PF_DXT5,64x64x1.
15:44:02: Mesh: Loading Storm_House_01_Interior_Floor.mesh.
15:44:02: Mesh: Loading Storm_House_01_InteriorStairs.mesh.
15:44:04: Mesh: Loading ringo2_sheath.mesh.
15:44:04: WARNING: ringo2_sheath.mesh is an older format ([MeshSerializer_v1.8]); you should upgrade it as soon as possible using the OgreMeshUpgrade tool.
15:44:05: Mesh: Loading cleaversword.mesh.
15:44:09: Mesh: Loading jitte01_sheath.mesh.
15:44:09: WARNING: jitte01_sheath.mesh is an older format ([MeshSerializer_v1.8]); you should upgrade it as soon as possible using the OgreMeshUpgrade tool.
15:44:09: Mesh: Loading jitte01_bare.mesh.
15:44:09: WARNING: jitte01_bare.mesh is an older format ([MeshSerializer_v1.8]); you should upgrade it as soon as possible using the OgreMeshUpgrade tool.
15:44:12: Mesh: Loading arkhaircut01F.mesh.
15:44:12: Skeleton: Loading arkhaircut01F.skeleton
15:44:12: WARNING: arkhaircut01F.mesh is an older format ([MeshSerializer_v1.8]); you should upgrade it as soon as possible using the OgreMeshUpgrade tool.
15:44:12: Texture: Scorch_F_B_006.dds: Loading 1 faces(PF_DXT5,64x64x1) with 4 custom mipmaps from Image. Internal format is PF_DXT5,64x64x1.
15:44:14: Mesh: Loading FoxTyoutyuo01new.mesh.
15:44:14: Mesh: Loading nodachi_sheath.mesh.
15:44:14: Mesh: Loading nodachi_bare.mesh.
15:44:14: Mesh: Loading Burst Ranger.mesh.
15:44:14: Mesh: Loading Burst Ranger_Loaded2.mesh.
15:44:14: Mesh: Loading Burst Ranger_Unloaded2.mesh.
But does it crash when building that stormhouse in vanilla, or only with the mods on? I know you said it was working in vanilla, but that was before you knew the trigger, so I'm wondering if you can perform the trigger in vanilla. Or does it perhaps work if you place it elsewhere, or in a new game?
The act of placing the stormhouse can't be the only trigger condition, as otherwise we'd be flooded with reports of it. So it's gotta be either some specific circumstances in your save, a mod that is altering the stormhouse or something, or a hardware/settings related issue. Doing the tests I mentioned above may help identify what the other conditions are.
If it does trigger in vanilla still, might be worth upload the save itself. That way I can test on my end, see if it's an issue in the save or your machine.
If it is coming from a mod, unfortunately there isn't much that can be done to help identify the problem. The logs and dump don't really often record any information useful for that. Personally, I'd backup the mod list and just test half the mods at a time. Once you identify which half the mod is in, you test half of that half, and so on. Pretty quickly narrows down even huge mod lists.
The act of placing the stormhouse can't be the only trigger condition, as otherwise we'd be flooded with reports of it. So it's gotta be either some specific circumstances in your save, a mod that is altering the stormhouse or something, or a hardware/settings related issue. Doing the tests I mentioned above may help identify what the other conditions are.
If it does trigger in vanilla still, might be worth upload the save itself. That way I can test on my end, see if it's an issue in the save or your machine.
If it is coming from a mod, unfortunately there isn't much that can be done to help identify the problem. The logs and dump don't really often record any information useful for that. Personally, I'd backup the mod list and just test half the mods at a time. Once you identify which half the mod is in, you test half of that half, and so on. Pretty quickly narrows down even huge mod lists.
-
- Information
-
Who is online
Users browsing this forum: Bing [Bot] and 7 guests