New Release D3D9Client Development - Page 4 - Orbiter-Forum

**jarmonik** · 10-15-2010, 11:04 PM

Quote:

Originally Posted by Xyon

Same visual issue, but for this:
Attachment 5993

Did you make sure that software vertex processing is disabled from video tab. I'll remove it from the next version.

I also noticed that the static build won't shutdown orbiter properly so you may need to use Task Manager. If existing orbiter process is active on a background you can't launch an other Orbiter process. It will give you a debug assertion failure.

**Xyon** · 10-15-2010, 11:13 PM

Quote:

Originally Posted by jarmonik

Did you make sure that software vertex processing is disabled from video tab. I'll remove it from the next version.

I also noticed that the static build won't shutdown orbiter properly so you may need to use Task Manager. If existing orbiter process is active on a background you can't launch an other Orbiter process. It will give you a debug assertion failure.

Turning that off prevented the CTD, however the splash screen did not progress to simulation. Eventually intervening caused the usual error message from Windows for a nonresponsive program. Orbiter.log shows:

Code:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.39777e-007 sec
Found 0 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module D3D9Client.dll ........ [Build 101016, API 100830]

**** Creating simulation session
D3D9Client: Viewport: Window 794 x 572 x 32
D3D9Client: Z-buffer depth: 24 bit
D3D9Client: Stencil buffer depth: 8 bit
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]

**jarmonik** · 10-15-2010, 11:24 PM

Looks like you need to remove Miranda from the Sol.cfg as well. I am sorry that the client doesn't work any better at a moment.

**Xyon** · 10-15-2010, 11:41 PM

Taking Miranda out accomplishes seemingly very little. Once I had it crash getting to the XR2's DLL, testing with a stock DG scenario gave this:

Code:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.39777e-007 sec
Found 0 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module D3D9Client.dll ........ [Build 101016, API 100830]

**** Creating simulation session
D3D9Client: Viewport: Window 794 x 572 x 32
D3D9Client: Z-buffer depth: 24 bit
D3D9Client: Stencil buffer depth: 8 bit
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Deimos.dll ............ [Build ******, API 060425]

---------- Post added at 00:41 ---------- Previous post was at 00:39 ----------

Testing again with the same scn (2010/Visual Improvements/KSC Update) gave this:

Code:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.39777e-007 sec
Found 0 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module D3D9Client.dll ........ [Build 101016, API 100830]

**** Creating simulation session
D3D9Client: Viewport: Window 794 x 572 x 32
D3D9Client: Z-buffer depth: 24 bit
D3D9Client: Stencil buffer depth: 8 bit
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Ariel.dll ............. [Build ******, API 060425]

The 2010 "Welcome" scenario gets slightly further:

Code:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.39777e-007 sec
Found 0 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module D3D9Client.dll ........ [Build 101016, API 100830]

**** Creating simulation session
D3D9Client: Viewport: Window 794 x 572 x 32
D3D9Client: Z-buffer depth: 24 bit
D3D9Client: Stencil buffer depth: 8 bit
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]

"In orbit over Africa", however, does not, and the same for "Space Shuttle Atlantis\Launch into Sunrise.scn":

Code:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.39777e-007 sec
Found 0 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module D3D9Client.dll ........ [Build 101016, API 100830]

**** Creating simulation session
D3D9Client: Viewport: Window 794 x 572 x 32
D3D9Client: Z-buffer depth: 24 bit
D3D9Client: Stencil buffer depth: 8 bit
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Ariel.dll ............. [Build ******, API 060425]

Interestingly, "Views\Martian Atmosphere Colours" got as far as a vessel's .dll before actually crashing rather than just getting stuck:

Code:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.39777e-007 sec
Found 0 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module D3D9Client.dll ........ [Build 101016, API 100830]

**** Creating simulation session
D3D9Client: Viewport: Window 794 x 572 x 32
D3D9Client: Z-buffer depth: 24 bit
D3D9Client: Stencil buffer depth: 8 bit
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100830, API 100830]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
Module ShuttlePB.dll ......... [Build 100911, API 100830]

