Orbiter beta（160412） can not run on win10

[craftyang]

Hello everyone, the 2016 release is very exciting, but i have trouble when running.I have read many articles but still can not solve it.I have download Orbiter beta（160412）and the minimum textures,and installed D3D9Client 23.11 and DirectX runtime 2010.When i run orbiter_ng.exe, it stop when initializing. I don't know what the problem exactly is and really need your help. Thanks!

I am using win10 laptop.Below is the log files.

**** Orbiter.log
000000.000: Build Apr 12 2016 [v.160412]
000000.000: Timer precision: 5.70182e-007 sec
000000.000: Found 0 joystick(s)
000000.000: Module AtlantisConfig.dll .... [Build 150906, API 150906]
000000.000: Module AtmConfig.dll ......... [Build 150906, API 150906]
000000.000: Module DGConfigurator.dll .... [Build 150906, API 150906]
000000.000: Module D3D9Client.dll ........ [Build 160617, API 160412]
000000.000:
000000.000: **** Creating simulation session
000000.000: D3D9: [DirectX 9 Initialized]
000000.000: D3D9: 3D-Adapter = Intel(R) HD Graphics 4000
000000.000: D3D9: MaxTextureWidth........: 8192
000000.000: D3D9: MaxTextureHeight.......: 8192
000000.000: D3D9: MaxTextureRepeat.......: 8192
000000.000: D3D9: VolTexAddressCaps......: 0x3F
000000.000: D3D9: NumSimultaneousRTs.....: 4
000000.000: D3D9: VertexDeclCaps.........: 0x37F
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...: No
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 = 1786 MB
000000.000: D3D9: [3DDevice Initialized]
000000.000: D3D9: [Loading Constellations]
000000.000: D3D9: [D3D9Client Initialized]

----------------------------------------------------------
***install.log
Orbiter installation verification.

w tests to verify a valid
Orbiter installation. Normally, this test needs to be executed
only once after installation. To run it again, execute the
'testinstall' utility in the Install subdirectory.
-----------------------------------------------------
Test 1: Directory structure
Orbiter root directory: E:\SVN\orbiter_beta
Folder Config found.
Folder Meshes found.
Folder Textures found.
Folder Scenarios found.
Folder Doc found.
Folder Script found.
Folder Modules found.
Folder Flights found.
Folder Html found.
Folder Install found.
-----------------------------------------------------
Test 2: C++ runtime libraries
Runtime libraries ok.
-----------------------------------------------------
Test 3: Checking DirectX
Scanning dxdiag output:


Processor: Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz (4 CPUs), ~1.8GHz
Memory: 10240MB RAM
DirectX Version: 12
Card name: Intel(R) HD Graphics 4000
Card name: AMD Radeon HD 8600M Series
DirectX version >= 7 required!
For full DirectX diagnostics, see file dxdiag.log.
-----------------------------------------------------
Orbiter installation verification complete.
Potential problems found.
Please examine the installation log file (install.log)
and fix the problems before launching Orbiter.




when i run 'testinstall' ,it shows that

This diagnostic utility performs a few tests to verify a valid
Orbiter installation. Normally, this test needs to be executed
only once after installation. To run it again, execute the
'testinstall' utility in the Install subdirectory.
-----------------------------------------------------
Test 1: Directory structure
Orbiter root directory: E:\SVN\orbiter_beta
Folder Config found.
Folder Meshes found.
Folder Textures found.
Folder Scenarios found.
Folder Doc found.
Folder Script found.
Folder Modules found.
Folder Flights found.
Folder Html found.
Folder Install found.
-----------------------------------------------------
Test 2: C++ runtime libraries
Runtime libraries ok.
-----------------------------------------------------
Test 3: Checking DirectX
Scanning dxdiag output:

Processor: Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz (4 CPUs), ~1.8GHz
Memory: 10240MB RAM
DirectX Version: 12
Card name: Intel(R) HD Graphics 4000
Card name: AMD Radeon HD 8600M Series
DirectX version >= 7 required!
For full DirectX diagnostics, see file dxdiag.log.
-----------------------------------------------------
Orbiter installation verification complete.
Potential problems found.
Please examine the installation log file (install.log)
and fix the problems before launching Orbiter.

 

