New Release D3D9Client Development

jgrillo2002 · Sep 19, 2016

I have been reading in this topic somewhere that there is a lens flare effect. can you point to me in the right direction?

turtle91 · Sep 19, 2016

I have been reading in this topic somewhere that there is a lens flare effect. can you point to me in the right direction?

It's a different independent build:
http://www.orbiter-forum.com/showthread.php?p=539790&postcount=4076

Antoo · Sep 19, 2016

Hi all,

Just tried Orbiter 2016 + new D3D9 client, and every time I launch the sim, after 5-6 minutes it does a CTD :facepalm: .

Here is the log :

Code:

**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 3.01175e-007 sec
000000.000: Found 1 joystick(s)
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: Module Meshdebug.dll ......... [Build 160828, API 160828]
000000.000: Module D3D9Client.dll ........ [Build 160830, API 160828]
000000.000: Module TrackIR.dll ........... [Build 160828, API 160828]
000000.000: TrackIR module found: C:\Program Files (x86)\NaturalPoint\TrackIR5\
000000.000: TrackIR initialised
000000.000: NaturalPoint software version 5.00
000000.000: Module CustomMFD.dll ......... [Build 160828, API 160828]
000000.000: Module LuaMFD.dll ............ [Build 160828, API 160828]
000000.000: Module transx.dll ............ [Build 160216, API 160214]
000000.000: Module LuaConsole.dll ........ [Build 160828, API 160828]
000000.000: Module ScriptMFD.dll ......... [Build 160828, API 160828]
000000.000: Module DX9ExtMFD.dll ......... [Build 150812, API 100830]
000000.000: Module ExtMFD.dll ............ [Build 160828, API 160828]
000000.000: Module FlightData.dll ........ [Build 160828, API 160828]
000000.000: Module Framerate.dll ......... [Build 160828, API 160828]
000000.000: Module Rcontrol.dll .......... [Build 160828, API 160828]
000000.000: Module ScnEditor.dll ......... [Build 160828, API 160828]
000000.000: 
000000.000: **** Creating simulation session
000000.000: D3D9: [DirectX 9 Initialized]
000000.000: D3D9: 3D-Adapter = NVIDIA GeForce GTX 970
000000.000: D3D9: MaxTextureWidth........: 16384
000000.000: D3D9: MaxTextureHeight.......: 16384
000000.000: D3D9: MaxTextureRepeat.......: 8192
000000.000: D3D9: VolTexAddressCaps......: 0x3F
000000.000: D3D9: NumSimultaneousRTs.....: 4
000000.000: D3D9: VertexDeclCaps.........: 0x30F
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...: Yes
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 = 4080 MB
000000.000: D3D9: [3DDevice Initialized]
000000.000: D3D9: [Loading Constellations]
000000.000: D3D9: [D3D9Client Initialized]
000000.000: Joystick throttle: Z-AXIS
000000.000: Joystick throttle control detected
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: D3D9: [Scene Initialized]
000000.000: NPClient: Simulation window registered.
000000.000: NPClient: Cursor stopped
000000.000: NPClient: Data transmission started
000000.000: Finished initialising panels
000066.093: D3D9: [Session Closed. Scene deleted.]
000066.093: D3D9: [Destroy Render Window Called]
000066.093: **** Closing simulation session
000066.093: D3D9: ERROR: Invalid Window !! RenderWndProc() called after calling clbkDestroyRenderWindow() uMsg=0x4A62A0
000066.093: 
000066.093: **** Creating simulation session
000066.093: D3D9: [DirectX 9 Initialized]
000066.093: D3D9: 3D-Adapter = NVIDIA GeForce GTX 970
000066.093: D3D9: MaxTextureWidth........: 16384
000066.093: D3D9: MaxTextureHeight.......: 16384
000066.093: D3D9: MaxTextureRepeat.......: 8192
000066.093: D3D9: VolTexAddressCaps......: 0x3F
000066.093: D3D9: NumSimultaneousRTs.....: 4
000066.093: D3D9: VertexDeclCaps.........: 0x30F
000066.093: D3D9: XNA Math Support.......: Yes
000066.093: D3D9: Vertex Texture.........: Yes
000066.093: D3D9: Shadow Mapping.........: Yes
000066.093: D3D9: D3DFMT_A16B16G16R16F...: Yes
000066.093: D3D9: D3DFMT_A32B32G32R32F...: Yes
000066.093: D3D9: D3DFMT_D32F_LOCKABLE...: Yes
000066.093: D3D9: D3DFMT_A2R10G10B10.....: Yes
000066.093: D3D9: D3DDTCAPS_DEC3N........: No
000066.093: D3D9: D3DDTCAPS_FLOAT16_2....: Yes
000066.093: D3D9: D3DDTCAPS_FLOAT16_4....: Yes
000066.093: D3D9: Available Texture Memory = 4080 MB
000066.093: D3D9: [3DDevice Initialized]
000066.093: D3D9: [Loading Constellations]
000066.093: D3D9: [D3D9Client Initialized]
000066.093: Joystick throttle: Z-AXIS
000066.093: Joystick throttle control detected
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 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: D3D9: [Scene Initialized]
000000.000: NPClient: Simulation window registered.
000000.000: NPClient: Cursor stopped
000000.000: NPClient: Data transmission started
000000.000: Finished initialising panels