**jarmonik** · 10-16-2010, 12:08 AM

Looks like different scenarios are crashing in a different DLL. Solving that problem is going to take some time. Right now I'll need go to sleep and I'll continue tomorrow.

**orb** · 10-16-2010, 01:58 AM

I've created a very simple star system from Sol with only Sol, Mercury, Venus and Mars (no Earth, nor any of Mars' moons), and a simple scenario with a single vessel landed on Mercury (exchangeable ShuttlePB or DG-S), and it loads without errors (with all visual effects disabled) with the precompiled client module (the one compiled with /MDd - the 1st in series). I guess there might be no 3D rendering implemented yet, because I get only 2D panel displayed while in 2D cockpit (for DG-S) or only engine status (top-left) in glass cockpit, + information text (top-right), and only this text in external view (no stars, planets, vessels).

But when I compile sources and then I try to run that module from withing VS in debug mode with Orbiter server - using these parameters:

Code:

Command="$(OrbiterDir)\Modules\Server\orbiter.exe"
WorkingDirectory="$(OrbiterDir)"

I get errors displayed in message boxes, while simulation is starting:

Only once, at the beginning:
After I close the first error message, repeatedly in presented order:

(Could it be connected to too old version of DirecX 9 SDK (March 2009) I have?

)
The GPU is NVidia G80. There were no such errors when I compiled the first version of sources (the code displaying only loading screen).

The only crashes I have had with either precompiled module or mine, and with that custom system/scenario, was with closing simulation session (either return to Launch Pad or Respawn).

**jarmonik** · 10-16-2010, 07:40 AM

Quote:

Originally Posted by orb

I guess there might be no 3D rendering implemented yet, because I get only 2D panel displayed while in 2D cockpit (for DG-S) or only engine status (top-left) in glass cockpit, + information text (top-right), and only this text in external view (no stars, planets, vessels).

Yes, Only 2D Panel and glass cockpit is online.

Quote:

Originally Posted by orb

But when I compile sources and then I try to run that module from withing VS in debug mode with Orbiter server - using these parameters:
(Could it be connected to too old version of DirecX 9 SDK (March 2009) I have?

)

I am not sure. I have February 2010 version. But anyway the problem is caused by the warning it gives you at first about the "pow". It is already protected against negative values by using "max" but the complier doesn't understand that for some reason. The warning will cause the Client to quit loading. The easiest way to get around it is to chnage the line "float s = pow(max(dot(r, toCamW), 0.0f), gLM.specPower);" into "float s = 0.0f;" from MeshTech.fx. It's not used right now but it will be when VC, exterior meshes and surface bases will go online.

**jarmonik** · 10-16-2010, 10:45 AM

Ok, Here is a new version for debugging. It doesn't have any new features but it should fix the FX script warning issue with "pow". The "Software vertex processing" is removed/disabled and a few CTD issues during shutdown are fixed. The package is containing two prebuild DLLs using static and dynamic linkking.

Installation note: Place the MeshTech.fx in the Orbiter's root folder.
Installation note: Remove Phobos and Saturn system from the Sol.cfg (And the other ones causing orbiter to stop responding. See the last line in the Orbiter.log)

**jarmonik** · 10-17-2010, 06:15 PM

Here is a new package.

-The MFD update efficiency is now on a same level as with the inline graphics engine.
-Star field, celestial grid and constellations are now online.

Installation note: Place the *.fx scripts in the Orbiter's root folder.
Installation note: Remove Phobos and Saturn system from the Sol.cfg (And the other ones causing orbiter to stop responding. See the last line in the Orbiter.log)

The surface handling is getting difficult. There is simply not enough information to create the surfaces properly. Automatic surface format conversion and reallocation seems to work somehow. But it is likely that a vessel specific configuration options will be needed.

A good example is the problem with clbkLoadTexture(). In a DirectX9 texture surfaces are a read only surfaces, texture can't be a target surface for a blitting operation and texture can't be used for GDI drawing. Of course, it's possible to create a texture with a dynamic option that allows GDI drawing but it's very slow. Based on what the Orbiter is about to do with a texture it may need to be converted into a plain surface or a rendering target texture. It may take some time until the surface allocation is on the optimal level. So far, I have only tested DeltaGlider and Shuttle-A.

