Problem VIDEO TAB Orbiter 2010 "MISSING"

[Geraldokerenz]

I get my problem in last one week, I have already play orbiter 2010 since 2014 then this is my first problem that probably makes me CONFUSED.

-----------------------

First of all I just install a new directory from Orbiter 2010, i extract from .ZIP file then i run for the first time, and there are check before we can start. Then i copy my D3D9 for Orbiter 2010, then i open my launchpad, go to module then i checklist my D3D9Client, the video tab appears. After i close, then i re-open again, basicly my VIDEO TAB is missing with D3D9Client still checklist.

https://drive.google.com/open?id=0By9qKzYRcMY1RTJ1dkJWUmM5M2s

Then i just ignore that video tab i just pick one scenario and launch it, the result will be like this:

https://drive.google.com/open?id=0By9qKzYRcMY1dTFyS1lfZHdWTkU

----------------------------------------

That makes me confused is i have my old directory of Orbiter 2010 in the same computer, but the old directory doesn't have problem like that (video tab missing), and the old directory is fine fine to play. (Basicly i want to start again because in the old directory many crash that happens whenever i start launchpad (cause old files with many new updates)).

----------------------------------------

Still i have read many tutorial from this Forum, but for all tips that post in General Question, my problem still happens.

----------------------------------------