Do you know what is wrong here?

Thanks.

jgrillo2002 · Sep 20, 2016

Antoo said:
Hi all,

Just tried Orbiter 2016 + new D3D9 client, and every time I launch the sim, after 5-6 minutes it does a CTD :facepalm: .

I have looked at your log and I have found this

Code:

000066.093: D3D9: ERROR: Invalid Window !! RenderWndProc() called after calling clbkDestroyRenderWindow() uMsg=0x4A62A0

I don't think this is normal for it to spit that error out. Is it possible that you are running it in windowed mode?

kuddel · Sep 20, 2016

jgrillo2002 said:
I have looked at your log and I have found this

Code:

000066.093: D3D9: ERROR: Invalid Window !! RenderWndProc() called after calling clbkDestroyRenderWindow() uMsg=0x4A62A0

I don't think this is normal for it to spit that error out. Is it possible that you are running it in windowed mode?

That error is not uncommon (in windowed mode) and should only be logged when closing an Orbiter session.
It is notifying that the Orbiter core is calling RenderWndProc although we (Jarmo & me [Kuddel]) think it should not be called after clbkDestroyRenderWindow has been called.
If this assumption is correct might be a topic to discuss with Martin.

In summary: This special log error is harmless and does not explain Antoos issue.

JMW · Sep 21, 2016

Having trouble getting D3D9ClientBeta25.1-forBETA r64(r795) to work with New Orbiter SVN commit (r.64, Sep 10 2016).
Both are in a clean install except for Orbitersound.

Its the old "no video tab" syndrome.

Kyle said:
Originally Posted by DaveS View Post
Did you install only the June DX Runtime files? You need the February runtimes as that's the DX9 SDK version that the sources were compiled against.

Kyle said:
EDIT: Problem fixed! The two weren't actually installed correctly.

Sorry for long delay here.
Have these runtimes gotta be installed somewhere specific or can it be anywhere on the HD?
I have other Orbiter folders that are working fine (with older revisions).......

DaveS · Sep 21, 2016

You only the February 2010 x86 runtimes. What you're downloading from Microsoft's site is the actual installer in a packaged format. This one can be extracted anywhere on your PC. The installer is named DXSETUP.exe.

JMW · Sep 21, 2016

Well, have extracted them to my root folder D:\ and still no video tab on Launchpad....:shrug:

What I have is "directx_feb2010_redist.exe" Correct or:thumbsdown:

DaveS · Sep 21, 2016

JMW said:
Well, have extracted them to my root folder D:\ and still no video tab on Launchpad....:shrug:

What I have is "directx_feb2010_redist.exe" Correct or:thumbsdown:

