Problem White Screen on Startup?

[Tchail]

Hello Everyone,

It's been a while since I did anything in Orbiter, but recently when I tried to start it, I was greeted with a white screen when I started a scenario.

I have tried this with both Orbiter 2016 & 2010 with the same result.

I even tried downloading a clean copy of Orbiter 2016 and starting it fresh install. The same thing happened.

Has anyone run into this before?

I have a NVidia GeForce GTX 870M graphics card with 3Gb of RAM. The drivers have been updated, and I have setting Orbiter to run on that card over the onboard graphics.

Any help would be appreciated!

-Tc

 

[IMHiggins]

I think the problem is in the drivers. To get started, completely remove the old driver versions. After this, install ALL updates.

 

[Tchail]

I completely removed all of my video drivers, then reinstalled fresh.

Unfortunately, I'm getting the same problem - A white screen when I try to launch Orbiter 2016 from the menu.

So I tried completely uninstalling Orbiter 2010 & 2016, and doing a fresh reinstall using the msi installer.

Same result - A white screen on startup.

Here are the results from Orbiter.log:

+++++++++++++++++++++++++++++

**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 4.27653e-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 (Intel(R) HD Graphics 4600) (HW)
000000.000: [x] Direct3D T&L HAL (Intel(R) HD Graphics 4600) (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 1920 x 1080 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
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: Module ShuttlePB.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

 

[Marijn]

Try installing the D3D9 client. Download it from https://www.tuttovola.org/index.php?...view;down=1104, unzip the archive in your Orbiter root folder, launch the Orbiter_ng.exe application (from now on, so you could delete the Orbiter.exe file). On the launchpad, go to Modules and activate the D3D9 client.

 

[Tchail]

Okay - I think I have a lead on the problem.

Orbiter 2010 & 2016 don't seem to be compatible with DirectX 12.

I've run into a similar problem with Microsoft Flight Simulator X-Acceleration. That program won't run unless I check the Preview DirectX 10 box under the Visual Display Settings tab.

I tried running the Orbiter 2016 Server with the D3D9 Client in windowed mode, but all I get is a spinning circle.

Any thoughts?

BTW: Here's the contents of my DirectX Diag:

+++++++++++++++++++

------------------
System Information
------------------
Time of this report: 12/26/2018, 22:27:32
Machine name: SERENITY
Machine Id: {9E0EAF3D-69F2-4A7F-8788-EF29E43123E8}
Operating System: Windows 10 Pro 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804)
Language: English (Regional Setting: English)
System Manufacturer: ASUSTeK COMPUTER INC.
System Model: G750JS
BIOS: BIOS Date: 07/17/14 14:42:51 Ver: 04.06.05 (type: BIOS)
Processor: Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz (8 CPUs), ~2.4GHz
Memory: 32768MB RAM
Available OS Memory: 32652MB RAM
Page File: 14546MB used, 50872MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Supported
DxDiag Version: 10.00.17134.0001 64bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Display Tab 2: No problems found.
Display Tab 3: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)



Etc.....

 

[Marijn]

Did you create the symlinks? (video=>advanced). If that isn't the problem, I think you need to install DX 9.03: https://www.microsoft.com/en-us/download/details.aspx?id=35

Next time, if you have long files to share with us, put them between code tags like so

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate eget, arcu. In enim justo, rhoncus ut, imperdiet a, venenatis vitae, justo. Nullam dictum felis eu pede mollis pretium. Integer tincidunt. Cras dapibus. Vivamus elementum semper nisi. Aenean vulputate eleifend tellus. Aenean leo ligula, porttitor eu, consequat vitae, eleifend ac, enim. Aliquam lorem ante, dapibus in, viverra quis, feugiat a, tellus. Phasellus viverra nulla ut metus varius laoreet. Quisque rutrum. Aenean imperdiet. Etiam ultricies nisi vel augue. Curabitur ullamcorper ultricies nisi. Nam eget dui. Etiam rhoncus. Maecenas tempus, tellus eget condimentum rhoncus, sem quam semper libero, sit amet adipiscing sem neque sed ipsum. Nam quam nunc, blandit vel, luctus pulvinar, hendrerit id, lorem. Maecenas nec odio et ante tincidunt tempus. Donec vitae sapien ut libero venenatis faucibus. Nullam quis ante. Etiam sit amet orci eget eros faucibus tincidunt. Duis leo. Sed fringilla mauris sit amet nibh. Donec sodales sagittis magna. Sed consequat, leo eget bibendum sodales, augue velit cursus nunc, quis gravida magna mi a libero. Fusce vulputate eleifend sapien. Vestibulum purus quam, scelerisque ut, mollis sed, nonummy id, metus. Nullam accumsan lorem in dui. Cras ultricies mi eu turpis hendrerit fringilla. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; In ac dui quis mi consectetuer lacinia. Nam pretium turpis et arcu. Duis arcu tortor, suscipit eget, imperdiet nec, imperdiet iaculis, ipsum. Sed aliquam ultrices mauris. Integer ante arcu, accumsan a, consectetuer eget, posuere ut, mauris. Praesent adipiscing. Phasellus ullamcorper ipsum rutrum nunc. Nunc nonummy metus. Vestibulum volutpat pretium libero. Cras id dui. Aenean ut

