matt18295

Evening all, Quick question, This eveing flying 747-400 into gatwick I have had an fsx crash, twice, in exactly the same place as I get established in the localiser.... The error report says the following: - Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Level 2 Task 100 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2013-01-17T22:01:17.000000000Z EventRecordID 26289 Channel Application Computer MattHardy-PC Security Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: TCAS2v7.dll, version: 1.1.6.0, time stamp: 0x4633aecd Exception code: 0xc0000005 Fault offset: 0x00006186 Faulting process id: 0x5f0 Faulting application start time: 0x01cdf4f387b5fa07 Faulting application path: C:\FSX\fsx.exe Faulting module path: C:\FSX\TCAS2v7.dll Report Id: 6a9ea0f8-60f1-11e2-9d1e-90e6baeed388 The reporting fault module is the TCAS2v7.dll......... I have no idea what this means, other than something to do with the TCAS system! Any help would be appreciated, Regards Matt Hardy PS, I should say that that crash happens at the same time, always as I establish on the localiser and begin to follow the glide path.

Thanks for the reply Bryan, To answer your question I am trying to assign Capslock to the prop sync via fsx, as I understand it the fsuicp free version does not have any key assignment functionality. The problem seems to be centred around fsx only being able to assign 1 key to 1 task, it tells me that it will be removed from one and assigned to the other. I will try another key assignment but fear I will have the same issue. I have already reinstalled pmdg sp1c and fs2crew I have even edited the HTML for the controls in fsx to have the key on both functions but it self corrects the first time you boot fsx. Any other ideas? Regards Matt Hardy

Oh yes.....

Help! Hi, I have been using the fs2crew on my pmdg perfectly for a long time. My VA have recently changed their setup and we now fly with kACARS and we also fly using fsconnect. Since installing kACARS, fsuipc and pilot assistant I have had a plethora of issues, most of which have now been sorted but one remains.... In fsconnect sessions I use the CAPSLock key as my transmit key (fsx default) and before all the changes I assigned CAPSLOCK to prop sync on/off to give me the soft mute functionality while I transmit. This stopped working, so I went back into key assignments and noticed that CAPSLOCK was assigned to Transmit, but not propsync on/off, so I reassigned it, except it then deletes it from Transmit.... and vice versa... It wasn't like this before!! So I can either softmute and not transmit, or transmit but not soft mute.... Arrrrrrgh Is this an fsuipc issue? If so then i'm stuffed, because I don't even know what it does. BTW, psuicp is the free version with no access to change anything Please help Kind regards Matt Hardy

Help! Hi, I have been using the fs2crew on my pmdg perfectly for a long time. My VA have recently changed their setup and we now fly with kACARS and we also fly using fsconnect. Since installing kACARS, fsuipc and pilot assistant I have had a plethora of issues, most of which have now been sorted but one remains.... In fsconnect sessions I use the CAPSLock key as my transmit key (fsx default) and before all the changes I assigned CAPSLOCK to prop sync on/off to give me the soft mute functionality while I transmit. This stopped working, so I went back into key assignments and noticed that CAPSLOCK was assigned to Transmit, but not propsync on/off, so I reassigned it, except it then deletes it from Transmit.... and vice versa... It wasn't like this before!! So I can either softmute and not transmit, or transmit but not soft mute.... Arrrrrrgh Is this an fsuipc issue? If so then i'm stuffed, because I don't even know what it does. Please help Kind regards Matt Hardy

Hi Bryan, Thanks for the tip, one small propblem though, the "Re-set Flight" option is greyed out... bugger! I think this may be a setting thats either allowed or disallowed by the HOST. However, if I end the flight and return to the briefing room and join the session again then it seems to work :-) Going to do a full setup and flight from cold and dark to shutdown and will report back. Regards Matt

Hi, I am fairly new to this forum so apologies if I ask questions that have already been answered. I currently run FSX with Active Sky 2012, ezdok, and fs2crew. I recently updated to fs2crew 1.5 and I am receiving an "SDK failed to initialise" but only when trying to join my Airlines LAN network. It works fine in freeflight. I have tried all of the following soloutions. 1: Reinstalled SP1C for the PMDG 737 NGX then reinstalling fs2crew 2: Reinstalled the whole 737-800/900 package then reinstalling fs2crew 3: Tried loading a stock aircraft first then global disabling ezdok and reloading pmdg and initialising fs2crew 4: All the other suggestions that I have found. The only major difference between freeflight and the LAN seems to be that when you join a LAN session you join in "paused" mode and have to un-pause to start setting up. Ezdok as we know forces a vc view at the start, but hitting F10 and switching to 2D as you enter the game seems to do the trick in freeflight and fs2crew will load. I wonder if entering the LAN paused, unpausing and hitting F10 is where the error starts. Any help would be hugely appreciated, is there a way of forcing ezdok to start in 2d? This bug needs sorting Regards Matt Hardy

Ok getting seriously frustrated now... I am getting a blue screen when I start teamspeak three with fs2crew running and connected to vatsim.... even if I connect to teamspeak first then start fs2crew I get the blue screen. The log states that "A clock interrupt was not received from a secondary processor" any help would be greatly appreciated Regards Matt HArdy

Hello, I am currently having issues with fs2crew which I downloaded today. I am flying the PMDG 737 NGX and using fs2crew for that model (voice) and everything goes swimmingly right up to the point in the pre-flight checklist where the FO asks "CDU preflight"... I reply "checked" and he then says "you may want to check that" Also, if i attempt to start engines I am told "engines are not configued for start.... After reading numerous form posts i am none the wiser... this is what I have done so far: Uninstalled EZDOK Deleted fsx.config updated pmdg airac cycle to current version re-installed PMDG sp1c for ngx ensured that fsx starts with default aircraft and starts in 2D cockpit mode I am just so frustrated.... There doesn't appear to be anything wrong with the info I am entering into the FMC (I have tried a few different routes) and I am following the instructions in the fs2crew manuals to the letter. It just seems that the FO or myself is leaving something out of the proceedures. Please accept my apologies if I am duplicating a question but I cannot find an answer anywhere... Incidentally, if I run the fs2crew config manager I always get a warning about ensuring I update the pmdg to sp1c... Not sure if it would do this every time regardless but wondered if there is an issue with the update from pmdg and if so is there a way of doing a fresh install of sp1c (other than a full install of pmdg737ngx, as i would have to send a ticket and request a fresh download of the package) I really hope someone can help regards Matt Windows 7 (64) I7 quad core 9 gig ram