Software Server/orbiter.exe runtime error

[E-trexer]

Hey everyone,

I'm getting my new system setup for Orbiter 2016 D3D9 and it seems to be running beautifully. Only abnormality is that after about ten minutes of running, the program freezes. If I alt-tab I can see the runtime error message related to Server/Orbiter 2016. Has anyone experienced this problem? I have been unable to resolve it. Here's my orbiter.log if you want to see my initialization. See attached Runttime error message.

**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 2.91586e-007 sec
000000.000: Found 2 joystick(s)
000000.000: Module AtlantisConfig.dll .... [Build 160828, API 160828]
000000.000: Module AtmConfig.dll ......... [Build 160828, API 160828]
000000.000: Module DGConfigurator.dll .... [Build 160828, API 160828]
000000.000: Module D3D9Client.dll ........ [Build 160830, API 160828]
000000.000: Module LuaMFD.dll ............ [Build 160828, API 160828]
000000.000: Module CustomMFD.dll ......... [Build 160828, API 160828]
000000.000: Module LuaConsole.dll ........ [Build 160828, API 160828]
000000.000: Module ScriptMFD.dll ......... [Build 160828, API 160828]
000000.000: Module DX9ExtMFD.dll ......... [Build 150812, API 100830]
000000.000: Module Rcontrol.dll .......... [Build 160828, API 160828]
000000.000: Module ScnEditor.dll ......... [Build 160828, API 160828]
000000.000: Module OrbiterSound.dll ...... [Build 121120, API 100830]
000000.000: Module TransX2.dll ........... [Build 160907, API 160828]
000000.000: Module BaseSyncMFD.dll ....... [Build 160910, API 160828]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: oapiRegisterMFDMode
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.000: Module BurnTimeMFD.dll ....... [Build 160905, API 160828]
000000.000: Module Glideslope.dll ........ [Build 170415, API 160828]
000000.000: Glideslope module init: version v2.5, date Apr 15 2017
000000.000: Module HUDDrawer.dll ......... [Build 160907, API 160828]
000000.000: Module FlyByWire.dll ......... [Build ******, API 060425]
000000.000: Module LaunchMFD.dll ......... [Build 160905, API 160828]
000000.000: Module ExtMFD.dll ............ [Build 160828, API 160828]
000000.000: 
000000.000: **** Creating simulation session
000000.000: D3D9: [DirectX 9 Initialized]
000000.000: D3D9: 3D-Adapter = NVIDIA GeForce GTX 970
000000.000: D3D9: MaxTextureWidth........: 16384
000000.000: D3D9: MaxTextureHeight.......: 16384
000000.000: D3D9: MaxTextureRepeat.......: 8192
000000.000: D3D9: VolTexAddressCaps......: 0x3F
000000.000: D3D9: NumSimultaneousRTs.....: 4
000000.000: D3D9: VertexDeclCaps.........: 0x30F
000000.000: D3D9: XNA Math Support.......: Yes
000000.000: D3D9: Vertex Texture.........: Yes
000000.000: D3D9: Shadow Mapping.........: Yes
000000.000: D3D9: D3DFMT_A16B16G16R16F...: Yes
000000.000: D3D9: D3DFMT_A32B32G32R32F...: Yes
000000.000: D3D9: D3DFMT_D32F_LOCKABLE...: Yes
000000.000: D3D9: D3DFMT_A2R10G10B10.....: Yes
000000.000: D3D9: D3DDTCAPS_DEC3N........: No
000000.000: D3D9: D3DDTCAPS_FLOAT16_2....: Yes
000000.000: D3D9: D3DDTCAPS_FLOAT16_4....: Yes
000000.000: D3D9: Available Texture Memory = 4080 MB
000000.000: D3D9: [3DDevice Initialized]
000000.000: D3D9: [Loading Constellations]
000000.000: D3D9: [D3D9Client Initialized]
000000.000: Joystick throttle disabled by user
000000.000: Module Sun.dll ............... [Build 160828, API 160828]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 160828, API 160828]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 160828, API 160828]
000000.000: Module VenusAtm2006.dll ...... [Build 160828, API 160828]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 160828, API 160828]
000000.000: Module EarthAtmJ71G.dll ...... [Build 160828, API 160828]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 160828, API 160828]
ELP82: Precision 1e-005, Terms 116/829
000000.000: Module Mars.dll .............. [Build 160828, API 160828]
000000.000: Module MarsAtm2006.dll ....... [Build 160828, API 160828]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
000000.000: Module Phobos.dll ............ [Build ******, API 060425]
000000.000: Module Deimos.dll ............ [Build ******, API 060425]
000000.000: Module Galsat.dll ............ [Build 160828, API 160828]
000000.000: Module Jupiter.dll ........... [Build 160828, API 160828]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 160828, API 160828]
000000.000: Module Europa.dll ............ [Build 160828, API 160828]
000000.000: Module Ganymede.dll .......... [Build 160828, API 160828]
000000.000: Module Callisto.dll .......... [Build 160828, API 160828]
000000.000: Module Satsat.dll ............ [Build 160828, API 160828]
000000.000: Module Saturn.dll ............ [Build 160828, API 160828]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 160828, API 160828]
SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 160828, API 160828]
SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 160828, API 160828]
SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 160828, API 160828]
SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 160828, API 160828]
SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 160828, API 160828]
SATSAT Titan: Terms 100
000000.000: Module Iapetus.dll ........... [Build 160828, API 160828]
SATSAT Iapetus: Terms 605
000000.000: Module Uranus.dll ............ [Build 160828, API 160828]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
000000.000: Module Miranda.dll ........... [Build ******, API 060425]
000000.000: Module Ariel.dll ............. [Build ******, API 060425]
000000.000: Module Umbriel.dll ........... [Build ******, API 060425]
000000.000: Module Titania.dll ........... [Build ******, API 060425]
000000.000: Module Oberon.dll ............ [Build ******, API 060425]
000000.000: Module Neptune.dll ........... [Build 160828, API 160828]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
000000.000: Finished initialising world
000000.000: Module XR2Ravenstar.dll ...... [Build 160916, API 160828]
000000.000: Module ShuttleA.dll .......... [Build 160828, API 160828]
000000.000: Module ShuttlePB.dll ......... [Build 160828, API 160828]
000000.000: Module DeltaGlider.dll ....... [Build 160828, API 160828]
000000.000: Module LuaInline.dll ......... [Build 160828, API 160828]
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: D3D9: [Scene Initialized]
000000.000: Glideslope module sim start
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: oapiBlt
000000.000: Colour key argument not supported by graphics client
000000.000: ---------------------------------------------------------------
000000.000: Finished initialising panels
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: VESSEL::GetHorizonAirspeedVector
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------

