Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Maddog with FS2Crew CTD

Featured Replies

Hi,I have a rather annoying problem which makes it impossible to use FS2Crew with the Maddog.I set up a new Windows XP SP3 system only for FS9 a few days ago. I installed the MS Speech Recognition Engine version 5.1, which works just fine during the training sessions.FS9 is patched to version 9.1, and everything works perfectly, even the Maddog with SP1. Now I installed FS2Crew for the Maddog, then I applied the SP3 update. When I select the Maddog now (doesn't matter if I do this in the start menu or later after loading another aircraft), the FS closes instantly before the loading bar appears. No error message is given.I made it 100% sure that FS2Crew is responsible, as deinstalling it results in the Maddog working flawlessly again.The same happened to the Wilco 737 with the FS2Crew Voice Commander Edition installed (SP1), but now I was able to load it up but then get the error message that the FS2Audio.dll could not be initialized. The file shows no version number but was created at 13. April 2010, 04:08:11 and is properly located in \Windows\System32.Is there any solution for this? I had it working under Windows XP SP3 before, so I really don't know why it won't work this time...Thanks for your help!Alex

  • Commercial Member

Hi Alex,If it worked before for you, it should be able to work again.Try this:1. (Re) Install DirectX from Microsoft.2. (Re) Install the VS2008 runtimes from Microsoft (just do a quick Google search for the link).3. (Re) Install SAPI.P.S. I strongly suggest upgrading to Win 7. XP has had its day.Hope that helps.Best,

Hi Bryan,wow, you're fast :DI reinstalled DirectX (Febuary 2010 Update), I redownloaded and updated the VS2008 runtimes, both already earlier today. I'll try reinstalling the SAPI engine, didn't do that yet.As for the jump to Win7, I actually downgraded again as I had severe CTD problems with FS9 and Win7 the last time I tried to run that combination. Under XP the FS9 usually is stable as hell, meaning I can do 5-6 flights in a row without the FS turning on me. I have FSX running under Win 7 though, working just fine - but I don't have enough FSX capable addons yet to really make the change to FSX on Win 7.

I reinstalled the Speech Recognition Software now (downloaded it again, so newest version in town...), didn't work.Do you have any other hints Bryan?

  • Commercial Member

Hi,Try updating your video and audio drivers.Other than that, hard to guess.It worked for you before.Only other guess... try removing any programs (if any) on your system that attempt to remove any Digital Rights from downloaded music.Some of those programs can conflict with the FS2Crew audio engine.Best,

  • 5 weeks later...

Hi Bryan,actually none of these things worked, so I threw away the XP setup and set up a fresh Windows 7 Professional for the Flight Sim. I have no programs removing DRM so that wasn't it either.I'm having problems now as well. Everything runs smoothly except FS2Crew (both the PIC and the Maddog Voice Commanders, updates installed). Here's what happens: I start Active Sky Evoltion, then the Flight Simulator. I prepare a free flight with the MD82 and load it. Runs perfectly. But once selecting FS2Crew by clicking the PFD (it does not matter if in VC or 2D panel), the FS window turns black and FS starts working. There is no error message, just the famous "Flight Simulator has stopped working" followed by "FlightSimulator is restarted...".Drivers for Audio, Video, Chipset and everything else I can think of are up to date, as are DirectX and the runtime libraries. I installed the Maddog in the following steps: Install Maddog 2008 - reboot - install Service Pack 1 - reboot - Install FS2Crew for Maddog - Reboot - install SP3 - reboot - Reset panel files in the manager.I also have an FSX copy set up in the exact same environment, also with Maddog and FS2Crew - this runs smoothly, as strange as it might sound. So there must be a problem between Fs2Crew and the FS9.I'm cut off from FS for months now, I need to get this going again *g*

  • Commercial Member
Hi Bryan,actually none of these things worked, so I threw away the XP setup and set up a fresh Windows 7 Professional for the Flight Sim. I have no programs removing DRM so that wasn't it either.I'm having problems now as well. Everything runs smoothly except FS2Crew (both the PIC and the Maddog Voice Commanders, updates installed). Here's what happens: I start Active Sky Evoltion, then the Flight Simulator. I prepare a free flight with the MD82 and load it. Runs perfectly. But once selecting FS2Crew by clicking the PFD (it does not matter if in VC or 2D panel), the FS window turns black and FS starts working. There is no error message, just the famous "Flight Simulator has stopped working" followed by "FlightSimulator is restarted...".Drivers for Audio, Video, Chipset and everything else I can think of are up to date, as are DirectX and the runtime libraries. I installed the Maddog in the following steps: Install Maddog 2008 - reboot - install Service Pack 1 - reboot - Install FS2Crew for Maddog - Reboot - install SP3 - reboot - Reset panel files in the manager.I also have an FSX copy set up in the exact same environment, also with Maddog and FS2Crew - this runs smoothly, as strange as it might sound. So there must be a problem between Fs2Crew and the FS9.I'm cut off from FS for months now, I need to get this going again *g*
On a fresh Win 7 install it should work.Try this:Re-install the VS2008 run-times via the link below.http://www.microsoft.com/downloads/en/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=enBest,

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.