WiTP CTD

[Spliffmaker]

Freshly downloaded v1.50, applied 1.804 comprehensive patch and then 1.806 update.

Running on Win XP SP3. This hardware has run the game successfully before, however, this is a fresh (well ok, 3 months old) install of XP.

Getting a random CTD in WiTP when clicking buttons, random button every time. It only seems to be happening when clicking buttons on a unit / base control screen. Like, for example, 'new TF', or 'load supplies', or even 'done'. Not recreatable on reload of game but will happen again within 5-10 minutes. No errors seen while processing turns, just when attempting to control stuff.

Game exits to windows error reporting.

[jwilkerson]

I'd try re-installing first. Hundreds if not thousands of games have been run on these versions with no issues like you're describing - so high probability that there is some local issue.

First, try just installing v1.50 and no patches. Then drive around in the game and see if you get the same behavior and let us know. Then we can proceed accordingly.

[Spliffmaker]

ok, reinstalled v1.50, applied no updates.
 
Still doing it, this time I loaded a diff campaign to the epic full one, set off some air patrols with no crashing and hit turn process, the crash happened when I clicked....um....done or close or exit or whatever the button is called on a combat summary.
 
 
The windows error I'm getting is 0xc0000005 - Memory access violation.   Now, I would say this points to dodgy ram in my machine but this is the only software I'm getting a crash of this type with.  Other games such as M2:TW, ARMA2, Civ, Silent hunter 4, etc, are working fine.
 
 

[Spliffmaker]

I just got a response from matrix support saying reinstall after a reboot and turn off anti-virus.

What ****** difference AVG makes to an install is beyond me.

The email also goes on to say I should run it as administrator in win XP PS2 compatibility mode. They seem to be under the impression I'm running Vista.......


Does anyone in support actually read problem descriptions these days or do they all just cut & paste the automatic response?

[Spliffmaker]

Ok.  I reckon it's either going to be something to do with a function call the program makes that causes the crash or a DEP thing. 

The crash happens after the button gets highlighted in yellow (when you click on it) but before the click noise gets played through the speakers.  It's possible the function call to play the click is causing my sound card driver to throw a fit, but I'm grabbing at straws here.  Going to find updated soundblaster drivers and try it out, I've also got on board sound (currently disabled) I can try instead.

If this has no effect, considering turning off data exception prevention in my boot.ini.  Dunno, does WiTP use executable memory?

[rtrapasso]

Antivirals can mess up installs - the mechanism varies... but actually, your problem MIGHT be SP3... did you recently install it? i have deliberately not installed SP3 because of the numerous problems reported with the game.

[jwilkerson]

I have SP3 now (for about a month) and haven't had any problems.

Bob, what about that "NOSOUND" fix from way back when? I actually don't know anything about that - but could that help this issue?

[Spliffmaker]

First of what....numerous problems reported with this game and SP3?


And secondly, what NOSOUND issue?

[rtrapasso]

ORIGINAL: jwilkerson

I have SP3 now (for about a month) and haven't had any problems.

Bob, what about that "NOSOUND" fix from way back when? I actually don't know anything about that - but could that help this issue?

Not everyone had issues with SP3, but many people did... there were a number of different issues... Spliffmaker, if you are are interested, you'd have to comb back through the Tech Support subforum... at one point, someone claimed there weren't any issues, so i found around 10 different threads (iirc) with SP3 problems... i have a list in there somewhere.

Perhaps the NOSOUND fix could work... trying it might be useful, but who knows?

Problems can arise with the codec and/or sound board drivers... to get around them, rename the SOUND folder to NOSOUND. i think you will lose your sound effects... if it works, then great... if not, just rename the folder to its original name (SOUND).

EDIT: if the NOSOUND solution works, you know you have a codec/soundboard driver problem, and you can work on fixing that.

[Spliffmaker]

Thank you sooooo much.

The NOSOUND fix has worked, I can play the game again.  . 



I'd really like to try just disabling the click that gets played when a button is...er...clicked, any idea which of the sound files in the SOUND directory is used for this?

[rtrapasso]

nope... you'd have to fiddle around trying them.

[jwilkerson]

ORIGINAL: Spliffmaker
The NOSOUND fix has worked, I can play the game again.  . 

I got the hint from re-reading your post!
[:)]