You need to run DXSETUP.exe in the folder that was created when you extracted the files. None of you have ever run a self-extracting archive before? Am I one of the few around here that was using PC's back in the 90's when these were common?

JMW · Sep 21, 2016

Well I haven't.
Am running it now.
It's saying it will take a few minutes..........

And now a restart...
Hope to be back soon....:leaving::leaving:

Hurrah !!
All's working fine now.
Thanks DaveS for your sage knowledge :tiphat:

cristiapi · Sep 23, 2016

This post is related to the thread:
http://www.orbiter-forum.com/showthread.php?t=37558

When I fly with Orbiter 2016 + D3D9Client2016-R1, after few minutes the "Virtual size" allocated by Orbiter 2016 (I use Sysinternals Process Explorer) goes beyond 4 GB and Orbiter crashes (no CTD, I see the error message).
Orbiter 2016 without D3D9Client2016-R1 doesn't crash.

My hardware: 16 GB SDRAM, GTX 660 Ti-DC2 (2 GB SDRAM).

jarmonik · Sep 23, 2016

cristiapi said:
This post is related to the thread:
http://www.orbiter-forum.com/showthread.php?t=37558

When I fly with Orbiter 2016 + D3D9Client2016-R1, after few minutes the "Virtual size" allocated by Orbiter 2016 (I use Sysinternals Process Explorer) goes beyond 4 GB and Orbiter crashes (no CTD, I see the error message).
Orbiter 2016 without D3D9Client2016-R1 doesn't crash.

My hardware: 16 GB SDRAM, GTX 660 Ti-DC2 (2 GB SDRAM).

I made a 45 minute test run and I didn't notice any kind of memory leaking. So, can you confirm that this happens in clean Orbiter 2016 + D3D9 R1 with Orbiter's stock vessels ?

Does the statistics panel Ctrl+Shift+C indicate where the memory goes ?

If an add-on is required to produce the memory leak then we would need to know which one so that we can investigate what goes wrong.

cristiapi · Sep 23, 2016

jarmonik said:
I made a 45 minute test run and I didn't notice any kind of memory leaking. So, can you confirm that this happens in clean Orbiter 2016 + D3D9 R1 with Orbiter's stock vessels ?

Yes. I disabled all the modules but D3D9 and I used the "The Alps in 3D" scenario (I changed some parameters in Video -> Advanced window).

jarmonik said:
Does the statistics panel Ctrl+Shift+C indicate where the memory goes ?

I see that the "Available video mem." value is continuously decreasing, while the "Tile Vertex Cache" value is continuously increasing. The others memory values are very small (few MB).
And now Orbiter just crashed showing the window titled "Microsoft Visual C++ Runtime Library", the error is:

Code:

Runtime Error!

Program: ...\orbiter.exe

This application has requested the Runtime to terminate it in an
unusual way.
Please contact...

The virtual size value is "4.068.708 K" and the GPU committed bytes value is "2.735.364 K".

---------- Post added at 23:48 ---------- Previous post was at 23:23 ----------

Now I changed "Video -> Advanced -> Font rendering" from cleartype to crisp and the virtual size is growing much slower than before. Now Orbiter crashed again, but it took much longer (about half an hour).

jarmonik · Sep 24, 2016

cristiapi said:
Now I changed "Video -> Advanced -> Font rendering" from cleartype to crisp and the virtual size is growing much slower than before. Now Orbiter crashed again, but it took much longer (about half an hour).

That should have no effect in memory consumption, something else worked differently in that test.

There is an option "Mesh Resolution" which has settings (16, 32, 64, 128). Do not keep it in 128 especially if reflections or custom cameras are enabled. (which require to render 360deg view around the vessel). Highest recommended setting is 64. I prefer 32 since the terrain quality doesn't increase munch beyond that but the performance costs and memory consts do increase.

Maybe we should disable 128 and probably 64 options based to reflection/
custom camera settings and an available video memory.

Does this information help the solve the problem ?

cristiapi · Sep 24, 2016

