Hey guys so I've been really frustrated with fsx recently. I keep getting the black screen when I alt+enter out of fsx. I'm running REX and when I exit out of fsx I get an error from there but I think that's due to me exiting out of fsx without closing REX first.

 

I've tried replacing the UIAutomationCore.dll (I am running on Windows Vista) but the problem hasn't gone away. It's very strange, like just now at EHAM in the NGX I tried alt+tabbing when it loaded up and it was fine. But then on takeoff fps dropped to 9 from around 30 so I hit alt+enter and the screen went black but I could still here the wind and trim sounds.

 

Other addons I run, other than scenery (I was at default EHAM though) are GSX but I was not using this. I also have the ENB. The only other addon is REX.

 

Any ideas on a fix guys?

 

Kind Regads,

 

Dan

 

Edit: Just tried again and got a fatal error this time. Strange it lets me alt+enter from windowed to full screen with no problems, then I try a minute later and black screen.

 

Recieved framework error:

 

 

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014B

at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveDispatch(SignalProcDelegate pfcnSignal)

at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveMessage()

at rexwxengine2.controls.ucLoadAircraftLocation.DefWndProc(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

at System.Windows.Forms.ContainerControl.WndProc(Message& m)

at System.Windows.Forms.UserControl.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

************** Loaded Assemblies **************

mscorlib

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5448 (Win7SP1GDR.050727-5400)

CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

----------------------------------------

rexwxengine2

Assembly Version: 2.5.2010.38549

Win32 Version: 2.5.2010.1027

CodeBase: file:///C:/Program%20Files%20(x86)/Real%20Environment%20Xtreme%202.0/rexwxengine2.exe

----------------------------------------

System.Windows.Forms

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5453 (Win7SP1GDR.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Drawing

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

Microsoft.FlightSimulator.SimConnect

Assembly Version: 10.0.61259.0

Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)

CodeBase: file:///C:/Windows/assembly/GAC_32/Microsoft.FlightSimulator.SimConnect/10.0.61259.0__31bf3856ad364e35/Microsoft.FlightSimulator.SimConnect.dll

----------------------------------------

msvcm80

Assembly Version: 8.0.50727.6195

Win32 Version: 8.00.50727.6195

CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a/msvcm80.dll

----------------------------------------

System.Xml

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

System.Configuration

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

System.Data

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll

----------------------------------------

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

The black screens were annoying so I got rid of the file entirely and that fixed everything for me. There was a guide on how to do it, there were two of this file in the windows folder. I backed 'em up and deleted them. If I have time later I can search for the tutoria and send you the link.

 

EDIT: I found the little tutorial on how to take ownership of these files to successfully delete them.

 

HERE IS THE FIX: You may have to take ownership of the files if windows stops you from deleting the file. Open CMD prompt and right click to run as administrator and then type in exactly as below substituting your windows login username where it says username:

 

takeown /f C:\Windows\System32\uiautomationcore.dll

 

cacls C:\Windows\System32\uiautomationcore.dll /G username:F

 

takeown /f C:\Windows\Syswow64\uiautomationcore.dll

 

cacls C:\Windows\Syswow64\uiautomationcore.dll /G username:F

 

Now you can just navigate to your syswow64 and system32 folders in windows explorer and after backing up the UIautomationcore.dll files just delete them from your computer. (Remember to delete the Uiatomationcore.dll file in your FSX folder also if you installed it as the fix in other posts.)

 

Here's a direct link to the tutorial if you wish to read it there: http://www.flightsimworld.com/forums/index.php?showtopic=188595

 

I do NOT take credit for this tutorial, I'm just sharing it! Credits go to the respective owner or creator of this tut.

Just out of interest when your ATL & ENTER. after you have done it just hit the enter key once.. let me know

@Jazz Pilot. I did this, and I also loaded up in a ceranado aircraft and there seems to be no problems. But then tried in the NGX and still got the black screen, which suggests it is something to do with the NGX which is causing the problem. I recieved the same error as I posted above.

 

Just out of interest when your ATL & ENTER. after you have done it just hit the enter key once.. let me know

 

I can't as it is now giving me a fatal error and shuts down. Just out of question what dotnet should I be running on/have installed? At the minute I have 2.0, 3.0, 3.5 and 4.0 installed. I did just have 2.0 installed but I was getting the error then and no difference with 2 3 3.5 and 4 installed.

 

It's very weird. Just loaded the ngx up now and not touched anything. Can sit pressing alt+enter switching from windowed to full screen a dozen times and it's fine. But then just now After I'd set up all the fmc for tutorial number 2 and went to go into full screen mode I got the black screen followed by the fatal error. I can't think what's causing it.

Daft questions have you installed the FSUIPC m8 and do you have the correct uiautomation core.dll file in your FSX root folder...

Daft questions have you installed the FSUIPC m8 and do you have the correct uiautomation core.dll file in your FSX root folder...

 

Yes I do. However as it says in this fix which I did earlier "Here's a direct link to the tutorial if you wish to read it there: http://www.flightsim...howtopic=188595

 

" to delete the uiautomationcore.dll from fsx root after doing that fix.

OKay, we may have fixed it *fingers crossed*. Just installed the latest FSUIPC then took off flew around in the ngx kept alt+entering from windowed to full for 5 minutes and no black screen! Hopefully it's fixed!