Good evening from The Netherlands,Great product you've made Bryan, It ads a new dimension to my flying experience.However there is still one major problem. Since I installed the PIC version of Fs2crew, my FSX crashes often. I enclosed a pic of what happens.As you can see I have FsPassengers and Radar Contact running as well as REX 2.0. This crash occured when I clicked the FsPassengers tab but I also have had it right after I took off. I would also like to add that this all occured when in windowed view, I haven't yet tried it in full screen.Hope you can help because this is a great product.Thanks in advanceMark

Hi Mark,You said the crash occurred when you hit the FS Passengers tab. Have you also tried contacting FS Passengers?When was the last time you used the 737 PIC before using FS2Crew?What happens if you don't hit the FS Passengers tab?We never had crashes reported during beta testing, so it's hard to say. Do you know how to run Event Viewer? You can get more info there on the specific file associated with the CTD.Cheers,

Hi again,Well I tried a couple other flights but I can't really say what is the cause.Even with FsPassengers off and in full screen mode it crashes. It is completely at random so it can occur at the gate or after takeoff. Haven't completed a single flight. I just need to find the cause. Could you please explain more about that Event Viewer maybe it can determine a cause.Many thanksMark

Hi Mark,We have enough FS2Crew 737 PIC users now to know that this appears to be system specific as other users aren't experiencing crashes.The randomness might suggest a memory issue. Please do this:1. Open the FS2Crew 2010 Config Manager.2. De-activate the FS2Crew panel.cfgs via the Panel CFG manager.3. That will take the FS2Crew gauges off the 737 PIC's panel.cfgs, and FS2Crew will not load.Try making a flight then.Regarding event viewer, please email me and I'll explain in detail: [email protected],

Hi thereThanks for the fast responces so far.I can now confirm that the problem lies within Radar Contact. I tried flights with FsPassengers off and Radar Contact off and everything went fine. Then I did a flight with only FsPassengers active, that went fine as well. But the flight with Radar Contact on crashed when queing for takeoff.Also the flight with everything on except Fs2crew being disabled went fine so it has definetly something to do with Radar Contact. Just a question has Fs2crew been tested with Radar Contact?Regarding the event viewer I will sent you an e-mail.ThanksMark

I'm not really much of a system specialist and don't have experience on Vista or W7, but looking at the list of resource intensive addons you are running it may also be a case of the system running out of resources and manifesting itself this way.Are you running a 32-bit or 64-bit operating system?

Hi thereThanks for the fast responces so far.I can now confirm that the problem lies within Radar Contact. I tried flights with FsPassengers off and Radar Contact off and everything went fine. Then I did a flight with only FsPassengers active, that went fine as well. But the flight with Radar Contact on crashed when queing for takeoff.Also the flight with everything on except Fs2crew being disabled went fine so it has definetly something to do with Radar Contact. Just a question has Fs2crew been tested with Radar Contact?Regarding the event viewer I will sent you an e-mail.ThanksMark

Well, I'm glad you narrowed it down and I'm glad it's not FS2Crew.However, we have a lot of users who use Radar Contact.As mentioned by Kimmo, just a wild guess because I don't know about your system specs, but you might be pushing your system too hard. How much memory do you have?If you're running a lot of addons with FSX, you're going to want a pretty good system with lots of memory and horsepower.Cheers,

To add a touch of a little more technical explanation on what may be happening, here is a good link http://www.fsdeveloper.com/wiki/index.php?title=OOM_ErrorWhile you may not be experiencing an OOM error message as such, I have understood that the manifestation of it is sometimes a fatal error or just a crash to desktop.Due to virtual memory management reasons on 32-bit systems, FSX is still extremely resource intensive even on powerful computers with loads of physical memory, so in order to run a considerable amount of add on programs as in your case, you may need to consider a 64-bit operating system and/or a second computer to run auxilliary programs (radar contact, fspax, weather programs.. etc.) over network.

Hi thereThanks for all the responses.My system has got the following specs:Intel E8500 @ 4.0 ghz2x 4850 512ddr2 xfire8 gb of ddr2 1066Vista 64-bitAnd the rest is I believe not relevant.Could it be that FSX is limited to a certain amount of memory it can use?If so could I raise that amount.Thank you guysMark

Make sure you're using the version of the Wilco 737 PIC that was specially updated for Vista. There is a special version for Vista users (I assume Win 7 too).Cheers,