I run an AMD FX6300 3.5GHz
16GB DDR3
GeForceGTX-970
Win 10

 

[dbeachy1]

It is likely caused by one of the add-ons you are running. I would start by testing in a clean installation and then installing one add-on at a time and retesting each time until the crash occurs.

 

[E-trexer]

Solved

It is likely caused by one of the add-ons you are running. I would start by testing in a clean installation and then installing one add-on at a time and retesting each time until the crash occurs.

All my add-ons are standard such as XR fleet, Ummu, Orbiter sound, and MFDs that all sensible orbinauts use. I resolved the problem by reducing my texture bias under terrain resolution from 128 to 64. I've been docked at the ISS and running continuously for 12 hours with no problems now.

However, I find it odd that higher graphics settings (terrain bias at 128) cause this runtime error. Especially since my framerates were very smooth and graphics looked outstanding. You would think lagging framerates would be the first indicator that the system wasn't coping.

 

[kuddel]

There is another D3D9Client specific log file @ ".\Modules\D3D9Client\D3D9ClientLog.html"
Maybe some more details can be found there (after the freeze / crash that is).

 

[jarmonik]

The client can easily run out of memory available for 32-bit app when the resolution is set to 128, that setting is no longer available in the latest builds of the client (maximum is 64)

 

[IronRain]

All my add-ons are standard such as XR fleet, Ummu, Orbiter sound, and MFDs that all sensible orbinauts use. I resolved the problem by reducing my texture bias under terrain resolution from 128 to 64. I've been docked at the ISS and running continuously for 12 hours with no problems now.

That's not what dbeachy1 asked. A clean install would tell you, for example, if the problem is with the Orbiter installation or a setting that might not be Orbiter related. If Orbiter works without add-ons, there might be something wrong with one off the add-ons, and the easiest way to find what could be wrong is to add them one by one. It might be possible that the combination of the location of Orbiter + a specific add-on causes the problems, so this is a great way to start troubleshooting, especially of you come to the forums asking for help.

All my add-ons are standard such as XR fleet, Ummu, Orbiter sound, and MFDs that all sensible orbinauts use.

Please note that this is different for everyone. My Orbiter base installation does not include the XR fleet and/or the same MFD's as you might have. Again, that's why beginning with a vanilla Orbiter installation is a great way to start troubleshooting when you come to the forum for help.