Hardware Problems with large screen resolution

[StevoPistolero]

I am getting the following error when I use large screen resolutions:

"Initializing 3d environment using a hardware device failed. Try again with a software device."

I am running orbiter 2016 with the D3D9 graphics.

 

[dbeachy1]

We will need more information so we can figure this out -- I am running Orbiter using D3D9 at 4K resolution with no problems. How are you launching Orbiter? Are you running orbiter_ng.exe and enabling the D3D9 client in the Modules section? What resolution are you using? Is this full-screen or windowed mode? Does it work in windowed mode? Can you please post your orbiter.log file?

 

[Donamy]

We will need more information so we can figure this out -- I am running Orbiter using D3D9 at 4K resolution with no problems.

SHUT UP !!!!

JK :tiphat:

 

[Ripley]

...I am running Orbiter using D3D9 at 4K resolution with no problems...

Screenshots, or it never happened!

:lol:

JK, too

 

[StevoPistolero]

Damnit, Bitdefender ate orbiter_ng.exe! What is the difference between orbiter_ng and orbiter.exe? I ran orbiter_ng and got it to work.

 

[DaveS]

Damnit, Bitdefender ate orbiter_ng.exe! What is the difference between orbiter_ng and orbiter.exe? I ran orbiter_ng and got it to work.

Orbiter_ng (No Graphics) doesn't have a built in graphics client like orbiter.exe does. This means it can essentially run as a stand-alone server rather than a client. You never want two graphics clients active at the same time as Orbiter will get confused on which one to actually use.

 

[Ripley]

Orbiter.exe is the plain vanilla Orbiter with inline graphics (DirectX7).

Orbiter_ng.exe is the server version you launch when you want to use an (any) external graphics client (must be enabled in the Modules tab). Nowadays the D3D9 client is the only valid alternative.
Launching Orbiter_ng.exe invokes YOUR_ORBITER_ROOT\Modules\Server\orbiter.exe.

DaveS beat me!

 

[gulfcoastfella]

I can run orbiter_ng.exe just once before Bitdefender kills it. I tried (1) uninstalling Orbiter2016, then (2) reinstalling Orbiter2016 to get the orbiter_ng.exe file back, then (3) going into BitDefender>Modules>AntiVirus>Settings Icon>Exclusions Tab> and adding the entire Orbiter root folder to the "Excluded files and folders" list. I then restart my computer just in case BitDefender has to "get itself straight", and then, upon running orbiter_ng.exe, it runs the one time, after which BitDefender detects the file INSIDE THE WHITELISTED FOLDER and removes it as a threat.
StevoPistolero, did you figure out how to stop BitDefender from doing this?