**Xyon** · 10-17-2010, 07:53 PM

Crashed as soon as it got to the vessel module.

Code:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.39774e-007 sec
Found 1 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module D3D9ClientSL.dll ...... [Build 101017, API 100830]
Error loading module Modules\Plugin\D3D9Client.dll (code 126)

**** Creating simulation session
D3D9Client: Viewport: Window 794 x 572 x 32
D3D9Client: Z-buffer depth: 24 bit
D3D9Client: Stencil buffer depth: 8 bit
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Finished initialising world
Module ShuttlePB.dll ......... [Build 100911, API 100830]

I've taken a leaf out of Orb's book and trimmed a special DX9Sol.cfg for testing this, with just Mercury, Venus, Earth and the Moon in it, and a simplistic SCN to use this smaller system, with only a PB landed on Earth in it.

**jarmonik** · 10-17-2010, 08:45 PM

Have you tried "Delta-glider/DG Mk4 in Orbit" or "Shuttle-A/ISS Approach" scenarios ? Also "Delta-glider/Docked at ISS" is pretty stable but it will start in VC mode.

ShuttlePB.dll is loading fine on my computer. I received a word from Martin that he is taking a look in to the problem when he got time.

**Xyon** · 10-17-2010, 08:58 PM

DX9Sol.cfg:

Code:

; === Configuration file for solar system - edited for compatibility with Alpha D3D9 client ===
Name = DX9Sol

Star1 = Sun
Planet1 = Mercury
Planet2 = Venus
Planet3 = Earth
Earth:Moon1 = Moon

Using the scenarios stated with minimal DX9Sol.cfg:

DGMK4 in orbit: (Modified to use DX9Sol.cfg, DG on Mars removed as system has no Mars)

Code:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.39774e-007 sec
Found 1 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module D3D9ClientSL.dll ...... [Build 101017, API 100830]
Error loading module Modules\Plugin\D3D9Client.dll (code 126)

**** Creating simulation session
D3D9Client: Viewport: Window 794 x 572 x 32
D3D9Client: Z-buffer depth: 24 bit
D3D9Client: Stencil buffer depth: 8 bit
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Finished initialising world
Module DeltaGlider.dll ....... [Build 100830, API 100830]

CTD

Shuttle A ISS Approach: (Modified to use DX9Sol.cfg)

Code:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.39774e-007 sec
Found 1 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module D3D9ClientSL.dll ...... [Build 101017, API 100830]
Error loading module Modules\Plugin\D3D9Client.dll (code 126)

**** Creating simulation session
D3D9Client: Viewport: Window 794 x 572 x 32
D3D9Client: Z-buffer depth: 24 bit
D3D9Client: Stencil buffer depth: 8 bit
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Finished initialising world
Module ShuttleA.dll .......... [Build 100830, API 100830]

CTD

Delta Glider Docked to ISS (Modified to use DX9Sol.cfg)

Code:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.39774e-007 sec
Found 1 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module D3D9ClientSL.dll ...... [Build 101017, API 100830]
Error loading module Modules\Plugin\D3D9Client.dll (code 126)

**** Creating simulation session
D3D9Client: Viewport: Window 794 x 572 x 32
D3D9Client: Z-buffer depth: 24 bit
D3D9Client: Stencil buffer depth: 8 bit
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Finished initialising world
Module DeltaGlider.dll ....... [Build 100830, API 100830]

CTD

I have not yet been able to get the client to render a single frame of simulation.

---------- Post added at 21:58 ---------- Previous post was at 21:54 ----------

lol. The line "Error loading module Modules\Plugin\D3D9Client.dll (code 126)" is innocuous, I have the dynamically linked one in there too, but the static linked one is working.

**jarmonik** · 10-17-2010, 09:06 PM

Can you zip and attach the D3D9ClientLog.html into your post. That would show what the client was doing before the CTD. I'll include more debug information into the next release.