[PhantomCruiser]

Does it work in the native graphics mode? Orbiter.exe instead or Orbiter_ng?

Also, when trying Orbiter_ng, are you in full screen or windowed mode? I seem to recall I had CTD in full screen also.

 

[craftyang]

Thanks for reply.I have tried both Orbiter.exe and Orbiter_ng.exe, with full screen and windowed mode, everytime it stopped at initializing. But Orbiter_2012_100830 runs no problem on my laptop.

When run with full screen mode, the log file does show some error message.I guess the problem is with DirectX. But I don't know what exactly the error message mean.Below is the log file.

**** Orbiter.log
000000.000: Build Apr 12 2016 [v.160412]
000000.000: Timer precision: 5.70181e-007 sec
000000.000: Found 0 joystick(s)
000000.000: Module AtlantisConfig.dll .... [Build 150906, API 150906]
000000.000: Module AtmConfig.dll ......... [Build 150906, API 150906]
000000.000: Module DGConfigurator.dll .... [Build 150906, API 150906]
000000.000: Module D3D9Client.dll ........ [Build 160617, API 160412]
000000.000:
000000.000: **** Creating simulation session
000000.000: D3D9: [DirectX 9 Initialized]
000000.000: D3D9: 3D-Adapter = Intel(R) HD Graphics 4000
000000.000: D3D9: MaxTextureWidth........: 8192
000000.000: D3D9: MaxTextureHeight.......: 8192
000000.000: D3D9: MaxTextureRepeat.......: 8192
000000.000: D3D9: VolTexAddressCaps......: 0x3F
000000.000: D3D9: NumSimultaneousRTs.....: 4
000000.000: D3D9: VertexDeclCaps.........: 0x37F
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...: No
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 = 1791 MB
000000.000: D3D9: [3DDevice Initialized]
000000.000: D3D9: ERROR: D3D9Client.cpp Line:2198 Error:-2005530516 pDevice->StretchRect(pTextScreen, NULL, pBackBuffer, &txt, D3DTEXF_POINT)
000000.000: D3D9: ERROR: D3D9Client.cpp Line:2198 Error:-2005530516 pDevice->StretchRect(pTextScreen, NULL, pBackBuffer, &txt, D3DTEXF_POINT)
000000.000: D3D9: ERROR: D3D9Client.cpp Line:2198 Error:-2005530516 pDevice->StretchRect(pTextScreen, NULL, pBackBuffer, &txt, D3DTEXF_POINT)
000000.000: D3D9: ERROR: D3D9Client.cpp Line:2198 Error:-2005530516 pDevice->StretchRect(pTextScreen, NULL, pBackBuffer, &txt, D3DTEXF_POINT)
000000.000: D3D9: [Loading Constellations]
000000.000: D3D9: ERROR: D3D9Client.cpp Line:2198 Error:-2005530516 pDevice->StretchRect(pTextScreen, NULL, pBackBuffer, &txt, D3DTEXF_POINT)
000000.000: D3D9: [D3D9Client Initialized]

 

[reopen]

I am looking for the same answer. I have been running Beta for many months on Win 10 and never had a problem. but all of a sudden it started locking up on me in the start screen. After numerous attempts to start and restart i set it to windowed mode and it seems to be fine... But why? What happened its been perfect, what changed? I had just installed a new GTX 1070 and run some windows updates. but it had worked full screen since that. Just seems like yesterday it just wont start in full screen, has to be windowed. I dont like windowed anything. not sure where to look

 

[jroly]

I know that dx9 client is not working with the latest beta, but dx7 is fine so don't do anymore troubleshooting using dx9 client.

 

[Abloheet]

Jarmoniik still hasnt updated the d3d9client to use the latest r56 beta. the current d3d9 client for beta is still for r55. wait for the r56 version to come out soon. then it will work

 

[Urwumpe]

Jarmoniik still hasnt updated the d3d9client to use the latest r56 beta. the current d3d9 client for beta is still for r55. wait for the r56 version to come out soon. then it will work

There is a new version for this in the beta thread.

 

[craftyang]

