New Release D3D9Client Development

[jarmonik]

I still getting those random ctd-s when the first 3d spacecraft mesh should appear.
Now i could start demo/docked at iss scenario on third try.

Here is a debug build of D3D9Client RC24. Could you reproduce the CTD with this one and post the appcrash data like you did earlier.

 

[ky]

So, I'm waiting for Jarmonik's answer. Now I'll make a pre-release package.

NOTE: Installing ENB:
1. Copy "d3d9.dll" to Orbiter2010/Modules/Startup
2. Copy the rest of files into root dir of Orbiter
should work:thumbup:

Still having problems loading it.

 

[Disconnect]

Here is a debug build of D3D9Client RC24. Could you reproduce the CTD with this one and post the appcrash data like you did earlier.

attached the log

 

[jarmonik]

Here is one pretty fundamental question. I have never needed the oapiBlt() function in my Orbiter projects so...

What is the oapiBlt() function doing when a source or a target rectangle is partially outside the surface. Does it clip ? Or does it quit ?

 

[diogom]

I'm having a problem on activating the client. When I try to activate it in the Modules tab, I get an error message saying it cannot be activated because "d3dx9_42.dll" is missing.

 

[xmariox]

I'm having a problem on activating the client. When I try to activate it in the Modules tab, I get an error message saying it cannot be activated because "d3dx9_42.dll" is missing.

Maybe You need a DirectX February 2010 or newer to run D3D9Client http://www.microsoft.com/downloads/e...7-5ab8109cb4f5

 

[Tschachim]

What is the oapiBlt() function doing when a source or a target rectangle is partially outside the surface. Does it clip ? Or does it quit ?

AFAIR quit, i.e. doing nothing.

 

[dbeachy1]

:hesaid: Yep, at least that's how it behaves for me. Even one pixel outside = no render at all.

On the plus side, it makes it easy to spot a problem in your panel code that way. :tiphat:

 

[Frankynov]

I've some graphic artifacts with the current version of the client.

Here is a youtube video

[ame="http://www.youtube.com/watch?v=H_e-kNe1734"]YouTube - D3d9client bug in orbiter[/ame]

And the log.

 

[jarmonik]

I've some graphic artifacts with the current version of the client.

It looks bad but I can't reproduce it and it's definitely not a common problem.

1. Reinstall the Client and replace all existing files during installation.
2. Remove all ENB series tweaks you might have. That is very potential source for all kind of problems.

Can you reproduce it in a clean installation of Orbiter with official high resolution textures ?

Does it occur if cloud layers and cloud shadows are disbled ?

 

[N_Molson]

I had a similar problem once. I installed a lot of surface bases before (almost everything on Orbithangar), removing their config files solved the issue.

 

[Turbo]

Ive had this problem before as well on my old computer a couple years ago. However it had nothing to do with orbiter (or more importantly the d3d9 client). The problem turned out to be old Nvidia drivers. I updated and the screen tearing / flickering went away. It was an old Nvidia 7800. Maybe that could help?

 

[jarmonik]

D3D9ClientRC25

Here is RC25.

- ReEntry texture is now implemented.
- "PreLBaseVis" parameter added in D3D9Client.cfg to allow pre-load all base visuals. Should prevent "freezing" while in orbit.
- A few bugs has been fixed.
- 2D panel performance improments.
- Automatic check for Hardware 4xAA capability added.

 

[xmariox]

Shuttle fleet umbilical door animation also doesn't work under new client.

 

[blixel]

Here is RC25.

Hmm.... can you confirm this?

When I installed RC25, there seems to be a new ambient light bug that crept into the release.

When I reverted back to RC24, the problem went away.

---------- Post added at 05:32 AM ---------- Previous post was at 05:14 AM ----------

Something else I noticed - the surface of the moon has no ambient light. (But this seems to be the case with RC25 as well as RC24. Hmm...)

Inline graphics engine.

 

[Columbia42]

I can't confirm this. Ambient light works fine for me in RC25. Does this happen with other vessels? (I tested it with the DG because I don't currently have the XR2 installed.)

 

[jarmonik]

Hmm.... can you confirm this?
When I installed RC25, there seems to be a new ambient light bug that crept into the release.

I can confirm this and I did found the bug. But I don't understand why RC24 is working, it has the same bug.

 

[FordPrefect]

Hello all,

if anybody has got an idea about this. Just yesterday I updated only my graphics drivers (ATI) to the latest version (11.6) to improve performance within the "SpaceEngine" application, which actually helped there a lot.
Now, since that upgrade, it seems I can no longer run the Orbiter D3D9client. On starting Orbiter, I get this error message:

This is what the Orbiter loge file says after the crash:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 2.79365e-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 transx.dll ............ [Build 100824, API 100823]
Module TrackIR.dll ........... [Build 100830, API 100830]
TrackIR module not found.
Module ScriptMFD.dll ......... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module Rcontrol.dll .......... [Build 100830, API 100830]
Module OrbiterSound.dll ...... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module Meshdebug.dll ......... [Build 100830, API 100830]
Module LuaMFD.dll ............ [Build 100830, API 100830]
Module LuaConsole.dll ........ [Build 100830, API 100830]
Module Framerate.dll ......... [Build 100830, API 100830]
Module FlightData.dll ........ [Build 100830, API 100830]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module CustomMFD.dll ......... [Build 100830, API 100830]
Module GPCMFD.dll ............ [Build 110114, API 100830]
Error loading module Modules\Plugin\D3D9ClientDebug.dll (code 126)
Module UnivPTG.dll ........... [Build 100629, API 100606]
Module AutoFCS.dll ........... [Build ******, API 050206]
Module D3D9Client.dll ........ [Build 110618, API 101016]
D3D9Client: [DirectX 9 Initialized]

**** Creating simulation session
D3D9Client:FAIL: [Pixel Shader Version 2.0 or better is required]
D3D9Client:WARNING: [Insufficient Vertex Shader. Attempting software vertex processing...]
D3D9Client:WARNING: [Not a pure device]
D3D9Client:WARNING: [No Hardware T&L]
D3D9Client:WARNING: [No Hardware MipMap auto generation]
D3D9Client: ERROR: Failed to initialize 3D Framework
Joystick throttle: Z-AXIS
No joystick throttle control detected
---------------------------------------------------------------
>>> ERROR: DInput error DIERR_OBJECTNOTFOUND
>>> [DInput::SetJoystickProperties | .\Input.cpp | 186]
---------------------------------------------------------------

The strange thing is, before the upgrade, the Orbiter D3D9client was running fine. Any ideas? Thank you very much for any help! Does this possibly require an "DirectX End-User Runtimes (February 2010)" update as mentioned few posts earlier?

Greetings.

 

[orb]

Does this possibly require an "DirectX End-User Runtimes (February 2010)" update as mentioned few posts earlier?

The runtime hasn't changed, and the Feb 2010 version was required since the first builds, but try reinstalling it. If it does not help, try reinstalling drivers, maybe.

 

[jarmonik]

Error loading module Modules\Plugin\D3D9ClientDebug.dll (code 126)

You might have incorrent module selected. Also, what is written in /Modules/D3D9Client/D3D9ClientLog.html ?