---------- Post added at 00:06 ---------- Previous post was at 00:03 ----------

Quote:

lol. The line "Error loading module Modules\Plugin\D3D9Client.dll (code 126)" is innocuous, I have the dynamically linked one in there too, but the static linked one is working.

It's probably good idea to install only one of them at a time.

**Xyon** · 10-17-2010, 09:17 PM

Quote:

Originally Posted by jarmonik

Can you zip and attach the D3D9ClientLog.html into your post. That would show what the client was doing before the CTD. I'll include more debug information into the next release.

D3D9ClientLog.zip

Quote:

Originally Posted by jarmonik

It's probably good idea to install only one of them at a time.

Having checked, only the SL is present in the folder. Not sure where the other one is.

**orb** · 10-17-2010, 09:20 PM

And this error probably says that my laptop's graphics card isn't compatible with D3D9Client (?):

If that's the case, then I won't be able to run it (even if I compile if from the sources) until I get my desktop PC repaired.

10-16-2010, 01:58 AM	#51
orb O-F Administrator	I've created a very simple star system from Sol with only Sol, Mercury, Venus and Mars (no Earth, nor any of Mars' moons), and a simple scenario with a single vessel landed on Mercury (exchangeable ShuttlePB or DG-S), and it loads without errors (with all visual effects disabled) with the precompiled client module (the one compiled with /MDd - the 1st in series). I guess there might be no 3D rendering implemented yet, because I get only 2D panel displayed while in 2D cockpit (for DG-S) or only engine status (top-left) in glass cockpit, + information text (top-right), and only this text in external view (no stars, planets, vessels). But when I compile sources and then I try to run that module from withing VS in debug mode with Orbiter server - using these parameters: Code: Command="$(OrbiterDir)\Modules\Server\orbiter.exe" WorkingDirectory="$(OrbiterDir)" I get errors displayed in message boxes, while simulation is starting: Only once, at the beginning: After I close the first error message, repeatedly in presented order: (Could it be connected to too old version of DirecX 9 SDK (March 2009) I have? ) The GPU is NVidia G80. There were no such errors when I compiled the first version of sources (the code displaying only loading screen). The only crashes I have had with either precompiled module or mine, and with that custom system/scenario, was with closing simulation session (either return to Launch Pad or Respawn). Attached Thumbnails Last edited by orb; 10-16-2010 at 02:01 AM.

10-16-2010, 10:45 AM	#53
jarmonik Beta Tester	Ok, Here is a new version for debugging. It doesn't have any new features but it should fix the FX script warning issue with "pow". The "Software vertex processing" is removed/disabled and a few CTD issues during shutdown are fixed. The package is containing two prebuild DLLs using static and dynamic linkking. Installation note: Place the MeshTech.fx in the Orbiter's root folder. Installation note: Remove Phobos and Saturn system from the Sol.cfg (And the other ones causing orbiter to stop responding. See the last line in the Orbiter.log) Last edited by jarmonik; 10-30-2010 at 07:43 PM.

10-17-2010, 06:15 PM	#54
jarmonik Beta Tester	Here is a new package. -The MFD update efficiency is now on a same level as with the inline graphics engine. -Star field, celestial grid and constellations are now online. Installation note: Place the .fx scripts in the Orbiter's root folder. Installation note:* Remove Phobos and Saturn system from the Sol.cfg (And the other ones causing orbiter to stop responding. See the last line in the Orbiter.log) The surface handling is getting difficult. There is simply not enough information to create the surfaces properly. Automatic surface format conversion and reallocation seems to work somehow. But it is likely that a vessel specific configuration options will be needed. A good example is the problem with clbkLoadTexture(). In a DirectX9 texture surfaces are a read only surfaces, texture can't be a target surface for a blitting operation and texture can't be used for GDI drawing. Of course, it's possible to create a texture with a dynamic option that allows GDI drawing but it's very slow. Based on what the Orbiter is about to do with a texture it may need to be converted into a plain surface or a rendering target texture. It may take some time until the surface allocation is on the optimal level. So far, I have only tested DeltaGlider and Shuttle-A. Last edited by jarmonik; 10-30-2010 at 07:43 PM.