Thnx

 

[Tchail]

I edited my previous post to reduce it.

With Orbiter, I created the symbolic links, and tried installing DirectX 9.03, but on that I received a message that "DirectX setup has determined that a newer or equivalent version of DirectX has been installed already. No installation is necessary."

When I try running the Orbiter 2016 Server, I get the same result - a spinning courser that eventually results in Orbiter 2016 Not Responding.

Any suggestions?

 

[Marijn]

and tried installing DirectX 9.03, but on that I received a message that "DirectX setup has determined that a newer or equivalent version of DirectX has been installed already. No installation is necessary."

Do you get a dialog which allows for installing it anyway? If so, I think you should proceed.

 

[kuddel]

You should not use the web-installer! Martijns link is therefore not recommended! It's useless in this case.
The web-installer checks for the higest Direct X version and does not do anything if the pre-installed version is higher (DirectX 12 e.g. is installed).
But DirectX 9 is NOT INCLUDED in any higher Version off Direct X!

Take the link as given in the D3D9Client.pdf!
https://www.microsoft.com/en-us/download/details.aspx?id=8109
After clicking on "download" you should de-select any additional downloads "Microsoft Recommends" so that only "DirectX End-User Runtimes (June 2010)" is left on the left "Download Summary".
Then click on " No thanks and continue DirectX End-User Runtime Web Installer" button. That should let you download "directx_Jun2010_redist.exe".
This direct link might work, but I can not guarantee that. The procedure before however is unchanged for at least 3 years!

Download directx_Jun2010_redist.exe (ca. 95,6 MB) and run it. This will extract the content of the package in any empty directory you want.
Then find a Setup.exe there and run it.
You can delete the contents of the directory after the setup is completed. The directory is just a temporary storage for the installation files.

 

[Marijn]

and does not do anything if the pre-installed version is higher (DirectX 12 e.g. is installed).

Then I expect the dialog won't offer the option to do so.
It's hard to remember these things, because you do them only once on a machine.

 

[kuddel]

Then I expect the dialog won't offer the option to do so.
It's hard to remember these things, because you do them only once on a machine.

Yes it is ugly for us, but for this kind of issues we have this forum :thumbup:

---------- Post added at 22:38 ---------- Previous post was at 22:26 ----------

@Tchail: I've edited my post #9 several times (to make it more clear)...

 

[Tchail]

You should not use the web-installer! Martijns link is therefore not recommended! It's useless in this case.
The web-installer checks for the higest Direct X version and does not do anything if the pre-installed version is higher (DirectX 12 e.g. is installed).
But DirectX 9 is NOT INCLUDED in any higher Version off Direct X!

Take the link as given in the D3D9Client.pdf!
https://www.microsoft.com/en-us/download/details.aspx?id=8109
After clicking on "download" you should de-select any additional downloads "Microsoft Recommends" so that only "DirectX End-User Runtimes (June 2010)" is left on the left "Download Summary".
Then click on " No thanks and continue DirectX End-User Runtime Web Installer" button. That should let you download "directx_Jun2010_redist.exe".
This direct link might work, but I can not guarantee that. The procedure before however is unchanged for at least 3 years!

Download directx_Jun2010_redist.exe (ca. 95,6 MB) and run it. This will extract the content of the package in any empty directory you want.
Then find a Setup.exe there and run it.
You can delete the contents of the directory after the setup is completed. The directory is just a temporary storage for the installation files.

@Kuddel - I did as you suggested and installed the DirecX Runtimes.

Unfortunately, I'm still facing the same problem - When I run orbiter_ng.exe, all I get is a spinning cursor.

When I used the task manager to shut the Orbiter process down, it said that orbiter.exe was not responding.