OkayI just not-finished a flight because of a crash again but for the third time it happened when I hit one of the menu tabs (the ones you bring up with alt). Just when FSX wanted to restart i recieved this error message:I also reinstalled the Wilco PIC again by downloading the latest release from wilcopub.com and yes this is the vista version.************** Tekst van uitzondering ************** ''Uitzondering'' means ''exception''System.Runtime.InteropServices.COMException (0xC000013C): Uitzondering van HRESULT: 0xC000013C bij System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) bij Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveDispatch(SignalProcDelegate pfcnSignal) bij Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveMessage() bij rexwxengine2.controls.ucLoadAircraftLocation.DefWndProc(Message& m) Rex engine? bij System.Windows.Forms.Control.WndProc(Message& m) bij System.Windows.Forms.ScrollableControl.WndProc(Message& m) bij System.Windows.Forms.ContainerControl.WndProc(Message& m) bij System.Windows.Forms.UserControl.WndProc(Message& m) bij System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) bij System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)************** Geladen assembly's **************mscorlib Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.4200 (NetFxQFE.050727-4200) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll----------------------------------------rexwxengine2 Assembly-versie: 2.0.0.0 Win32-versie: 2.0.2009.0803 CodeBase: file:///D:/Program%20Files%20(x86)/Real%20Environment%20Xtreme/rexwxengine2.exe----------------------------------------System.Windows.Forms Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.4016 (NetFxQFE.050727-4000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll----------------------------------------System Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.4016 (NetFxQFE.050727-4000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll----------------------------------------System.Drawing Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.4016 (NetFxQFE.050727-4000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll----------------------------------------Microsoft.FlightSimulator.SimConnect Assembly-versie: 10.0.61242.0 Win32-versie: 10.0.61355.0 (fsx-sp1.20070510-2038) CodeBase: file:///C:/Windows/assembly/GAC_32/Microsoft.FlightSimulator.SimConnect/10.0.61242.0__31bf3856ad364e35/Microsoft.FlightSimulator.SimConnect.dll----------------------------------------msvcm80 Assembly-versie: 8.0.50727.4053 Win32-versie: 8.00.50727.4053 CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d08d7da0442a985d/msvcm80.dll----------------------------------------System.Xml Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.4016 (NetFxQFE.050727-4000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll----------------------------------------System.Configuration Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.4016 (NetFxQFE.050727-4000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll----------------------------------------System.Data Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.4016 (NetFxQFE.050727-4000) CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll----------------------------------------mscorlib.resources Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.4200 (NetFxQFE.050727-4200) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll----------------------------------------System.Windows.Forms.resources Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.4016 (NetFxQFE.050727-4000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_nl_b77a5c561934e089/System.Windows.Forms.resources.dll----------------------------------------So could it be that REX causes the crashes?I'll test it out now.Also why could FSX crash precisely when hitting one of the tabs? Is this a common issue?Thanks in advanceMark

Hmm.. most certainly looks like a problem with REX. I don't own it, but have you tried any of these, especially the top one that deals with HRESULT errors?http://realenvironmentxtreme.com/forum/index.php?board=20.0

Hi Mark,I have REX installed and I have no problems.That crash report, though, is definitely pointing to REX.I'd contact the REX developers. Maybe they have some idea.Cheers,

Good day again,after spending a lot of time searching for potential problems I think I finally may have found a cause and potential solution.After some more testing flights it became evident that the crash occurs when hitting one of the menu pull downs in-game.When reviewing the crash reports it kept up saying the cause lies in the uiautomationcore.dll .After doing some research on the internet I came across a couple of forum threads which indicate that the problem is a common issue.http://forums1.avsim.net/index.php?showtopic=249211&st=0http://forums.flightsim.com/vbfs/showthread.php?t=202199But these problems seem to be Windows 7 only and since I am still running Vista 64-bit I can't tell for sure whether or not this may be the cause and solution for my in-game menu crashes, but it is certainly my best guess.So could someone please provide a uiautomationcore.dll file for me so that I can replace the one which may be corrupt with a working one to see if the dll is causing my problems?If it won't work I think I will contact REX to see if they can provide help.All the best and thanks in advance,Mark

Good day again,after spending a lot of time searching for potential problems I think I finally may have found a cause and potential solution.After some more testing flights it became evident that the crash occurs when hitting one of the menu pull downs in-game.When reviewing the crash reports it kept up saying the cause lies in the uiautomationcore.dll .After doing some research on the internet I came across a couple of forum threads which indicate that the problem is a common issue.http://forums1.avsim.net/index.php?showtopic=249211&st=0http://forums.flightsim.com/vbfs/showthread.php?t=202199But these problems seem to be Windows 7 only and since I am still running Vista 64-bit I can't tell for sure whether or not this may be the cause and solution for my in-game menu crashes, but it is certainly my best guess.So could someone please provide a uiautomationcore.dll file for me so that I can replace the one which may be corrupt with a working one to see if the dll is causing my problems?If it won't work I think I will contact REX to see if they can provide help.All the best and thanks in advance,Mark

Hi Mark,Here's a download link for that DLL. Download it at your own risk:http://www.search-dll.com/dll-files/downlo...oncore.dll.htmlPersonally, though, your system sounds like it has problems.My advice: Start start fresh. Do a clean install of Windows 7 64 (dump Vista), and re-install everything fresh.I run Win 7 64 with REX and numerous other addons and it works brilliantly.