September 15, 20214 yr Hey, Can someone help me? I've just purchased FS2Crew Airbus Button edition on Steam for use with FSX:SE. When I press the Hotkey to open the main panel, I get the following error..followed by a panel that opens but produces no sounds when pressing any buttons. This is for use alongside the Airbus Steam version.
September 15, 20214 yr Commercial Member Please ensure Nahimic or Asus Sound Studio are not running on your computer. Also, please check this:http://www.support.fs2crew.com/help/manuals/#pageid=troubleshooting2 B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
September 15, 20214 yr Author I don't have either of those on my system. I am currently reinstalling FSX to see if that solves anything in the meantime. The only "sound" related thing running on my machine is "Dell Audio". I can see if finding a way to close that helps. It doesn't crash FSX. In fact, the first time I loaded FSX to try it i was in fullscreen and so the panel appeared but no sound played. It wasn't until I ran it windowed I saw the error dialog appear.
September 15, 20214 yr Commercial Member Also try this: Uninstall your audio drivers. Reboot Windows. Windows will auto install generic Windows sound drivers. That could solve your problem there. Best, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
September 15, 20214 yr Author Ok I have reinstalled FSX....Same error. I closed all audio services I could find running....Same error. I uninstalled all audio sound cards from Device manager and restarted ..same error. I even tried a whole seperate machine that has FSX installed on a different drive letter and folder structure...exact same error.
September 15, 20214 yr Commercial Member What's the exact error code? It should be longer than 0x0. And confirm you're using the "Steam store" version of the Aerosoft Airbus aircraft (bought via the Steam store), not the version from the Aerosoft store. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
September 15, 20214 yr Author Ok I have found a way to make it work, although im not sure why it works this way. It shows that error and no sound from FS2Crew plays when I first create a flight/load a flight plan. If I end flight and start it again, it all works. No error, and the sound test works. It also shows my speakers in the speaker box, where as it says no audio devices found the first time. Always the first ever flight shows the error and no sound.
September 15, 20214 yr Commercial Member 22 minutes ago, ManchurianMan83 said: Ok I have found a way to make it work, although im not sure why it works this way. It shows that error and no sound from FS2Crew plays when I first create a flight/load a flight plan. If I end flight and start it again, it all works. No error, and the sound test works. It also shows my speakers in the speaker box, where as it says no audio devices found the first time. Always the first ever flight shows the error and no sound. Interesting... but we generally don't recommend using saved situation or flight plan files. They can cause load order problems in FSX. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
September 15, 20214 yr Author I wasn't initially. if I choose Airbus, Airport,Weather and Time in the Free Flight menu and click fly now... Once it loads, and the airbus turns off (Cold & Dark MCDU kicks in)... if I then press 'C' (main panel key)...it shows the error dialog..followed by panels with no sound or sound car set/detected. if I simply do file>end flight..back to the free flight screen and just click fly now again..same settings... Once it loads again, and the airbus turns off (Cold & Dark MCDU kicks in)... if I then press 'C' (main panel key)..this time no error and it all works. No flight plan or saved scenario used at all. It's odd.
September 15, 20214 yr Author I find this out by accident..because i accidentally forgot to set the airport to anything other than FSX default (Friday Harbor) and so I ended up loading up in the air..with the plane then going Cold and Dark...so I quickly quit the flight and changed the airport to one wher I was grounded to start with...I then pressed C and it worked! That's when I then repeated the steps to figure out why that worked...the restart.
September 15, 20214 yr Commercial Member Ahh, that would explain it. Yes, don't start the plane in the air over Friday Harbor. Start the plane at your parking spot at our desired airport. Do not use saved situation files. Complex 3rd party addons should be loaded as "cleanly" as possible. Edited September 15, 20214 yr by byork B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
September 16, 20214 yr Author To be clear, this error also happens when creating a free flight, not just a saved situation/flight plan. For example, if I set Aircraft:Airbus, Airport:Heathrow, Weather: Fair, Time of Day:1:00 pm and click Fly Now... (unless i'm misunderstanding things, that is not a "saved situation" right?) it will error the moment I eventually load into Heathrow and press the Main Panel key. Anyway, I've found a more streamlined way to fix the issue. If I simply Reset Flight (without having to End Flight back to menu first), then it will work the second time around.
September 16, 20214 yr Commercial Member What's the default aircraft that loads 1st on the free flight screen? Is it the Trike? It should be the trike, never a 3rd party plane. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
September 16, 20214 yr Author Yea it's the Trike, Friday Harbor, fair weather, and the time I believe varies when FSX first loads. Then I change plane to Airbus, and the airport to a ground starting one.
September 16, 20214 yr Author Worth mentioning as well... I've also tried changing the MCDU state to "Turn around" and back to "Cold & Dark" once it first loads, to see if it's something to do with the initial default state of the MCDU not working properly. (I already have set to "Cold & Dark" by Default though) Still causes the error. Only a Flight Reset/End Flight & Reload actually works.
Archived
This topic is now archived and is closed to further replies.