Aces High Bulletin Board
General Forums => Aces High General Discussion => Topic started by: Pyro on February 25, 2013, 12:48:57 PM
-
There is a new version of the AH FMOD beta with a download link below. Please use this version for all further testing until a new version is released.
This version attempts to address ticking and device issues.
There is a new diagnostic output file. In your Aces High folder, there will be a file named fmodinit.txt that is created after you run the test version. When reporting a problem, please cut and paste the contents of that text file into your post. It is not necessary to include your dxdiag output.
Thanks for your continued assistance in testing.
Original post with new download link:
In our previous sound system change, we ran into some roadblocks that eventually kept us from implementing a sound event system that allows us more detailed sounds. We're once again looking into moving to a new sound system (FMOD) and need some help with low level testing across multiple platforms. We have a test version that will install in your existing Aces High folder. It should run just the same as your regular Aces High. There are no new sounds or effects in this, this is just to check that everything still works and nothing crashes. There is a small installer download that will install 3 files into your Aces High folder. If you want it will also create a shortcut on your desktop(ahfmod.exe). Run this shortcut instead of your usual Aces High icon to launch the test version. If you have a problem with the test version you can simply go back to launching the game as you normally do.
Here is the link to the download. It is about 4MB. Please report in this thread if the test version runs normally for you of if you encountered a problem. Thanks for your help.
http://downloads.hitechcreations.com/AHFMODBETA2.EXE
-
Hi Pyro,
It seems good for the part regarding sounds - I don't use vox.
No sound cards too.
TY
:salute
-
I get the same thing with fmmodbeta2.exe :noid won't load the game
(http://i836.photobucket.com/albums/zz281/Megalodon2/ahtest_zpsddb0e242.jpg)
-
So far offline.
If I enable Dolby with my plantronics 780. When I press the VOX key and speak, the game hangs for 30 seconds while it disables all advanced graphics. Then my voice comes through. The yellow SERVER will stay in the upper right corner of the screen for 60 seconds then go away. If I disable Dolby I can now use 7.1 emulation without FPS hits after 2-3 minutes of using VOX and viewing around the airfeild.
I tested with "protect objects" disabled using the 88 to destroy the feild and cause fires. Initialy when looking at a fire and talking on VOX, pressing the VOX button would cause a micro hitch. Then voice playback woud happen. Eventualy by the third object destoryed that resulted in a fire, I could press the VOX key with no screen hitches.
There is still a click that preceeds the voice playback. But I'm so far not taking FPS hits and I have both sliders to the left with Detailed water, Detailed terrain, Local water reflections, and clouds bump mapped. My varyence and delay is now flat instead of having micro movements in it with the last two beta executables. There were small up spikes and small period square waves only at the points that screen hitches happened. Then it flattened for the rest of the session as I destroyed the feild.
After exiting the beta executable I ran the 2.29p5. I left my speaker emulation at 7.1. When I pressed the VOX button the game hung for 30 seconds then faulted to an exe error. I checked the "Windows Speaker" configuration and the speaker emulation had been changed from 7.1 to 5.1. I reconfigured to Quad speakers and had no hangs when using VOX.
The default sound level for the beta is 1\3 lower than the 2.29p5 executable.
-
Buster of you are testing voice offline, please check that the voice transmit settings (in Arena Flags) is set the same as the host.
HiTEch
-
Had a good hour session with the beta. No problems. I do use vox.
-
Still getting freezes when using vox. Seems the longer I am on, the worse it gets.
Speaker 0 [Speakers (4- Logitech G35 Headset)]
Speaker 1 [Speakers (SB X-Fi Xtreme Audio)]
Speaker 2 [Digital Audio Interface (SB X-Fi Xtreme Audio)]
*****************************
Mic 0 [Microphone (4- Logitech G35 Headset)]
Mic 1 [Microphone (SB X-Fi Xtreme Audio)]
Mic 2 [Line-In (SB X-Fi Xtreme Audio)]
Mic 3 [S/PDIF-In (SB X-Fi Xtreme Audio)]
*****************************
Driver 0 Index -1
Driver 1 Index -1
Driver 2 Index -1
Creating Primary Event System for PrimaryDeviceIndex 0
Setting DriverListIndex 0 default = 0
Default speaker mode
Using Hardware Exceleration
Rate 48000
Speaker 2
OutputChannel 2
InputChannel 6
Method 1
Bits 16
Setting default format Result 0
Driver Name [Speakers (4- Logitech G35 Headset)] result 0
Effect init result 0
snprimInitSpeakers retured 0
-
Buster of you are testing voice offline, please check that the voice transmit settings (in Arena Flags) is set the same as the host.
HiTEch
Since I do not know the extent of difference between the 2.29p5 executable and the beta executable. I also have no specific object names for "voice transmit settings". These are the only sound related settings from "ArenaFlags".
ArenaFlags
2.29p5--- Beta
--{ } ------{ } -- Use LPC Codec
--{ } ------{ } -- Use VOX Codec
--{x} -----{x} -- Use MS GSM 6.10
--{ } ------{ } -- Use MS GSM 6.10 11kHz
-
Figured it out.
Before with this I had the dolby and vox button crash problems. I seem to remember more option checked a while back like before 2.29p5.
ArenaFlags
2.29p5--- Beta
--{ } ------{ } -- Use LPC Codec
--{ } ------{ } -- Use VOX Codec
--{x} -----{x} -- Use MS GSM 6.10
--{ } ------{ } -- Use MS GSM 6.10 11kHz
Did this and Dolby with 7.1 works in both executables. Quitting out of the GUI is almost instantanious now.
ArenaFlags
2.29p5--- Beta
--{x} ------{x} -- Use LPC Codec
--{ } -------{ } -- Use VOX Codec
--{x} -----{x} -- Use MS GSM 6.10
--{x} ------{x} -- Use MS GSM 6.10 11kHz
VOX Codec will allow Doby 7.1 in the 2.29p5 executabale but crashes the beta when I press the transmitt button no matter how I setup the sound source options and speaker. By not checking it I was able to run any setup under both executables and no VOX button crashes to the desktop. With this renaFlags setup I now have the Full extended list in the "Speaker Layout" dropdown choices list.
There is an issue with VOX still in the beta that when my voice first plays back it's no longer a click but, like a chunk of static then my voice. Say 1-2 seconds lead to my voice playback.
All of this trouble in offline mode...still need to test online.
-
Had about three hours with this beta so far, and rock solid no issues. Will continue to test, if you'd like to know system specs let me know.
<S>...-Gixer
-
I had a problem similar to NOT's. When flying a 190A5 solo everything seemed fine. Flying a Storch low and slow I had about a 4 second freeze while talking on range, then about 3 minutes later the game completely froze while talking on range. I had to do a hard reset to get out of the program.
Speaker 0 [Speakers (Sound Blaster X-Fi Xtreme Audio (Vista))]
Speaker 1 [Digital Audio (S/PDIF) (Sound Blaster X-Fi Xtreme Audio (Vista))]
*****************************
Mic 0 [Microphone (Sound Blaster X-Fi Xtreme Audio (Vista))]
Mic 1 [Digital Audio (S/PDIF) (Sound Blaster X-Fi Xtreme Audio (Vista))]
*****************************
Driver 0 Index -1
Driver 1 Index -1
Driver 2 Index -1
Creating Primary Event System for PrimaryDeviceIndex 0
Setting DriverListIndex 0 default = 0
Default speaker mode
Using Hardware Exceleration
Rate 48000
Speaker 2
OutputChannel 2
InputChannel 6
Method 1
Bits 16
Setting default format Result 0
Driver Name [Speakers (Sound Blaster X-Fi Xtreme Audio (Vista))] result 0
Effect init result 0
snprimInitSpeakers retured 0
CPU: Core 2 Quad Q8400 OC to 3.08GHz
4 GB RAM
Video: EVGA GeForce GTX 660
-
The ArenaFlags settings I enabled fixed the VOX key to desktop executable error. But, if I didn't match my windows speaker setup in the beta exe or the 2.29p5 exe game sounds, I would get the VOX transmit button to desktop executable error.
I was able to play online with either executable set to Dolby 7.1. There is no longer a click befor the voice comes through with the beta executable. Now there is a 1sec static hiss befor the voice comes through as though pressing the button caused hiss.
But, before even that with the beta executable. Every time I pressed the VOX key I would get a 1-2 second game freeze. FPS was not impacted outside of expected norms now by running sound as Dolby 7.1. I got the game freeze with Dolby and without.
-
posted again
Noticed a problem. If I log in with the test version everything seems fine. If logged in regular version. I can hear others but I can not transmit. The little indicator does not light up. All other sounds seem fine.
-
Downloaded last night and zero issues. I uninstalled Realtek about two weeks ago so I'm run ing straight windows sound.
No FPS improvement.
-
ArenaFlags
2.29p5--- Beta
--{ } ------{ } -- Use LPC Codec
--{ } ------{ } -- Use VOX Codec
--{x} -----{x} -- Use MS GSM 6.10
--{ } ------{ } -- Use MS GSM 6.10 11kHz
This is how the flags should be set.
Don't test the lpc or vox, because both of those options will be going away.
Also you MUST only choose 1 at a time.
HiTech
-
Still getting freezes when using vox. Seems the longer I am on, the worse it gets.
Are these when you hear some one, or transmit?
HiTech
-
I get the same thing with fmmodbeta2.exe :noid won't load the game
(http://i836.photobucket.com/albums/zz281/Megalodon2/ahtest_zpsddb0e242.jpg)
What version of Windows are you running?
-
I get the same thing with fmmodbeta2.exe :noid won't load the game
(http://i836.photobucket.com/albums/zz281/Megalodon2/ahtest_zpsddb0e242.jpg)
You need to install windows xp sp2 or 3
HiTech
-
transmit only.
-
Been running it since Skuzzy let it out, no problem here so far! Been on for at lest 6 hours. :D
-
So as this story evolves and I've been given more information after I cause my own unintendad consiquences. Here is the results of todays testing.
-------------------------------------------------
ArenaFlags
2.29p5--- Beta
--{ } ------{ } -- Use LPC Codec
--{ } ------{ } -- Use VOX Codec
--{x} -----{x} -- Use MS GSM 6.10
--{ } ------{ } -- Use MS GSM 6.10 11kHz
This is how the flags should be set.
Don't test the lpc or vox, because both of those options will be going away.
Also you MUST only choose 1 at a time.
HiTech
-----------------------------------------------------
Plantronics GameCom 780
1. - After I finish testing if I want to play on the 2.29p5 executable. I have to change the flag to LPC Codec or I get a crash to desktop when I press the VOX key. But, I don't get screen freezes or FPS hits.
2. - I tested MS GSM 6.10 options separately.
a. - MS GSM 6.10 11kHz:
Offline - stutters, screen freezes and FPS drops into the single digits sometimes pressing the VOX key. Online - the same.
Dosen't like Dolby and Windows reduced my speaker emulation from 7.1 to 5.1 during a 1 minute hard freeze. It's possible I need to set my windows internal sound configuration to 11kHz first and this won't happen.
b. - MS GSM 6.10:
Clicks or hiss just before voice playback happens. Some FPS hit as low as the 20's in hand with transmit screen freeze. On average 40's are the lowest. If I first check Dolby, exit, reenter offline, then press the VOX key. It dosen't like Dolby and crashes to destop when I press the VOX key. But, if I enter offline already set to Windows Speaker Configuration then change to Dolby it won't crash with the VOX key.
Choosing windows speaker configuration rather than the specific windows speaker setup is the least problematical on my PC.
Online in an empty AvA tuned to myself and range while blasting away with an 88 at an ord bunker. I could not get screen stutters or FPS hits while making constant sounds over VOX. Same in the TA firing 5" rapidly from a carrier. My experience last night in the MA was micro screen freezes and FPS hits everytime I spoke on VOX.
-
my issues went away with the new version. but out of curiosity what am I supposed to be listening to? I dont hear anything different then again I have custom sounds. gonna rename them see if that is my mistake now.
semp
-
Try a search on MS GSM 6.10.
-
my issues went away with the new version. but out of curiosity what am I supposed to be listening to? I dont hear anything different then again I have custom sounds. gonna rename them see if that is my mistake now.
semp
There is no difference in the sounds..... yet :D
Once HTC gets the sound system up and running the way they want, THEN they will be able to add sounds like they want.
-
the spatialization (if that even exist) of the samples sounds a bit better, but it could be a placebo effect on my side.
Even as I play in mono, sometimes I get stereo effects with this system :headscratch:
-
There should not be any difference then the current version in quality.
This is a simple foundation for the new stuff. What you are looking for are major issuses, like the game won't start. The game will not see speakers. The game hangs .....
It is the low level stuff that is system dependent, hence why some have issues some don't. It is what we need to sort out in a beta.
HiTech
-
I don't use vox.
I found a little bug respect to what it seems going on vox.
I taked-off from a cv that was not under attack and i flew to a field under attack.
Well i could hear the field alarm. The sound was very very low but it was there.
The field was far from cv.
:salute
-
Installed the Beta Monday
Running: Win 7, 64-bit, 12GB RAM, i7-990x, 2xGeforce 580M, Running 3 different sound setups:
1. Soundblaster XFi USB
2. Internal RealTek
3. Plantronics Gamecom 780 USB
All working perfectly, no crashes/oddities
:salute
-
Had a strange situation yesterday in MW, while defending a VBase in a wirbl. We were shooting at a formation of KI67's when they warped, then dissappeared, reappeared and flew off "into the sunset". when I landed my wirbl, I recieved credit for 21 victories, un earned I might add. I did save the video. I was running the latest FMOD beta.
-
Only had time for a short test but no issues so far with beta2.
-
I've been using it regularly and no issues so far....... :old:
-
I get micro freezes that occur at the end of every vox trasmission. Very noticable in GVs
Speaker 0 [Speakers (Logitech G35 Headset)]
*****************************
Mic 0 [Microphone (Logitech G35 Headset)]
Mic 1 [Microphone (Realtek High Definition Audio)]
*****************************
Driver 0 Index 0
Driver 1 Index 0
Driver 2 Index 0
Creating Primary Event System for PrimaryDeviceIndex 1
Setting DriverListIndex 0 default = 0
Default speaker mode
Using Hardware Exceleration
Rate 48000
Speaker 2
OutputChannel 2
InputChannel 6
Method 1
Bits 16
Setting default format Result 0
Driver Name [Speakers (Logitech G35 Headset)] result 0
Effect init result 0
snprimInitSpeakers retured 0
-
I was in the MA, one sortie 10 minutes, with about 15 cons nearby (less that 6k). When I used VOX the game froze several times. One freeze lasted about 3 or 4 seconds. I have a Lenovo IdeaCentre running W7 Home Edition.
-
I played today and only had one crash. not sure how it happened but I was using vox and another transmission came in and game froze. I was able to come back and rejoin my plane.
like somebody else already pointed out. I play with 60 fps and shadows at 4096 except for enviromental mapping as that sucked the frames out into kansas. today I had it at 50% just to test it and my frames stayed above 50 and mostly 60 even with heavy gv/air fighting. had no stutters at all when using vox.
semp
-
Something odd happened last night. I am pretty sure I upped with the regular AH icon instead of the beta last night. We were on our squad channel and I kept loosing voice from the two others in the squad although they could here each other. This is a problem I have not had before until I installed the beta.
I will up with the beta tonight.
-
I used the last version test from the very beginning with no probleme but today
strange sound 'click' or 'crek' when engine is one are returned :O
So I had to use the normal version.
Very strange.
:salute
-
when engine is one are returned :O
:headscratch:
King illegal forest to pig wild kill in it a is?
-
Lulu,
Do you type your response in another language than english first? Then run it through a text translater and paste it into your forum responses?
-
Whats the correct way to get rid of the beta version. Just delete it from the AH folder?
-
Neg. I do not use translator. But differences are minimal :rofl
:salute
P.S.
The last beta version worked well for me until yestarday. After yestarday
it has started to show some problem. When engine is on there are some unexpected
sounds in the form of 'click' or 'crek' that are produced.
-
Mobilis in mobile: unexpected flexability and quantum leaps in the Helicobacter pylori genome.........
Lulu you saying you give people ulcers......
-
"Megalodon, please try the new version and report if the problem still persists."
Yes it does. :uhoh
Thank you for trying,
:salute
-
Last night using the beta several issues occurred:
1. Frame Stuttering repeatedly
2. Freeze frame for 6-7 seconds but the game resumed on three occasions
3. Frame rate drops of 45+ fps with no visible difference in gameplay
-
Last night using the beta several issues occurred:
1. Frame Stuttering repeatedly
2. Freeze frame for 6-7 seconds but the game resumed on three occasions
3. Frame rate drops of 45+ fps with no visible difference in gameplay
Will you post your fmodinit.txt please.
HiTech
-
Had the same problem as Changeup. DIdn't know it was due to the FMOD. Here ya go:
Speaker 0 [Speakers (Realtek High Definition Audio)]
Speaker 1 [Realtek Digital Output (Realtek High Definition Audio)]
*****************************
Mic 0 [FrontMic (Realtek High Definition Audio)]
*****************************
Driver 0 Index 0
Driver 1 Index 1
Driver 2 Index 0
Creating Primary Event System for PrimaryDeviceIndex 0
Setting DriverListIndex 0 default = 0
Default speaker mode
Using Hardware Exceleration
Rate 48000
Speaker 2
OutputChannel 2
InputChannel 6
Method 1
Bits 16
Setting default format Result 0
Driver Name [Speakers (Realtek High Definition Audio)] result 0
Effect init result 0
********************************
Creating Secondary Device 1
Setting DriverListIndex 1 default = 0
Default speaker mode
Using Hardware Exceleration
Rate 48000
Speaker 2
OutputChannel 2
InputChannel 6
Method 1
Bits 16
Setting default format Result 0
Driver Name [Realtek Digital Output (Realtek High Definition Audio)] result 0
System init result 0
snprimInitSpeakers retured 0
-
Last night using the beta several issues occurred:
1. Frame Stuttering repeatedly
2. Freeze frame for 6-7 seconds but the game resumed on three occasions
3. Frame rate drops of 45+ fps with no visible difference in gameplay
I figured when that happened is was my video card or the Trackir so today I cut back to just Bump mapping and did not have the problem although the session was short so not much of a test.
I could not find the fmodinit.txt. I downloaded the second version but it must not have installed.
-
Sorry should have posted the results of the init file.
Speaker 0 [Speakers (Plantronics GameCom 780)]
*****************************
Mic 0 [Microphone (Plantronics GameCom 780)]
*****************************
Driver 0 Index 0
Driver 1 Index 0
Driver 2 Index -1
Creating Primary Event System for PrimaryDeviceIndex 0
Setting DriverListIndex 0 default = 0
Default speaker mode
Using Hardware Exceleration
Rate 48000
Speaker 2
OutputChannel 2
InputChannel 6
Method 1
Bits 16
Setting default format Result 0
Driver Name [Speakers (Plantronics GameCom 780)] result 0
Effect init result 0
snprimInitSpeakers retured 0
-
I launched Early War. I spoke on channel as I took off with no problems. Spoke on "Range", the game froze immediately and ended with a host connection lost message. It looks like was the only one to disco.
Flew 3 sorties in the MA ( 2 into a massive furballs) without using VOX. No problems noted.
Speaker 0 [Speakers (Realtek High Definition Audio)]
Speaker 1 [SMB2430H-1 (NVIDIA High Definition Audio)]
*****************************
Mic 0 [Microphone (Realtek High Definition Audio)]
Mic 1 [Stereo Mix (Realtek High Definition Audio)]
*****************************
Driver 0 Index -1
Driver 1 Index -1
Driver 2 Index -1
Creating Primary Event System for PrimaryDeviceIndex 0
Setting DriverListIndex 0 default = 0
Default speaker mode
Using Hardware Exceleration
Rate 48000
Speaker 2
OutputChannel 2
InputChannel 6
Method 1
Bits 16
Setting default format Result 0
Driver Name [Speakers (Realtek High Definition Audio)] result 0
Effect init result 0
snprimInitSpeakers retured 0
-
Will you post your fmodinit.txt please.
HiTech
Speaker 0 [Headphones (High Definition Audio Device)]
Speaker 1 [Digital Audio (S/PDIF) (High Definition Audio Device)]
Speaker 2 [W2361-1 (NVIDIA High Definition Audio)]
Speaker 3 [Digital Audio (S/PDIF) (High Definition Audio Device)]
Speaker 4 [Speakers (High Definition Audio Device)]
*****************************
Mic 0 [Microphone (High Definition Audio Device)]
*****************************
Driver 0 Index 0
Driver 1 Index 0
Driver 2 Index 0
Creating Primary Event System for PrimaryDeviceIndex 1
Setting DriverListIndex 0 default = 0
Default speaker mode
Using Hardware Exceleration
Rate 48000
Speaker 2
OutputChannel 2
InputChannel 6
Method 1
Bits 16
Setting default format Result 0
Driver Name [Headphones (High Definition Audio Device)] result 0
Effect init result 0
snprimInitSpeakers retured 0
RealTek uninstalled two weeks ago...straight Windows sound.
-
How do I uninstall this? This is miserable. Check my discos from tonight. Seriously, I'd like to get this off my system please. :salute
-
If you have a problem with the test version you can simply go back to launching the game as you normally do.
No, I cannot. I tried and got repeated crashes...
-
Update...screen lock and crash 7 times but no disco since last post.
-
Update...screen lock and crash 7 times but no disco since last post.
By chance are you using one of vinkman's affinity changes?
-
How do I uninstall this? This is miserable. Check my discos from tonight. Seriously, I'd like to get this off my system please. :salute
I asked the same question on 2-28-13.
-
By chance are you using one of vinkman's affinity changes?
Not Vinkmans....
-
No, I cannot. I tried and got repeated crashes...
Then it is not the beta that is crashing your system.
When you test the beta is gives you a different start-up icon. If you don't want to use the beta, use the original start-up icon you have on your desktop.
The game doesn't make any changes to your computer, beta or other wise. So going back to the original game icon/start is like you NEVER used the beta. If your having problem being IN the game on the beta then it is just coincidence that your getting crashes and/or dumps when your not in the game.
-
Then it is not the beta that is crashing your system.
When you test the beta is gives you a different start-up icon. If you don't want to use the beta, use the original start-up icon you have on your desktop.
The game doesn't make any changes to your computer, beta or other wise. So going back to the original game icon/start is like you NEVER used the beta. If your having problem being IN the game on the beta then it is just coincidence that your getting crashes and/or dumps when your not in the game.
I understand what's been done and I understand the diff in the two. What I don't understand is why after 6 years of flying and this never happening, I install the beta, then it starts happening. No other changes. SOOOoooooooo? The easiest explanation is usually the right one.
-
Sadly once you run the beta it seems to change things sound wise with the 2.29p5 release when you go back to using it. I'm probably wrong but, who knows. I went through one night having to reduce my graphics detail just to stop FPS hits after switching back to 2.29p5. Yes possibly it was a bad internet night killing my system. But, then until I took part in this beta I never had the game auto reduce my graphics detail to try and keep me from being discoed.
On the other hand there was the issue of switching between the Beta executable and the 2.29p5 executable and the first time you hit the transmit key your system crashes. That took discovering what was changed in my speaker and mic source selections. I would start the beta with one speaker configuration and find when I went back to the 2.29p5 executable my speaker configuration had changed.
I don't even know which VOX Codec is the correct one for the 2.29p5 release. One night I had LPC checked and my FPS and performance was great. The next night after I logged in my Codec was changed to GSM 6.10 and at times I was getting reduced FPS during VOX chatter. I had my squad check their ArenaFlags and all were GSM 6.10.
I hope HTC has a forced arena profile for us when we first login to insure our VOX Codec choice is the correct one for their VOX server.
And then there has simply been times over the years that I uninstall the game and run a new full install and copy over my backed up settings. Then all the performance issues seem to go away for awhile. Kind of like the Window 3.1 days where you bit the bullet and reinstalled once in awhile. My MS support contact used to laugh at me for trying to go as long as possible without reinstalling Win3.1. It really takes very little time to uninstall and reinstall the game if you regularly backup your important settings.
I know....I ain't got the derned time and I payed my $14.95 and it's HTC's problem not mine. He wrote this bunked up code so so so....whiffle......It's all HiTechs fault and I'm a victim of his COAD!!
This game is a alot easier to reinstall than Win3.1.
-
I understand what's been done and I understand the diff in the two. What I don't understand is why after 6 years of flying and this never happening, I install the beta, then it starts happening. No other changes. SOOOoooooooo? The easiest explanation is usually the right one.
changeup is right. I havent really had a disco in months and when using the beta I had no problems for 2 days then yesterday I would get freezes and game crashes. I guess there was a lot of airplanes and lots of people on vox then game would stutter, freeze and a crash.
semp
Speaker 0 [Speakers (Creative SB X-Fi)]
*****************************
Mic 0 [Microphone (Creative SB X-Fi)]
*****************************
Driver 0 Index 0
Driver 1 Index 0
Driver 2 Index -1
Creating Primary Event System for PrimaryDeviceIndex 0
Setting DriverListIndex 0 default = 0
Default speaker mode
Using Hardware Exceleration
Rate 48000
Speaker 2
OutputChannel 2
InputChannel 6
Method 1
Bits 16
Setting default format Result 0
Driver Name [Speakers (Creative SB X-Fi)] result 0
Effect init result 0
snprimInitSpeakers retured 0
-
I haven't appeared to have had any issues. There doesn't seem to be an improvement or deterioration in FPS or quality in any way. I'm launching both normal and beta using FSAutostart.
Regards,
Leonard
F77
-
I gave up today on the beta. lots of stuters and game freezes with one crash.
semp
-
No, I cannot. I tried and got repeated crashes...
I also ent back to original tisay everytime I tried to xmit on Vox it crashed, 3 times in a row.
Speaker 0 [Speakers (Realtek High Definition Audio)]
Speaker 1 [Realtek Digital Output (Realtek High Definition Audio)]
*****************************
Mic 0 [FrontMic (Realtek High Definition Audio)]
*****************************
Driver 0 Index 0
Driver 1 Index 1
Driver 2 Index 0
Creating Primary Event System for PrimaryDeviceIndex 0
Setting DriverListIndex 0 default = 0
Default speaker mode
Using Hardware Exceleration
Rate 48000
Speaker 2
OutputChannel 2
InputChannel 6
Method 1
Bits 16
Setting default format Result 0
Driver Name [Speakers (Realtek High Definition Audio)] result 0
Effect init result 0
********************************
Creating Secondary Device 1
Setting DriverListIndex 1 default = 0
Default speaker mode
Using Hardware Exceleration
Rate 48000
Speaker 2
OutputChannel 2
InputChannel 6
Method 1
Bits 16
Setting default format Result 0
Driver Name [Realtek Digital Output (Realtek High Definition Audio)] result 0
System init result 0
snprimInitSpeakers retured 0
-
Im done with this test boys. Everytime I touched the vox button the game froze. Prior to today, I unloaded every non-essential operation I had. I've torpedoed the game and reloaded it.
-
Then it is not the beta that is crashing your system.
When you test the beta is gives you a different start-up icon. If you don't want to use the beta, use the original start-up icon you have on your desktop.
The game doesn't make any changes to your computer, beta or other wise. So going back to the original game icon/start is like you NEVER used the beta. If your having problem being IN the game on the beta then it is just coincidence that your getting crashes and/or dumps when your not in the game.
There is more than this...there was an entry in my system registry for the new sound exe.
-
There is more than this...there was an entry in my system registry for the new sound exe.
windows will create reg entries for any executable you run
-
Tried to go back to the standard AH, everytime I hit the VOX button the computer freezes, online or offline. THe FMOD appears to be working ok though, while I have experienced the frame rate drop and the short freezes in the video, everything else appears to work fine. How do you remove the FMOD?
Speaker 0 [Speakers (Realtek High Definition Audio)]
Speaker 1 [Realtek Digital Output (Realtek High Definition Audio)]
*****************************
Mic 0 [FrontMic (Realtek High Definition Audio)]
*****************************
Driver 0 Index 0
Driver 1 Index 1
Driver 2 Index 0
Creating Primary Event System for PrimaryDeviceIndex 0
Setting DriverListIndex 0 default = 0
Default speaker mode
Using Hardware Exceleration
Rate 48000
Speaker 2
OutputChannel 2
InputChannel 6
Method 1
Bits 16
Setting default format Result 0
Driver Name [Speakers (Realtek High Definition Audio)] result 0
Effect init result 0
********************************
Creating Secondary Device 1
Setting DriverListIndex 1 default = 0
Default speaker mode
Using Hardware Exceleration
Rate 48000
Speaker 2
OutputChannel 2
InputChannel 6
Method 1
Bits 16
Setting default format Result 0
Driver Name [Realtek Digital Output (Realtek High Definition Audio)] result 0
System init result 0
snprimInitSpeakers retured 0
-
Im done with this test boys. Everytime I touched the vox button the game froze. Prior to today, I unloaded every non-essential operation I had. I've torpedoed the game and reloaded it.
ChangeUp, will you run the beta, and then go into the sound configuration and change your mic selection. Then see if the vox still locks up.
Also Aces High does only 1 thing to the registry, and that is put it's installation path there. The beta release did not change anything in the registry.
The only thing the beta touches that is any different the the release is the sndgrp.cfg file in the settings folder.
Delete settings/sndgrp.cfg will return you sound card selections to default installation.
The beta release simply places 3 files into you Aces High folder and adds 1 short cut.
HiTech
-
ChangeUp, will you run the beta, and then go into the sound configuration and change your mic selection. Then see if the vox still locks up.
Also Aces High does only 1 thing to the registry, and that is put it's installation path there. The beta release did not change anything in the registry.
The only thing the beta touches that is any different the the release is the sndgrp.cfg file in the settings folder.
Delete settings/sndgrp.cfg will return you sound card selections to default installation.
The beta release simply places 3 files into you Aces High folder and adds 1 short cut.
HiTech
I blew it all away. I tried to keep all my folders but when I reinstalled last night, it kept trying to download beta2 over and over. So I crushed the whole thing.
I did change the mic and restart, speakers and restart, mic and speakers and restart multiple times. If you want me to load the beta again. The fresh install isn't a problem.
-
"it kept trying to download beta2"
This makes no since to me, the beta2 does not update anything.
HiTech
-
I found through trial and error that your "Mic" source choice under your "Speakr Layout" choice can crash the game when you press the VOX button. Less often your speaker layout can do this.
When I switched between the beta and the 2.29p5 executable these things would get changed. I found when I set the beta so pressing the VOX button didn't crash the game. Then went back to the 2.29p5, the "Speaker Layout" and "Mic" choice would be different from what I set befor exiting and running the beta.
Often when I set the speakers and mic to what I configured in "Windows" in the beta. When I went back to the 2.29p5 the speakers would be "Use Windows Speaker Configuration" and mic would be "use primary driver" or something like this. Sometimes the reverse would happen going from the 2.29p5 to the beta. I just got used to checking my sound setup before I pressed the VOX button.
The beta installs in moments. Before going into it, copy down your sound setup choices under "Speaker Layout" by running 2.29p5 and inspecting them knowing they are the ones that work. Then make sure those are your choices when you run the beta. If your mic source is wrong the game will crash when you press the VOX button.
Beta and Bug testing with an ongoing feature like this is frustrating and annoying if you really aren't intersted in beta testing. The whole process is supposed to P you Off so you can help the programmer fix it. Not take it personaly and treat the programer like this is the released product with a horrible bug he missed to screw you. We all know some of us get screen freezes when you press the VOX key. And now we all know if your mic source is wrong, you get an executable error dump to the desktop when you press the VOX key.
-
"it kept trying to download beta2"
This makes no since to me, the beta2 does not update anything.
HiTech
I'm sorry....the terrain beta2. The download path statement said ahterr/beta2
-
ChangeUp, will you run the beta, and then go into the sound configuration and change your mic selection. Then see if the vox still locks up.
Also Aces High does only 1 thing to the registry, and that is put it's installation path there. The beta release did not change anything in the registry.
The only thing the beta touches that is any different the the release is the sndgrp.cfg file in the settings folder.
Delete settings/sndgrp.cfg will return you sound card selections to default installation.
The beta release simply places 3 files into you Aces High folder and adds 1 short cut.
HiTech
Did this HT and 2.29p5 runs fine with no crash when I use VOX. Thank you.