This is frustrating, but I appreciate all of the help!

-Tc

 

[kuddel]

Hmmm that's a pitty.
As the Orbiter_ng.exe process does not like to start at all, I would investigate in whether you have all the C++ runtimes installed.
I am currently not at my home machine, so I am not sure whether you needed the 2008 runtime or another version.
There should be some kind of check program (in Install folder) wich might give you a hint.
The orbiter documentation (pdf) might have information on that topic, too.

 

[Tchail]

Hmmm that's a pitty.
As the Orbiter_ng.exe process does not like to start at all, I would investigate in whether you have all the C++ runtimes installed.
I am currently not at my home machine, so I am not sure whether you needed the 2008 runtime or another version.
There should be some kind of check program (in Install folder) wich might give you a hint.
The orbiter documentation (pdf) might have information on that topic, too.

I went into the Orbiter_2016/Install folder and ran vcredist_x86.exe.

After first trying to repair the Microsoft Visual C++ 2008 Redistributals, I then tried uninstalling, then reinstalling them.

Unfortunately, I'm still in the same place - A spinning cursor when I try to launch orbiter_ng.exe.

This shouldn't be so hard.

Sigh...

-Tc

 

[GLS]

Is the Orbiter folder read-only?
If you go to Properties of the Orbiter_ng.exe file, is it locked? (bottom of window)
Are you running Orbiter as an Administrator, or a limited account?

 

[Abloheet]

**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 4.27653e-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 (Intel(R) HD Graphics 4600) (HW)
000000.000: [x] Direct3D T&L HAL (Intel(R) HD Graphics 4600) (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 1920 x 1080 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
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: Module ShuttlePB.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

I notice from your Orbiter log, that only the integrated Intel HD Graphics HD 4600 is being detected by Orbiter as a graphics adapter. Where is your dedicated gpu? "Enumerate all devices"check box has to be checked for Orbiter to detect all available gpus in your system. You had forcefully selected Orbiter to run on the nvidia gpu, by right clicking on the Orbiter executable file, but Orbiter detects only your integrated gpu. First make Orbiter detect your dedicated gpu.

---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------

I have a NVidia GeForce GTX 870M graphics card with 3Gb of RAM. The drivers have been updated, and I have setting Orbiter to run on that card over the onboard graphics.

-Tc

You tried this, but Orbiter didn't detect your dedicated gpu. That's why you are getting the white screen

 

[Tchail]

Sorry for the delay in getting back to everyone on this.

I bought a new computer, and had Orbiter running fine - for a few days.

But now I seem to have run into the same problem, except this time I have more information.

Orbiter2016 doesn't seem to be seeing my Nvidia GeForce GTX 1070 graphics card. For some reason "3D Device" is stuck on "RGB Emulation," even though I have the "Always enumerate devices" box checked.

Any suggestions?

 

[Marijn]

I bought a new computer, and had Orbiter running fine - for a few days.

Was Orbiter running fine with the D3D9 client out of the box? Or did you have to visit a Microsoft site to download and install any DirectX related components to get Orbiter to run fine? If yes, which one did you download?

If Orbiter was running fine and now it doesn't, then something did change on your system. If you installed it from scratch, you can start over and check if Orbiter still runs fine after every change you make to your system. This way, you'll find the problem eventually.

 

[Tchail]

Yes, Orbiter did run fine out of the box.

I know something did change on my system, but at this point I'm at a loss as to what.

However, Orbiter isn't the only program that I'm having this problem with. Microsoft Flight Simulator X now refuses to recognize the graphics card.

The Sansar VR client also refused to work, and when I uninstalled the program then attempted to reinstall, the installer told me that my video card didn't meet the minimum requirements.

Yesterday I contacted NVidia Support. They've kicked it up to the next level of support. The Tech said that before I revert to reinstalling everything, they wanted to see what they could do on their end.

I can't be the only person to have run into this kind of problem, right?

And why would it happen on "both" of my computers?

Frustrating. But for now it looks like I just have to be patient.

 

[Marijn]

And why would it happen on "both" of my computers?

That's the big question. It could be some update which you did on both systems. Or some bad habit of yours which you aren't aware of. If NVidia kicks it up it isn't so simple.

---------- Post added at 10:31 PM ---------- Previous post was at 10:19 PM ----------

Did you have a look in the Event Viewer of Windows for application errors? Maybe some more info can be found there.

I assume you are testing with the default scenario's. Because errors in scenario's can cause Orbiter to crash as well.

Any chance both your pc's are HP branded?