Software Crash to Desktop when clicking on MFD buttions

Chuckosan

New member
Joined
Feb 19, 2011
Messages
18
Reaction score
0
Points
1
Just upgraded my PC and installed O 2016. Running Orbiter Sound and D3D9Client2016-R2-1. This is the most current version of the D9 client I could find. Starts fine. But when I click on any MFD button the program exits to desktop. Suggestions?

**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 1e-007 sec
000000.000: Found 0 joystick(s)
000000.000: Devices enumerated: 9
000000.000: Devices accepted: 7
000000.000: [ ] RGB Emulation (SW)
000000.000: [ ] Direct3D HAL (HW)
000000.000: [x] Direct3D T&L HAL (HW)
000000.000: [ ] Direct3D HAL (Radeon RX 570 Series) (HW)
000000.000: [x] Direct3D T&L HAL (Radeon RX 570 Series) (HW)
000000.000: [ ] Direct3D HAL (Radeon RX 570 Series) #2 (HW)
000000.000: [x] Direct3D T&L HAL (Radeon RX 570 Series) #2 (HW)
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 OrbiterSound.dll ...... [Build 121120, API 100830]
000000.000:
000000.000: **** Creating simulation session
000000.000: DirectDraw interface OK
000000.000: Direct3D interface OK
000000.000: Graphics: Viewport: Fullscreen 1680 x 1050 x 32
000000.000: Graphics: Hardware T&L capability: Yes
000000.000: Graphics: Z-buffer depth: 32 bit
000000.000: Graphics: Active lights supported: 8
000000.000: Loading 15382 records from star database
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 DeltaGlider.dll ....... [Build 160828, API 160828]
000000.000: Module LuaInline.dll ......... [Build 160828, API 160828]
000000.000: Module ShuttleA.dll .......... [Build 160828, API 160828]
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
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: ---------------------------------------------------------------
 

Marijn

Active member
Joined
Mar 5, 2008
Messages
755
Reaction score
166
Points
43
Location
Amsterdam
Are you running Orbiter with just the D3D9 client and no other add-ons installed? Are you launching a default scenario?

---------- Post added at 11:14 PM ---------- Previous post was at 11:08 PM ----------

And you also did activate the D3D9 client, created the symlinks and launched the Orbiter_ng.exe and not Orbiter.exe? Did you try a windowed mode instead of full-screen?
 

Chuckosan

New member
Joined
Feb 19, 2011
Messages
18
Reaction score
0
Points
1
D3D9 active. Used symlinks. Launched ng.exe.

Just tried it in widowed mode and it crashed. Switched to full screen and it crashed. Was able to get it to crash using the MFD buttons in both generic cockpit mode and 2D Panel. Seemed to work ok in VGC. Seems to only be the bottom two buttons on the right side of both MFDs.
 

Chuckosan

New member
Joined
Feb 19, 2011
Messages
18
Reaction score
0
Points
1
None. Clean install. Reinstalled it today. O2016, OSound, New D3D9. That's it.

---------- Post added at 12:19 AM ---------- Previous post was at 12:07 AM ----------

Just did a complete reinstall. Same buttons, same crash. Weird.
 

dbeachy1

O-F Administrator
Administrator
Orbiter Contributor
Addon Developer
Donator
Beta Tester
Joined
Jan 14, 2008
Messages
9,218
Reaction score
1,566
Points
203
Location
VA
Website
alteaaerospace.com
Preferred Pronouns
he/him
I suggest trying it first in a totally clean installation with only Orbiter 2016 (no ObiterSound and no D3D9). If that works, then install D3D9 and retest. As for OrbiterSound, there are known CTD issues with its Radio MFD in Orbiter 2016, so be sure not to use its Radio MFD, at least.
 

Chuckosan

New member
Joined
Feb 19, 2011
Messages
18
Reaction score
0
Points
1
I suggest trying it first in a totally clean installation with only Orbiter 2016 (no ObiterSound and no D3D9). If that works, then install D3D9 and retest. As for OrbiterSound, there are known CTD issues with its Radio MFD in Orbiter 2016, so be sure not to use its Radio MFD, at least.

If I do it that way, I can't test it under ng.exe, right? Doesn't that only work with D3D9 installed?
 

Ripley

Tutorial translator
Donator
Joined
Sep 12, 2010
Messages
3,135
Reaction score
409
Points
123
Location
Rome
Website
www.tuttovola.org
Yes, without D3D9 you just launch orbiter.exe.

Yessir. Built from scratch. Ryzen 2600 w/ RX570 card. 16 GB RAM...
Brand new pc could mean that you miss some of the needed older MS VC++ runtimes.
 
Last edited:

Chuckosan

New member
Joined
Feb 19, 2011
Messages
18
Reaction score
0
Points
1
Yes, without D3D9 you just launch orbiter.exe.


Brand new pc could mean that you miss some of the needed older MS VC++ runtimes.

So, maybe I should skip the 2016 version with D3D9?

---------- Post added at 01:18 AM ---------- Previous post was at 01:05 AM ----------

OK. Interesting. I got it to work fine on a clean install using the base exe file (not ng). Then I added O-Sound. Crash. Could I have a corrupted version of O Sound?

---------- Post added at 01:22 AM ---------- Previous post was at 01:18 AM ----------

Yep. Definitely O Sound that's causing the conflict. both exe and ng work fine without O Sound. Suggestions? Should I NOT be using Orbiter Sound and using, XR Sound instead?

---------- Post added at 03:32 AM ---------- Previous post was at 01:22 AM ----------

Looks like I got it with XR Sound. Thanks everyone for your assistance.
 
Last edited:
Top