Despite getting hold of the latest dsd_fsx_xml_sound.gau from Doug's site.. I still get the error on loading. It all works pretty well.. I just don't get all the flightdeck sounds.. some of which are bloody anoying so it's not all bad
Just brought it down from EGPK to Brum on the AP and FSX spit out an OOM with 7 miles to run. Piece of sh1t!!! Still.. I wouldn't have got this far in the QW model. In fact, I doubt I'd have got out of Prestwick!
I had that too last night, i was taking the 146 from London City to Jersey, just about reached the south coast and FSX crashed... Reloaded FSX and started at southhampon and got those errors, i even tried loading the Nimrod and had no sound at all. Closed FSX and reloading again seemed to stop the issue...
A bit of digging yesterday shows we're not alone. Unfortunately, I've yet to see a fix One guy had the same problem and posted over at FSDevelopers towit Doug himself answered. He has a sound config tool over at his website and asked the chap to download and try it. It didn't work and Doug's answer was that the chap didn't have DirectX compliant sound (he did.. he had a Soundblaster Audigy) Of all the posts I've seen.. that one was the only one to get any sort of answer!
I use Doug's sound2 and sound3 gauges in a number of models without issue but there's definitely something rather hit and miss with this one Still, as I mentioned above.. I don't get the 'too low.. terrain', 'Pull Up' and a host of the other pain in the butt sounds so it's not all bad. Callouts would be nice but I don't get those either. We'll see what JF send as a reply to my ticket. I'm not confident of a successful outcome
EDIT: Chris.. I've tried using the sound config tool from Doug's site and it doesn't work for me.. I still get the sound error. I've checked both sound devices using DXDIAG (for what THAT is worth) and it reports no problems found. So.. I'm at a loss
ATB
DaveB
I get the betty sounds, with V1 and rotate calls normally i think it was just the once after FSX crashed. Do you get the rotate and V1 call outs? I have a SupremeFX III on my Rampage board so wouldnt guess its that...
Looking at the list of sounds associated with the gauge (I'm not on my flying pc at the moment) I probably don't hear any. Engine sounds and the odd switch click is about the extent of it. Certainly no callouts, GPWS, terrain, bing bongs, gear or flaps It's all surprisingly quiet
Sounds a bit like the same problem as the JF 737 Pro in so much as you get CTD as soon as the aircraft loads up There is a hotfix for this fault which seems to take out all the additional sounds, switch clicks flap sounds, call outs etc the only thing audible are the engines However the model loads up ok and theres no CTD I dont like flying without the sounds so my work around is to load up another model and then swap it on the menu bar. Dont think the 737 adv is a CLS bird But maybe the same workround would work
ATB
Dale
Yes.. I've seen the same problem noted with the 737. As far as the quick fix goes, I bet all it does is either remove or rename the dsd gauge as this is the culprit. The sim loads for me every time.. I just get those 2 error boxes.. click OK and up it loads.. quietly Renaming/removing the dsd gauge is the same as removing the associated sound files.. better really as you wouldn't get the error message as the gauge tried to initialize. Removing the soundfiles will still let the gauge try to initialize thus you'll still get the error.
A roundup of what's happening with the sound problem I'm seeing on the 146.
JF have looked at the error and say it's only happening with a very few users. The only suggestion they've been able to make is for me to download the pack again as the original may have been corrupt. I was loathe to do this as 2 x 146 downloads equates to almost 1/10 of my monthly bandwidth but I did it anyway and still see the error.
I've checked through all my FSX models and see that I already use dsd_fsx_xml_sound.gau with the bladeslapSND utility which gives helicopters a nice 'slapping' sound under certain parts of the flight envelope and for this.. the gauge works perfectly. I'm not really sure what's going on with the 146 soundset. It uses CLS_fsx_sound.gau and CLS_fsx_sound2.gau. Sound2 references DSDGlobals so I presume it's sound2 that is calling dsd_fsx_xml_sound but I'm really not sure. Whatever.. CLS appear to have over-complicated things a little as both CLS gauges reference the same sounds The answer is out there somewhere but I'm no sound boffin so I guess I'll never find it
On another note.. I quite fancy the DC6 which was recently part of a multi-buy offer.. or I did until I read it was from Aeroplane Heaven. Never really had anything of theirs I've been happy with but it might be worth it if it comes up for a fiver at some point
Re' the sound issue I've been having with this model.. I spent a couple of days sending info to JF (I tried everything to be honest) and eventually, I got an email back saying they'd been in touch with the developer and would I mind them passing my email address on. Not quite sure what happened in the meantime but a couple of days later, I got an email from Doug Dawson. I explained everything I'd tried plus the fact that I'd already got a copy of dsd_fsx_xml_sound.gau on my system which worked perfectly with BladeSlapSND. This got Doug thinking as it was the first time he'd had a report that the gauge was working but not with the 146. He suspected a timing issue.. that is, the CLS gauge was calling for his gauge and for whatever reason, DirectSound didn't have enough time to initialize hence.. the error box. What he did was write additional code into his gauge so it would keep trying to initialize DirectSound rather than 'run once' and fail if it was unsuccessful.
The end result is that the 146 will now load at any time, not just if it is selected first, and I can chop and change aircraft with impunity.. notwithstanding the dreaded OOM's
So.. a big for JF, CLS and not least of all.. Doug Dawson Doug is going to pass the revised gauge to JF and CLS for them to make available to users who have the same problem
Still.. I wouldn't have got this far in the QW model. In fact, I doubt I'd have got out of Prestwick! 
One guy had the same problem and posted over at FSDevelopers towit Doug himself answered. He has a sound config tool over at his website and asked the chap to download and try it. It didn't work and Doug's answer was that the chap didn't have DirectX compliant sound (he did.. he had a Soundblaster Audigy) 
Of all the posts I've seen.. that one was the only one to get any sort of answer!
The answer is out there somewhere but I'm no sound boffin so I guess I'll never find it 
for JF, CLS and not least of all.. Doug Dawson 
Doug is going to pass the revised gauge to JF and CLS for them to make available to users who have the same problem 
