Occassional (annoying) crash

[Conceit]

Hello Forum!

I just bought FlyInside FSX pro 1.71 and quite often, usually when playing a bit, like 20 minutes, and seemingly when I'm preparing to land (lower altitude, more textures?), I encounter a crash. The message says it's in "Rendering\TextureQueueSharedSurface.cpp:152". System: Win 10, GTX 1070, 16 GB, no overclocking, Oculus CV1, otherwise very reliable system (also under load). Any advice or information for further diagnostics appreciated.

[Tony]

Are you changing settings whilst flying at all ? Do you get an error log in the appdat/roaming/flyinside folder at all ? Do you have any camera addons or anything hardware heavy for fsx ? Anything running in the background mate ?

[Conceit]

Tony, I didn't change any Flyinside settings in that session, but I generally, I deactivated ASW, set MSAA to 2x and deactivated audio controls (see below). Before flight I may have changed controller assignments in FSX. There are no other add-ons than those in the Steam version (missions). There is nothing particular bad in the background, but maybe geForce experience in the tray (not recording, no "video-proof"), and VoiceMeeter, and I had to deactivate the FlyInside sound settings at all, as this does not work with VoiceMeeter for some reason that I could not figure out yet*.

The last lines of the error log say (full log via pm?):

1662.5 Hooks\FSX\D3D9\Rendering\Context.cpp 279 D3D9Tex { w = 32, h = 32, levels = 1, usage = 0, fmt = 21, pool = 2, handle = 006FF118}
1662.5 Hooks\FSX\D3D9\Rendering\Context.cpp 284 D3D9Tex { w = 32, h = 32, levels = 1, usage = 1, fmt = 21, pool = 0, handle = 00000000}
1665.45 Hooks\FSX\D3D9\Rendering\Context.cpp 279 D3D9Tex { w = 32, h = 32, levels = 1, usage = 0, fmt = 21, pool = 2, handle = 006FF118}
1665.45 Hooks\FSX\D3D9\Rendering\Context.cpp 284 D3D9Tex { w = 32, h = 32, levels = 1, usage = 1, fmt = 21, pool = 0, handle = 00000000}
1742.73 Utils\Asserts.cpp 70 FlyInside Fatal Error Encountered (-2005270523, 0)
Rendering\TextureQueueSharedSurface.cpp: Line 152
Please post this message to http://flyinside-fsx.com/forum/
Be sure to include what hardware, software, and versions you are running

On another log:

1026.54 Hooks\FSX\D3D9\Rendering\Context.cpp 284 D3D9Tex { w = 2, h = 2, levels = 1, usage = 1, fmt = 21, pool = 0, handle = 00000000}
1026.54 Hooks\FSX\D3D9\Rendering\Context.cpp 279 D3D9Tex { w = 261, h = 80, levels = 1, usage = 0, fmt = 21, pool = 2, handle = 0040EEB4}
1026.54 Hooks\FSX\D3D9\Rendering\Context.cpp 284 D3D9Tex { w = 261, h = 80, levels = 1, usage = 1, fmt = 21, pool = 0, handle = 00000000}
1073.7 DesktopCapture\SubwindowCatcher.cpp 177 Ignoring window: 0014007C Title: [] Class: []
1073.7 DesktopCapture\SubwindowCatcher.cpp 177 Ignoring window: 00150C16 Title: [] Class: []
1073.7 DesktopCapture\SubwindowCatcher.cpp 177 Ignoring window: 00150C18 Title: [Default IME] Class: [Default IME]
1350.41 Utils\Asserts.cpp 70 FlyInside Fatal Error Encountered (-2005270523, 0)
Rendering\TextureQueueSharedSurface.cpp: Line 152
Please post this message to http://flyinside-fsx.com/forum/
Be sure to include what hardware, software, and versions you are running

I also noticed that every time the crash occurs, the windows notification sound gets played, but maybe that's just the upcoming crash report causing this. There is no particular action (button press etc.) I take when this happens. Just lowering altitude to downwind leg level in a Cessna C208B near a small airport.


* I couldn't get FlyInside to route sound through the VoiceMeeter audio driver. It's the system's default audio output and works flawfless otherwise. With Flyinside audio controls active, all FSX sound is muted. So I deactivated the audio controls in FlyInside.

[Tony]

I think a few months ago someone posted a conflict with voicemeter? Can you try deactivating that whilst using flyinside and see if the crashes continue. Also the windows bong usually means an OOM error ?

[Conceit]

Tony, I updated my system (there were pending Win10 and geforce driver updates), and during my last session I did not encounter any crash. Maybe it's gone now, but as this occured randomly, I cannot certainly say. If I encouter this again, I will try removing VoiceMeeter (though I think it has nothing to do with it, but never know). We'll see.

Off topic: Could you add support to select the sound device instead of completely deactivating the sound controls? Or simply identify the sound device set up in FSX, alternatively?