The Home of FlyInside Flight Simulator FFS FSX P3D and X-PLANE Message Board

FlyInside crashes on startup with this error in the log:

0.00984 Logging\ConfigurationLogger.cpp 113 Name: NVIDIA GeForce GTX 980 DeviceId: 5056 VendorId: 4318 Flags: 0 Dedicated System: 0 Dedicated Video: 3221225472 Shared: 1073676288
0.00991 Logging\ConfigurationLogger.cpp 127 Output 0 Name: \\.\DISPLAY1 Attached: 1 Rotation: 1 Position: 0x0 Size: 2560x1440

5.2268 DesktopCapture\SubwindowCatcher.cpp 177 Ignoring window: 000D05FA Title: [TurboVHelp] Class: [TurboVHelp]
5.22683 DesktopCapture\SubwindowCatcher.cpp 177 Ignoring window: 00280154 Title: [Master] Class: [Master]
5.22691 DesktopCapture\SubwindowCatcher.cpp 177 Ignoring window: 00390134 Title: [DIEmWin] Class: [DIEmWin]
5.22694 DesktopCapture\SubwindowCatcher.cpp 177 Ignoring window: 000A0176 Title: [] Class: []
5.22697 DesktopCapture\SubwindowCatcher.cpp 177 Ignoring window: 00260202 Title: [] Class: []
5.227 DesktopCapture\SubwindowCatcher.cpp 177 Ignoring window: 0039012E Title: [Jump List] Class: [Jump List]
5.22703 DesktopCapture\SubwindowCatcher.cpp 177 Ignoring window: 00080952 Title: [Headset Mirror] Class: [Headset Mirror]
5.22706 DesktopCapture\SubwindowCatcher.cpp 177 Ignoring window: 000B092E Title: [Headset Window] Class: [Headset Window]
5.2271 DesktopCapture\SubwindowCatcher.cpp 177 Ignoring window: 000709A4 Title:
[D:\Steam\SteamApps\common\SteamVR\bin\win32\vrserver.exe] Class: [D:\Steam\SteamApps\common\SteamVR\bin\win32\vrserver.exe]
21.5149 Utils\Asserts.cpp 64 FlyInside Fatal Error Encountered (-2147024882, 0)
DesktopCapture\GDICaptureSource.cpp: Line 54

OR it just crashes and the event viewer has:

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: d3d9.dll, version: 0.0.0.0, time stamp: 0x5703ca68
Exception code: 0xc000001d
Fault offset: 0x0005f254
Faulting process id: 0x1e98
Faulting application start time: 0x01d1a2a8870a83df
Faulting application path: D:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: D:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\d3d9.dll
Report Id: cc4fa851-0e9b-11e6-934a-010101010000

I've tried removing and reinstalling FSX (from DVD, not the Steam version), running SteamVR first, running without SteamVR, running without PrecisionX16, with ... So far nothing is making it work.

I'm running a EVGA NVIDIA GTX 980 on Windows 7 x64 with 32G RAM and a ROGSWIFT GSYNC monitor. No other SteamVR titles are having issues on this system.

Hi mate and welcome. I see you are using the DVD version of FSX? Do you have the 2 service packs plus acceleration installed ? Flyinside runs best with the steam version and it usually is on sale for about 5 dollars or so. But the boxed version should still work ok ? Just make sure you have the service packs.

Tony

Thank you for posting the crash log, that's a very good start in figuring this out

• Make sure you have Windows 7 SP2 installed
• Check that you have the latest SPs for FSX installed as Tony mentioned
• Are your monitor and Vive both plugged into the same GTX 980? If not that could cause this issue.

The error itself could be an OOM. Is there any chance that you're running a lot of add-ons in FSX, and that it could be near the 3-4GB 32-bit limit before FlyInside was added (bumping it over)? I don't think it's an OOM, there are a few different conditions which can trigger a similar error-code.

If you upload/attach your full log.txt I may get a better insight into the issue.

Thanks,
Dan

I purchased the Steam version and tried again, but had the same result. I'm definitely running SP2 and the HMD is also attached to the GTX980. I also have a GTX690 as a secondary card, but this shouldn't effect the HMD at all.

I thought it might be add-ons so I completely removed and deleted every FSX directory, including the User settings. The Steam is in a new directory. The HMD is activate and the initial window is displayed, but then turns grey and either the message box with the error at line 54 is shown or a generic error is shown and that second entry is in the event viewer.

Attached is the full log output of the latest run attempt.

Hi mate , is the 690 set as sli or separate use by itself? Does flyinside see that card on start up ?

Tony

The 690 is operating separately. I left it in after installing the new card so that I could use it for extra monitors, dedicated physx and extra CUDA core processing.

I upgraded to a GTX 1080 and tried the new 1.51, but still get the same error message on line 54 "GDICaptureSource.cpp". I noticed that someone else was able to solve a similar issue by installing Windows 10 (which I have no plans to do). By any chance are using this interface for screen capture:

https://msdn.microsoft.com/en-us/librar ... 87(v=VS.85).aspx

If so, it doesn't work with Windows 7 and a standard BitBlt call would be needed instead.

FlyInside falls back to plain old GDI for screen-capture on Windows 7 so that shouldn't be the problem, but that's failing. I'm suspicious that somehow the 690 is throwing a wrench into things but I'm not sure. Are you able to test with the 690 either disabled or removed? Sorry, I know that's a pain

When I installed the 1080, I replaced the 690 with the 980 so I still have 2 video cards installed (independently), but I've yet to have that be an issue for anything else. I also have Virtual Desktop installed and I believe it uses the same fallback option for Windows 7 and appears to work. I could try removing the 980 to see if it helps but even if that worked I'd still choose to have it installed as it's used for other non-gaming tasks.

The only other odd memory issue I've run into (rarely) is if an application attempts to directly allocate Virtual Memory as I have Paging Size set to 0 (with 32G of ram in a 64 bit system, it's an unnecessary relic of the Win32 api). I'll try enable it again later and see if that makes any difference.