Problem [SOLVED] Orbiter160828 crashes upon lauching

Raltals

New member
Joined
Mar 29, 2017
Messages
3
Reaction score
0
Points
0
Hello,
I've been away from orbiter for quite some time. Today I deceided to try out the shiny new Orbiter 2016 :thumbup: after discovering it has been released since last year. However, I'm encountering some problem trying to get it up and running:

Basic infomation:
  • AMD E-450 APU with Radeon HD6320 intergrated graphics
  • 4 GB Memory
  • Windows 7 32-bit

What I did:
1. Download the msi package;
2. Install the msi package using default param;
3. Run orbiter.exe
3. Click "Launch Orbiter"

What happened:
Popup "orbiter.exe has stopped working".

Expected result:
It should launch without any problem.

Further infomation:

Problem details in the popup "orbiter.exe has stopped working."
Code:
  Problem Event Name:    BEX
  Application Name:	orbiter.exe
  Application Version:	0.0.0.0
  Application Timestamp:	57c23433
  Fault Module Name:	MSVCR90.dll
  Fault Module Version:	9.0.30729.4940
  Fault Module Timestamp:	4ca2ef57
  Exception Offset:	00051380
  Exception Code:	c0000417
  Exception Data:	00000000
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	2052
  Additional Infomation 1:	2650
  Additional Infomation 2:	26504345eb1e9f874bf11624665179d8
  Additional Infomation 3:	5024
  Additional Infomation 4:	5024079be90418018a11bc63729ca9ff

Orbiter.log
Code:
**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 6.21918e-007 sec
000000.000: Found 1 joystick(s)
000000.000: Devices enumerated: 6
000000.000: Devices accepted: 5
000000.000: [ ] RGB Emulation (SW)
000000.000: [ ] Direct3D HAL (HW)
000000.000: [x] Direct3D T&L HAL (HW)
000000.000: [ ] Direct3D HAL (AMD Radeon HD 6320 Graphics) (HW)
000000.000: [x] Direct3D T&L HAL (AMD Radeon HD 6320 Graphics) (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: 
000000.000: **** Creating simulation session
000000.000: DirectDraw interface OK
000000.000: Direct3D interface OK
000000.000: Graphics: Viewport: Fullscreen 1024 x 768 x 16
000000.000: Graphics: Hardware T&L capability: Yes
000000.000: Graphics: Z-buffer depth: 16 bit
000000.000: Graphics: Active lights supported: 8
000000.000: Loading 15382 records from star database


Is there any further infomation I need to provide?

Thanks!
 
Last edited:
I suspect the problem is this:

Code:
AMD E-450 APU with Radeon HD6320 integrated graphics

...since many integrated graphics drivers have problems with DirectX7. You could try running the D3D9 client.
 
And I still suspect it's the old version of Visual Studio 2008 redistributable. The number of light sources is listed as 8, unlike in other with integrated graphics cards (which listed either -1 and 2147483647 or 4294967295 after a patch fixing the issue), which caused most of the problems previously.

The version of MSVCR90.dll isn't the newest:
  • Installed: 9.0.30729.[highlight]4940[/highlight]
  • Most recent: 9.0.30729.[highlight]6161[/highlight] (MS11-025)
 
Thanks to all the suggestions. I've tried the following:

1. Downloaded the zip package and extracted it to D:\orbiter2016. Get the same symptom.

2. Downloaded and installed all 6 patches in post #3, reboot, start orbiter, get the same symptom. Note that it's still a BEX error on MSVCR90.dll, but the fault module version is now 9.0.30729.6161, showing that it is indeed upgraded. Other than that, I don't see other difference in the log files. logs: http://paste.ubuntu.com/24281331 http://paste.ubuntu.com/24281332

3. (re)Installed DirectX 9.0c June2010 redist

4. Deployed D3D9Client2016-R1

5. Launch orbiter-ng.exe, enable D3D9Client module, launch orbiter. Got the same BEX error on MSVCR90.dll. logs: http://paste.ubuntu.com/24281362 http://paste.ubuntu.com/24281370
 
Now I can see better what might be the issue. I didn't check the locale code earlier as everything was in English, but as I see it's Chinese, that changes what I suspect to be the issue.

Try this solution: <PostID: 528777>
 
Now I can see better what might be the issue. I didn't check the locale code earlier as everything was in English, but as I see it's Chinese, that changes what I suspect to be the issue.

Try this solution: <PostID: 528777>

Thank you very much. In fact I manually translated the BEX error message to English before posting since my system locale is Chinese(PRC). I tried changing the locale setting as per post #528777 and it works like a charm.

Many thanks for helping me diagnosing the problem! :speakcool:
 
Back
Top