I have the reflections enabled (full scene) and custom cameras disabled.
If I use Mesh Resolution = 64 there is not much difference in memory allocation (and probably Orbiter will crash sooner or later), but if I use 32, the memory allocation is much lower and it increases very slowly.
[With 64 or 128 the GPU is fully loaded, while with 32 the GPU is 80% loaded.]

To be honest, I'm still using very old video card drivers (november 2014); now I'm downloading the latest release...

Thank you for the help.

---------- Post added at 12:05 ---------- Previous post was at 10:55 ----------

Now I have GeForce 372.90 drivers, but nothing changed (it seems that I got 5/6 extra FPS).

jarmonik · Sep 24, 2016

cristiapi said:
If I use Mesh Resolution = 64 there is not much difference in memory allocation (and probably Orbiter will crash sooner or later), but if I use 32, the memory allocation is much lower and it increases very slowly.

There is an upper limit on how high the "Tile Vertex Cache" allocation can climb. (Exact values are depending on multiple configuration settings). The climb in fast in the beginning but gets slower when nearing the limit.

Currently "Tile Vertex Cache" allocation is never reduced. But, Of course, unused surface tiles are removed from the cache and the space is reused for new tiles. So the cache size it pretty much the "peak" amount of terrain that has been seen at some point during the simulation.

Here are some approximate peak values for different "Mesh resolutions":

128 = 2-3 GB
64 = 512-800 MB
32 = 128-200 MB without high-res textures (32-64 MB)

cristiapi · Sep 25, 2016

jarmonik said:
Currently "Tile Vertex Cache" allocation is never reduced. But, Of course, unused surface tiles are removed from the cache and the space is reused for new tiles.

While in my PC it seems that the surface tiles are never removed.
I'll overwrite the D3D9 files to restore the default settings and I'll try again...

jarmonik said:
Here are some approximate peak values for different "Mesh resolutions":

128 = 2-3 GB
64 = 512-800 MB
32 = 128-200 MB without high-res textures (32-64 MB)

What I see in my PC is in good agreement with the upper values.

---------- Post added 25-09-16 at 14:16 ---------- Previous post was 24-09-16 at 22:27 ----------

cristiapi said:
I'll overwrite the D3D9 files to restore the default settings and I'll try again...

That did not fix the problem.

jacquesmomo · Sep 26, 2016

Hi everybody.
It's my first post in this D3D9 subject.

I noticed something strange with Orbiter 2016 and D3D9 about object's shadows :

1) Without D3D9 the shadows are ok, in the right localisation.

2) With D3D9 the shadows are ok, but with a curious localisation (shifted)

3) Without D3D9 and the Hires Pack textures for Earth, the shadows are not visible.

an idea ? :shrug:

GLS · Sep 26, 2016

jarmonik said:
It's currently not possible to disable them but I can define a new CATEGORY 3 setting for the next version of the client that will disable the main lights. Only PAPI(s) and VASI remains enabled. Is that Ok ?

This wasn't implemented yet, right?

jarmonik · Sep 26, 2016

jacquesmomo said:
I noticed something strange with Orbiter 2016 and D3D9 about object's shadows :

Thanks, I'll look into it. Base structure shadows are currently broken and I'll try to figure something to get them in a better shape.

---------- Post added at 18:14 ---------- Previous post was at 18:12 ----------

GLS said:
This wasn't implemented yet, right?

It was implemented a long ago and a quick test reveals that it still works:thumbup:

---------- Post added at 18:18 ---------- Previous post was at 18:14 ----------

cristiapi said:
That did not fix the problem.

I haven't found anything and I can't reproduce the problem. Anyone else able to get the client to run out of memory with tile mesh resolution 64 ? (Happens pretty easily with 128, so that is a known issue)

Orbiter 2024 has been released!

New Release D3D9Client Development

Conservative Pioneer

Active member

New member

Conservative Pioneer

Donator

Aspiring Addon Developer

Addon Developer

Aspiring Addon Developer

Addon Developer

Aspiring Addon Developer

New member

Well-known member

New member

Well-known member

New member

Well-known member

New member

Addon Developer

Well-known member

Well-known member

Similar threads