Hi,A few days ago I bought FS2Crew for PIC737 and like the version for MD80 if gives me CTD's.I started up FS2004 and selected the PIC 735, 2D panel only.I open the FS2Crew main panel + config panel and do my settings.The moment I close the FS2Crew main panel I get black screen and next a CTD in dinput8.dll(This assembly also gave problems in the MD80 version...)I run the latest (or one of the latest) version of DX9c (April 2010 if I recall correctly) on Windows XP x86 SP3 US version.Any suggestions?P.S. Both .NET Framework 3.5 SP1 and 4.0 are installedP.S. Dinput8.dll in system32 folder is version 5.3.2600.5512, dated 14-04-2008

Hi Egbert,Tough one as it hasn't been reported before and the user base for the Voice Versions combined is large.So I'm going to have to guess...Dinput8 is associated with DirectX.Questions:1. Do you have a joystick plugged in?2. If so, what kind is it?3. Are you unplugging the joystick after loading FS2Crew?4. Do you have the 'mute' button tied to a joystick button? Try clearing the mute button so it's assigned to nothing (joystick or keyboard).You can clear the mute button assignment directly (this is the best way) by editing the cfg file located in AppData:AppData\Roaming\FS2Crew2010\Versions\737\FS2CrewInputMapper.CFGThat's the file path for Vista/Win 7. XP I recall does not use AppData, but a different folder name. You may need to 'show' hidden files.Failing all that, you might want to do a clean install of XP. Something might just be buggered on your system.Best,

Hi Egbert,Tough one as it hasn't been reported before and the user base for the Voice Versions combined is large.So I'm going to have to guess...Dinput8 is associated with DirectX.Questions:1. Do you have a joystick plugged in?2. If so, what kind is it?3. Are you unplugging the joystick after loading FS2Crew?4. Do you have the 'mute' button tied to a joystick button? Try clearing the mute button so it's assigned to nothing (joystick or keyboard).You can clear the mute button assignment directly (this is the best way) by editing the cfg file located in AppData:AppData\Roaming\FS2Crew2010\Versions\737\FS2CrewInputMapper.CFGThat's the file path for Vista/Win 7. XP I recall does not use AppData, but a different folder name. You may need to 'show' hidden files.Failing all that, you might want to do a clean install of XP. Something might just be buggered on your system.Best,

I have a clean version of XP, installed XP and FS2004 2 weeks ago and will not do it again.It took me 3 days to install sceneries, aircraft, .... ;-)I don't have the mute button assigned, unless it is assigned by default. I will check in cfg.Regarding joysticks: I have Saitek Yoke + TQ, the X52 and VRInsight MCP Combo. So far they function properly without any issues and are always connected.It looks like something in FS2Crew is triggering the assembly because it explicitly happens when closing FS2Crew gauge.Will try to do some testing with less 3rd party modules in the FS2004/modules directory.

I can find only find 1 version of the KeyMapper.cfg in the FS2Crew2010\Control Mapper folder (Doc & Settings)It contains 5 entries but none have a value.I'm a bit puzzled I have a 'B737Default' folder, because I have the PIC version.This is how my FS2004 FS2Crew folder look like:

Hi Egbert,737Default folder is deliberate because many of the users have all three versions of the 737 and it's easier if the "mute button" and other assignments are saved to common cfg files for the 737s.I still can't explain your issue.Please email me the Input Mapper Cfg file.admin *at* fs2crew.comThanks,

Hi,It looks like I have solved the problem by reinstalling FS2Crew PIC + SP1.This time I also entered the serial key. I had forgotten this the first time I installed.So far so good.Egbert

Hi Egbert,Glad you got it resolved :( But the serial key would have made no difference.Whatever caused that that DirectInput CTD is a big 'who knows'.No one else reported it, so it was probably just some weird one-off-thing.Cheers,

Uhhrrrr :( I cheered a bit too early. Still CTD'sHowever, I removed the PanelAsTexture=0 setting from the FS9.cfg and I'm now a lot further then before.Keeping my fingers crossed. EDIT:Completed my first flight, no CTD so I think the PanelAsTexture setting was the cause.Still have the P/B issue, but I have a hunch what this is causing.Will report back later.

Uhhrrrr :( I cheered a bit too early. Still CTD'sHowever, I removed the PanelAsTexture=0 setting from the FS9.cfg and I'm now a lot further then before.Keeping my fingers crossed. EDIT:Completed my first flight, no CTD so I think the PanelAsTexture setting was the cause.Still have the P/B issue, but I have a hunch what this is causing.Will report back later.

Hi,Glad you're making progress.Is "PanelAsTexture" something you manually added to the FS9.CFG?

Is "PanelAsTexture" something you manually added to the FS9.CFG?

Affirm.I used it for a long time, since (in the past) with some graphics cards it would increase framerates considerably with some panels.So I always made the entry in the cfg. Nowadays it isn't necessary anymore.Luckily I noticed the entry otherwise I never would have figured out what the CTD cause was.

Affirm.I used it for a long time, since (in the past) with some graphics cards it would increase framerates considerably with some panels.So I always made the entry in the cfg. Nowadays it isn't necessary anymore.Luckily I noticed the entry otherwise I never would have figured out what the CTD cause was.

So all is good now and that cfg entry was the prob?No more CTDs?