I use
Orbiter 2010 Version 100830 (http://orbitersimulator.com/orbiter-2010-downloads/)

D3D9 Client R12 (https://d3d9client.codeplex.com/releases/view/109361)

DirectX Jun 2010 (Redist https://www.microsoft.com/en-us/download/details.aspx?id=8109)

----------------------------------------

ORBITER LOG:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 5.40194e-007 sec
Found 0 joystick(s)
Error loading module Modules\Startup\AtlantisConfig.dll (code 193)
Error loading module Modules\Startup\AtmConfig.dll (code 193)
Error loading module Modules\Startup\DGConfigurator.dll (code 193)
Error loading module Modules\Plugin\Meshdebug.dll (code 193)
Error loading module Modules\Plugin\TrackIR.dll (code 193)
Error loading module Modules\Plugin\LuaMFD.dll (code 193)
Error loading module Modules\Plugin\CustomMFD.dll (code 193)
Error loading module Modules\Plugin\transx.dll (code 193)
Error loading module Modules\Plugin\LuaConsole.dll (code 193)
Error loading module Modules\Plugin\ScriptMFD.dll (code 193)
Error loading module Modules\Plugin\ExtMFD.dll (code 193)
Error loading module Modules\Plugin\Framerate.dll (code 193)
Error loading module Modules\Plugin\Rcontrol.dll (code 193)
Error loading module Modules\Plugin\FlightData.dll (code 193)
Error loading module Modules\Plugin\ScnEditor.dll (code 193)
Error loading module Modules\Plugin\OrbiterSound.dll (code 193)
Error loading module Modules\Plugin\D3D9Client.dll (code 193)

**** Creating simulation session
Finished initialising world
---------------------------------------------------------------
>>> ERROR: Could not load vessel module: DeltaGlider
>>> [Vessel::LoadModule | .\Vessel.cpp | 5442]
---------------------------------------------------------------
Finished initialising status
Finished initialising camera
Finished setting up render state

----------------------------------------

My DXDIAG

Machine name: GERALDO
Operating System: Windows 8.1 Pro 64-bit (6.3, Build 9600) (9600.winblue_gdr.140330-1035)
Language: English (Regional Setting: English)
System Manufacturer: LENOVO
System Model: 80KY
BIOS: InsydeH2O Version 05.04.20B0CN80WW
Processor: Intel(R) Core(TM) i3-4030U CPU @ 1.90GHz (4 CPUs), ~1.9GHz
Memory: 4096MB RAM
Available OS Memory: 4022MB RAM
Page File: 2316MB used, 4393MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11

----------------------------------------

So my question is What Happens? Is there are missing files or what?

----------------------------------------

Please
Somebody to help me, i just very confused and i want to play ORBITER again.

Thanks to all of response. I will appreciate to fix my problem.

----------------------------------------

Regards,
GERALDO NATHANAEL
[email protected]

 

[Face]

First of all I just install a new directory from Orbiter 2010, i extract from .ZIP file then i run for the first time, and there are check before we can start. Then i copy my D3D9 for Orbiter 2010, then i open my launchpad, go to module then i checklist my D3D9Client, the video tab appears. After i close, then i re-open again, basicly my VIDEO TAB is missing with D3D9Client still checklist.

Question: what does "Then i copy my D3D9 for Orbiter 2010" mean? Do you extract the release package into the fresh install? Or did you just copy the module from your old install over to the new directory?

Suggestion: copy the orbiter_ng.cfg and the D3D9Client.cfg from the old - functioning - installation to the new one.

 

[Geraldokerenz]

Question: what does "Then i copy my D3D9 for Orbiter 2010" mean? Do you extract the release package into the fresh install? Or did you just copy the module from your old install over to the new directory?

Suggestion: copy the orbiter_ng.cfg and the D3D9Client.cfg from the old - functioning - installation to the new one.

I mean that from Folder D3D9 (That i downloaded from source) i copy to the Orbiter Directory.


I have already do that, but still with the same problem. The Video Tab still not appears.

 

[martins]

If the video tab doesn't show despite the client being selected in the Modules list, this means that Orbiter couldn't load the D3D9client.dll. This usually indicates a missing dependency (i.e. another dll that the client depends on). The most common problem is missing c++ runtime libraries, but if you do have a working installation on the same system then that's less likely here (unless you have the runtimes installed locally in the Orbiter directory).

I don't know which local dependencies the D3D9 client has, but are you sure you installed all of the required shared libraries? It sounds like you copied files manually from one installation to the other, so it's easy to miss a library.

You could try with dependency checker (depends.exe) to track down missing dependencies.

 

[Face]

Error loading module Modules\Plugin\D3D9Client.dll (code 193)

Windows error 193 seems to be this: ERROR_BAD_EXE_FORMAT .

Sounds like there is some serious 64/32-bit mismatch.

 

[turtle91]

Hmmm, all standard Orbiter modules are failing to load with code 193.
Have you tried to run the C++ Runtime Libs installer in ".../orbiter/install" ?

The fact, that you might have another copy on the same box without problems might be, that there arethe required 32-bit-C++ libs INSIDE orbiter-dir (manual copied ?).

As far as I know, the OS looks for system-wide dlls, if missing...it looks into the actual directory, where the application is installed (apps working directory).

All 193 erros I found are pointing to a 32 vs 64 bit problem.
Just one example:

https://www.orbiter-forum.com/showthread.php?t=37996

 

[Ripley]

Why R12?

Get R16.5 here:
https://www.orbiter-forum.com/showthread.php?p=530736&postcount=3691

 

[Geraldokerenz]

Hmmm, all standard Orbiter modules are failing to load with code 193.
Have you tried to run the C++ Runtime Libs installer in ".../orbiter/install" ?

The fact, that you might have another copy on the same box without problems might be, that there arethe required 32-bit-C++ libs INSIDE orbiter-dir (manual copied ?).

As far as I know, the OS looks for system-wide dlls, if missing...it looks into the actual directory, where the application is installed (apps working directory).

All 193 erros I found are pointing to a 32 vs 64 bit problem.
Just one example:

https://www.orbiter-forum.com/showthread.php?t=37996

How about this one?

---------------------

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: D:\Orbiter Folder\Orbiter File\orbiter100830_Fix
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) i3-4030U CPU @ 1.90GHz (4 CPUs), ~1.9GHz
Memory: 4096MB RAM
DirectX Version: DirectX 11
Card name: Intel(R) HD Graphics Family
Card name: Intel(R) HD Graphics Family
Card name: AMD Radeon R5 M330
For full DirectX diagnostics, see file dxdiag.log.
-----------------------------------------------------
Orbiter installation verification complete.
No problems found.

---------------------

---------- Post added at 11:28 PM ---------- Previous post was at 11:17 PM ----------

Why R12?

Get R16.5 here:
https://www.orbiter-forum.com/showthread.php?p=530736&postcount=3691

I have already try, still doesn't work.

I very confused, any ideas for my problem? :facepalm:

---------- Post added at 11:29 PM ---------- Previous post was at 11:28 PM ----------

Windows error 193 seems to be this: ERROR_BAD_EXE_FORMAT .

Sounds like there is some serious 64/32-bit mismatch.

Which one miss from my Computer?

---------- Post added at 11:42 PM ---------- Previous post was at 11:29 PM ----------

I already check that for solution to install VS2015 Redist and C++ Runtime Libraries for latest version, it's WORK for Orbiter 2016. But my Orbiter 2010 still have a same problems.

 

[kuddel]

I already check that for solution to install VS2015 Redist and C++ Runtime Libraries for latest version, it's WORK for Orbiter 2016. But my Orbiter 2010 still have a same problems.

The VS2015-Runtime-Libraries are for Orbiter 2016.

Orbiter 2010 likes to have the VS2005-Runtime-Libraries.
Would you please run the "Install\vcredist_x86.exe", located in your Orbiter 2010 install folder?

 

[Geraldokerenz]

The VS2015-Runtime-Libraries are for Orbiter 2016.

Orbiter 2010 likes to have the VS2005-Runtime-Libraries.
Would you please run the "Install\vcredist_x86.exe", located in your Orbiter 2010 install folder?

i have already did, still with the same problem. "Video Tab Missing".


Is anyone can upload the Orbiter 100830 files with D3D9Client already installed? and absolutely sure to run. I will downloaded from you guys.


Thanks.

 

[kuddel]

O.K. Now let's try from root up

1. Could you please check that the Folder structure was left intact when you extracted any of the ZIPs?
   The D3d9Client.dll for example should be in the "Modules/Plugin" sub-folder...
2. Where did you install your Orbiter 2010 instance?
   I never had Windows 8.x, so there might be a UAC issue bugging us.
   If you installed it under "C:\Program Files" or "C:\Program Files (x86)", please move it to somewhere else (a folder on the Desktop is usually fine)

P.S.: Giving you a "complete ZIP" might not help here, 'cause the settings (Orbiter_ng.cfg rsp. D3D9Client.cfg might not fit your hardware)

 

[Marijn]

When I was installing Orbiter 2016 I ran into the same problem. The video tab was only visible on the first launch of Orbiter. Afterwards, the video tab was gone.

After installing version 9.29.1974 of DirectX on my Win8.1 machine, the problem was solved.

https://www.microsoft.com/en-us/download/details.aspx?id=35

I am not sure whether this is helpful to you since I was installing Orbiter 2016, but you could give it a try.

 

[kuddel]

Hello Marijn,

After installing version 9.29.1974 of DirectX on my Win8.1 machine, the problem was solved.

https://www.microsoft.com/en-us/download/details.aspx?id=35

Yes of course! Now I see that Geraldokerenz' diagnostic utility log only states DirectX 11...:facepalm:
Having DirectX 11 does not include DirectX 9!

So Geraldokerenz: Install DirectX 9 (see Martijns link) and you should be fine
WATCH OUT FOR THE BING BAR OPTION:thumbsdown:

(...having both DirectX 11 and DirectX 9 does not hurt)

/Kuddel

 

[Marijn]

Hi kuddel. Hopefully it will work for Geraldokerenz. I do confirm that DirectX 11 and DirectX 9 live happily alongside. No worries about that. Next next finish, and it should be done.