I can't get three minutes into the cornfield scenario with out a crash. Sometime the crash comes when I'm not touching anything. Last night I experienced some crashing as well with the beta patch. BTW I did install the final 1.4 first. Disappointed to say the least.

EDIT1: Crashed again (SOW - has stopped working) at the 5:46:17 mark. Seems to crash on any kind of mouse movement.

Tried the second scenario and it crashed again within 5 seconds of starting with no activity on my part.

Until I get a response it's back to Combat Mission.


EDIT2: Tried a sandbox game with an Antietam map Brig vs Brig as Col. Douglas. Finally got the same crash after 10 minutes or so. Going to try Gettysburg and see what happens.


EDIT3: Yea, got a crash on the Culps Hill map playing a Brigade game. Can't play the game right now. Any Suggestions?

As mentioned already in the other thread: Disable mods!

And without posting the content of the SOWGB.log it's nearly impossible to tell what's wrong.

OK, I'm looking in the SOW folder. I don't see a file by that name. What should I be looking for? Sorry, I'm not as technically proficient as most of your posters.
Meanwhile should I disable all mods and re download the patch and Map Pack?

It's in the Work sub-folder.

No, just disable the mods.

OK I think this is it. Off to work now. No crash with mods disabled.

Yes, I can see several mods were enabled in the log. I can see a lot of those mods will probably still work, but like I said in that other thread, disable all mods, enable one at a time to determine the culprit.

Thanks LP. This whole mod issue is odd. Too bad because the mods, to me, are a big part of the whole SOW experience. The scenario packs shouldn't be a problem just the graphic and sound modifications, I would think.

If we had to hold up our development based on every mod released, we would never get anything done and the engine would remain stagnant. We try our best to make sure everything continues working, but we just don't have the resources to verify the mods before we release. I'm sure the mod authors will update soon.

Fine by me. Thanks Norb.

gbs wrote:

If there is a way to crash the game, mod writers will find it. Norb is right, it is much easier for each modder to update his work than have Norb tearing his hair out trying not to impact those mods. As soon as the new SDK is released, I'm sure they'll be updated.

I just noticed that you have the "Blood Mod" active. While this works well in version 1.3 I really don't think you should activate this mod with the new patches.

As stated above, it is in your best interest to disable all mods, and then start by activating one mod at a time.

Just to let you know that you should start a NEW Sandbox game each time. If you are loading a saved game which had other mods active YOU WILL have major problems...trust me your speaking to someone who has bothered these poor folks to no end.

Once I get the patch 1.4 I will be doing a full MOD test to see what works, and what doesn't (I have to keep my website mod section clean, and version proof).

I can do this because I have no life (life of SOWgb that is), and I can disable the patch between 1.3, and 1.4 with no problems.

So give me about 24 hours to download the patch, and I will soon have your answers...or until NSD decides to keep posting new patches between now, and then.

Okay, since I run version 1.3.10, and run 1.4 as a mod I can switch between versions without much trouble, well it's as easy as pickings one's nose actually...okay forget that you read that.

Okay I have tested the Bloodmod, and Bloodbath III, and both work perfectly in 1.3, but in version 1.4 (beta, still downloading latest version) these mods DO NOT work. The graphics of these two mods do not show up, but they haven't caused me any CTD's, so there isn't much point in having them active until I can figure out how to use the Texture Packer so I can update my blood mod graphics.

I have tested these two mods with 1.3, and 1.4 with the EXACT same options.