I have tried the new version(r57), Orbiter.exe ,window mode,still crash when initializing.

**** Orbiter.log
000000.000: Build Jul 3 2016 [v.160703]
000000.000: Timer precision: 5.70181e-007 sec
000000.000: Found 0 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 (Intel(R) HD Graphics 4000) (HW)
000000.000: [x] Direct3D T&L HAL (Intel(R) HD Graphics 4000) (HW)
000000.000: Module AtlantisConfig.dll .... [Build 150906, API 150906]
000000.000: Module AtmConfig.dll ......... [Build 150906, API 150906]
000000.000: Module DGConfigurator.dll .... [Build 150906, API 150906]
000000.000:
000000.000: **** Creating simulation session
000000.000: DirectDraw interface OK
000000.000: Direct3D interface OK
000000.000: Graphics: Viewport: Window 1530 x 835 x 32
000000.000: Graphics: Hardware T&L capability: Yes
000000.000: Graphics: Z-buffer depth: 32 bit
000000.000: Graphics: Stencil buffer depth: 8 bit
000000.000: Graphics: Active lights supported: 8
000000.000: Loading 15382 records from star database
000000.000: ---------------------------------------------------------------
000000.000: >>> ERROR: DDraw error DDERR_BLTFASTCANTCLIP
000000.000: >>> [OrbiterGraphics::clbkBlt | .\OGraphics.cpp | 1633]
000000.000: ---------------------------------------------------------------

 

[Urwumpe]

Looks more like your GPU driver does not support a specific function used in the DX9 client.

 

[DaveS]

Looks more like your GPU driver does not support a specific function used in the DX9 client.

I wouldn't even call The Intel HD series a GPU. They're IGPUs. Intel added it to the CPU just for the sake of having anything outputting an image. AMD however has stopped with this practice and now requires a dedicated graphics card if you're going with a AMD CPU.

It seems however that craftang has a laptop that has dual GPUs (the IGPU and a dedicated GPU, Radeon HD 8600M). For some reason it isn't engaging the real GPU (the Radeon) when it detects a 3D application. He could try the solutions in these posts: http://www.tomsguide.com/answers/id-2610379/switch-intel-graphics4000-amd-radeon-8570m.html

For reopen: Have you tried re-installing the drivers? Or if that doesn't work, try rolling back to an earlier driver version making sure it's a 100% clean and fresh install.

 

[Urwumpe]

I wouldn't even call The Intel HD series a GPU. They're IGPUs. Intel added it to the CPU just for the sake of having anything outputting an image. AMD however has stopped with this practice and now requires a dedicated graphics card if you're going with a AMD CPU.

It seems however that craftang has a laptop that has dual GPUs (the IGPU and a dedicated GPU, Radeon HD 8600M). For some reason it isn't engaging the real GPU (the Radeon) when it detects a 3D application. He could try the solutions in these posts: http://www.tomsguide.com/answers/id-2610379/switch-intel-graphics4000-amd-radeon-8570m.html

For reopen: Have you tried re-installing the drivers? Or if that doesn't work, try rolling back to an earlier driver version making sure it's a 100% clean and fresh install.

I have the same setup with a Intel HD 5000 in my i7 CPU and a NVidea GTX 670M on top.

It works usually.

 

[Fabri91]

I wouldn't even call The Intel HD series a GPU. They're IGPUs. Intel added it to the CPU just for the sake of having anything outputting an image. AMD however has stopped with this practice and now requires a dedicated graphics card if you're going with a AMD CPU.

...

Are you sure? AMD calls them "APUs", but for all intents and purposes they are CPUs with integrated GPUs.

 

[jedidia]

For some reason it isn't engaging the real GPU (the Radeon) when it detects a 3D application.

I have noticed that orbiter doesn't get started on the strong GPU by default on a dual setup a while ago. Win10 does have a context menu option "run with graphics processor" that shows up when you right-click the exe, and GPU utilities usually let you configure individual exes, so you can note it there to get started with the proper card every time. That would look differently for Radeon and NVidia though, and I'm currently driving NVidia.
Heck, I even had to add visual studio in there, because otherwise I couldn't launch orbiter on the proper card when debugging.