AH locking up

[Elfie]

AH is locking up sometimes when I alt/tab out to check on things while flying to target areas or (currently) while trying to get vox working.

I'm using Windows Vista Premium.

[Skuzzy]

Need a DXDIAG output for this one.

[Denholm]

Early long-shot: You have AH installed in the default location (C:\Program Files\HTC\Aces High II\) and Vista is moving some of the game files around causing the game to lock-up.

If that's the case, part or all of the solution lies in you moving or re-installing AH to a new directory, for example: C:\games\HTC\Aces High II\

[Skuzzy]

Yes, placing the game in the dreaded "Program Files" folder will cause all manner of problems due to all the things Vista does when you have a file in there.

Also note, if the computer is a dual-core AMD CPU, you have to run the game in "Windows 98/Windows ME" compatibility mode.  If the computer has an NVidia video card, make sure to get the latest driver as NVidia is still having nightmares getting thier drivers stable under Vista.

[drdeathx]

If you have xp, is it better to have AH is a different folder?

[Skuzzy]

XP does not sniff on the "Program Files" folder as much as Vista does, but it does sniff on it.

On my new computer, I just installed everything outside of "Program Files".  Seems a happier camper.

[Elfie]

Yes, placing the game in the dreaded "Program Files" folder will cause all manner of problems due to all the things Vista does when you have a file in there.

Also note, if the computer is a dual-core AMD CPU, you have to run the game in "Windows 98/Windows ME" compatibility mode.  If the computer has an NVidia video card, make sure to get the latest driver as NVidia is still having nightmares getting thier drivers stable under Vista.

ewww.....How do I make AH run in compatibility mode?

I didn't install it to the default directory either, I installed it to c:\games\AH

[Skuzzy]

Here is the instructions on getting the game configured to run in compatibility mode.  It is the only way to work around a bug in the dual-core AMD CPU running Vista.

[Elfie]

Thanks Skuzzy, I'll call you tomorrow on the vox issue. I'm sure you can't wait to deal with that one. 

[Skuzzy]

Thing about VOX is there is not a lot I can do.  There is just very few parameters required to make it work.

1)  The mic has to be the default recording device.
2)  Try the "Use Wave In" option if it does not work.
3)  Make sure there is no firewall blocking inbound connections to the game.
4)  Set the "V" channel to "101" for normal operations.

That's it.

[Elfie]

Thing about VOX is there is not a lot I can do.  There is just very few parameters required to make it work.

1)  The mic has to be the default recording device.
2)  Try the "Use Wave In" option if it does not work.
3)  Make sure there is no firewall blocking inbound connections to the game.
4)  Set the "V" channel to "101" for normal operations.

That's it.

I don't see anywhere in windows to make it the default device, it's the only mic, so shouldn't it be default by.....well....default? heh

[Denholm]

Start>Control Panel>Sounds and Multimedia>Audio

Check to see if your mic is listed as the default recording device. Then check the volume to see if it's all the way up. Afterward just press OK and your changes are saved.

[Skuzzy]

Careful with the mic volumn.  If the gain is too high, it can get garbled.

[Elfie]

Start>Control Panel>Sounds and Multimedia>Audio

Check to see if your mic is listed as the default recording device. Then check the volume to see if it's all the way up. Afterward just press OK and your changes are saved.

Got that part. I even shut off my firewall completely and still the only time the vox works properly is when I tune the vox channel to myself. Then I get the channel beeps and I can hear myself. When I tune to say...101, I no longer get the channel beeps and no one can hear me. Same thing applies to range channel. I can however, hear everyone else just fine.

Maybe this onboard sound is just to crappy?

[Skuzzy]

Sounds like you are behind a router and the firewall in the router is configured to allow established connections to come back through, but it will not allow an external asynchronous connection through, or the router does not support NAT over UDP properly.