10-17-2010, 09:20 PM	#60
orb O-F Administrator	And this error probably says that my laptop's graphics card isn't compatible with D3D9Client (?): If that's the case, then I won't be able to run it (even if I compile if from the sources) until I get my desktop PC repaired. Attached Thumbnails

Quick Links	Need Help?
About Us Register to Participate Orbiter Website Orbiter Download Projects Recommended Addons Orbit Hangar Mods Photo Gallery Social Groups External Links	Did you forget your password? Rules & Guidelines Frequently Asked Questions Orbiter F.A.Q. Orbiter Tutorials Orbiter IRC Chat Search Forum Site Map Contact Us Mark Forums Read

10-15-2010, 11:04 PM	#46
jarmonik Beta Tester	Quote: Originally Posted by Xyon Same visual issue, but for this: Attachment 5993 Did you make sure that software vertex processing is disabled from video tab. I'll remove it from the next version. I also noticed that the static build won't shutdown orbiter properly so you may need to use Task Manager. If existing orbiter process is active on a background you can't launch an other Orbiter process. It will give you a debug assertion failure.

10-15-2010, 11:24 PM	#48
jarmonik Beta Tester	Looks like you need to remove Miranda from the Sol.cfg as well. I am sorry that the client doesn't work any better at a moment.

10-16-2010, 12:08 AM	#50
jarmonik Beta Tester	Looks like different scenarios are crashing in a different DLL. Solving that problem is going to take some time. Right now I'll need go to sleep and I'll continue tomorrow.

10-16-2010, 07:40 AM	#52
jarmonik Beta Tester	Quote: Originally Posted by orb I guess there might be no 3D rendering implemented yet, because I get only 2D panel displayed while in 2D cockpit (for DG-S) or only engine status (top-left) in glass cockpit, + information text (top-right), and only this text in external view (no stars, planets, vessels). Yes, Only 2D Panel and glass cockpit is online. Quote: Originally Posted by orb But when I compile sources and then I try to run that module from withing VS in debug mode with Orbiter server - using these parameters: (Could it be connected to too old version of DirecX 9 SDK (March 2009) I have? ) I am not sure. I have February 2010 version. But anyway the problem is caused by the warning it gives you at first about the "pow". It is already protected against negative values by using "max" but the complier doesn't understand that for some reason. The warning will cause the Client to quit loading. The easiest way to get around it is to chnage the line "float s = pow(max(dot(r, toCamW), 0.0f), gLM.specPower);" into "float s = 0.0f;" from MeshTech.fx. It's not used right now but it will be when VC, exterior meshes and surface bases will go online.

10-17-2010, 08:45 PM	#56
jarmonik Beta Tester	Have you tried "Delta-glider/DG Mk4 in Orbit" or "Shuttle-A/ISS Approach" scenarios ? Also "Delta-glider/Docked at ISS" is pretty stable but it will start in VC mode. ShuttlePB.dll is loading fine on my computer. I received a word from Martin that he is taking a look in to the problem when he got time.

10-17-2010, 09:06 PM	#58
jarmonik Beta Tester	Can you zip and attach the D3D9ClientLog.html into your post. That would show what the client was doing before the CTD. I'll include more debug information into the next release. ---------- Post added at 00:06 ---------- Previous post was at 00:03 ---------- Quote: lol. The line "Error loading module Modules\Plugin\D3D9Client.dll (code 126)" is innocuous, I have the dynamically linked one in there too, but the static linked one is working. It's probably good idea to install only one of them at a time.

10-17-2010, 09:17 PM	#59
Xyon Puts the Fun in Dysfunctional	Quote: Originally Posted by jarmonik Can you zip and attach the D3D9ClientLog.html into your post. That would show what the client was doing before the CTD. I'll include more debug information into the next release. D3D9ClientLog.zip Quote: Originally Posted by jarmonik It's probably good idea to install only one of them at a time. Having checked, only the SL is present in the folder. Not sure where the other one is.