Button mouseover-induced CTD... huh? -1 reply

Please wait...

C38368

...burning angel wings to dust

50 XP

14th February 2004

0 Uploads

5,013 Posts

0 Threads

#1 13 years ago

As the title suggests, I've just stumbled across a previously-unknown problem where both FH and BF42 will execute a lovely CTD whenever I move the mouse over any button on the first screen to come up when you load the game. Because it does this regardless of which game I load, I suspect that it's a hardware issue of some kind on my end of things. I'm asking for help here because I have more faith in the FH community than in the BF42 community-at-large.

I'm running BF42 v1.6, and I think FH v0.67a. Not certain on the last one; it's been quite some time since I've loaded FH, and I'm wanting to get back into it. I was actually jumping in to check when I discovered this crash-prone behaviour.

Here's the kicker: since the last time I got into FH, I've made numerous changes to my system, including: -Swapping my ABIT IC7-MAX3 out in favour of an ASUS P4C800-E Deluxe -Pulling my SB Audigy 2 in favour of an M-Audio Revolution 5.1 (set, at the moment, to use coax S/PDIF out) -Replacing an ageing Gigabyte Radeon 9600XT with an MSI 6600GT -I've also reinstalled Windows at least once, and moved the swap file to another drive -I've also moved to an LCD monitor for the time being, and running Windows at 16x12, but BF42/FH is defaulting to something smaller ATM--1280x960, I think

I'm checking on drivers right now, but I seem to recall FH having worked on this setup a couple months back. Right now, the soundcard is my primary suspect, but I'm putting out the call for anyone who may have some insight into this, just in case I'm either overlooking something, or there's a bit of trivia about FH that I'm not privy to.

Thanks folks!




pvt. Allen

I would die without GF

50 XP

20th July 2005

0 Uploads

5,654 Posts

0 Threads

#2 13 years ago

Well, I can't help you with fixing this issue but I can tell you that FH should run without such a problems on your PC. As for the installation it should be like this: Bf1942->Bf parch v. 1.6->Bf patch v. 1.61b->FH 0.65 #1->FH 0.65 #2->FH 0.65 #3->FH 0.67->FH 0.67a->and FH fan map packs if you wan't additional maps, there are FH fan map pack 1, 4, and 5.




C38368

...burning angel wings to dust

50 XP

14th February 2004

0 Uploads

5,013 Posts

0 Threads

#3 13 years ago

I yanked my installations of FH and BF42 this afternoon and reinstalled everything, including both expansion packs (eh, why not--at least I've got the art assets for them), like so: BF42>RTR>SWWWII>patch v1.61b. On the FH side, I then did the standard .65 (in order--can it be done otherwise?) >.67>.67a

Sadly, it's still doing it. However, I can't seem to get analogue audio to function properly out of the Revo, so I'm going to try the onboard tomorrow, or perhaps drop the A2 back in.

Slightly associated question, which I cannot recall the answer to: In FH, when you mouseover a button, does it depress (or appear to), or does that require a mouseclick event? I ask because moving the mouse over a button causes it to change appearance to a "clicked" state. This in turn lead me to suspect that BF42/FH doesn't like my mouse (not likely) or it's crashing when a second sound tries to play.




Real-BadSeed

Science experiment

50 XP

5th December 2004

0 Uploads

3,799 Posts

0 Threads

#4 13 years ago

try reinstalling your mouse driver




C38368

...burning angel wings to dust

50 XP

14th February 2004

0 Uploads

5,013 Posts

0 Threads

#5 13 years ago

I don't think it matters much to anyone, but for posterity's sake: BF42 in general does not paly nicely with the M-Aduio Revo 5.1. Presumably, this holds for other M-Audio cards. Buggered if I know why, but changing the default sound device to something else (SoundMAX in this case, as I can't get my damn A2 working again) solves it.




MG42Maniac

A man of dubious moral fibre

50 XP

28th May 2003

0 Uploads

3,932 Posts

0 Threads

#6 13 years ago

I had an awful problem with my old PC where FH would CTD as soon as the menu loaded up, I suspected it was Audio hardware related ( BF sucks in this department). I tried pretty much everything short of a full windows reinstall ( family PC) but to no avail. In the end I built myself a PC and put in an Audigy 2 ZS and i've had to problems with this PC. But the other PC still has this error after over 1 year.