New Release D3D9Client Development

Not sure if this is known, but I just found out that the spotlights behave like light points, with the light going in all directions. Using Orbiter Beta, D3D9 R25.3.
 
Not sure if this is known, but I just found out that the spotlights behave like light points, with the light going in all directions. Using Orbiter Beta, D3D9 R25.3.

That was fixed a while ago but it's not yet merged in Orbiter Beta branch.
 
Hey everyone, Ive been trying to get the DxD9 client to work (since i have to use orbiter2010 since UCGO and most other addons still aren't sorted for 2016,) and i keep getting the message "The procedure entry point ?ElevationGrid@GraphicsCient@oapi@@QBE_NPAXHHHHHHPAF1PAN@Z could not be located in the dynamic link library D:\(my orbiter directory)\Modules\Plugin\D3D9client.dll."

I've installed the Feb2010 DirectX package, but that didnt change it. Also, the 'Video Settings' tab doesnt appear in Orbiter_NG. can't find any other information on it elswhere on the web, so i figured i'd com here. any ideas?
 
Hey everyone, Ive been trying to get the DxD9 client to work (since i have to use orbiter2010 since UCGO and most other addons still aren't sorted for 2016,) and i keep getting the message "The procedure entry point ?ElevationGrid@GraphicsCient@oapi@@QBE_NPAXHHHHHHPAF1PAN@Z could not be located in the dynamic link library D:\(my orbiter directory)\Modules\Plugin\D3D9client.dll."

I've installed the Feb2010 DirectX package, but that didnt change it. Also, the 'Video Settings' tab doesnt appear in Orbiter_NG. can't find any other information on it elswhere on the web, so i figured i'd com here. any ideas?

You have incompatible versions of the Orbiter and the Client installed.

Here's the latest build D3D9ClientR16.5 for Orbiter 2010-P1: http://www.tuttovola.org/index.php?action=downloads;sa=view;down=1134
Download orbiter 2016 builds from the next post...

---------- Post added at 11:05 ---------- Previous post was at 11:03 ----------

Has something changed re: reflections between the Release branch and the Beta branch? That would explain why GLS and I get such different reflections with the exact same textures: http://www.orbiter-forum.com/showthread.php?p=555721&postcount=542

The Release is much more accurate producing the dull reflection it should.
I don't recall all the details but let's see if the problem exists in the next release...
 
Last edited:
D3D9Client2016 Beta 4

Here's the latest build for Orbiter 2016 and Orbiter Beta...

- Camera altitude related horizon haze and atmosphere opacity jumps should be fixed.
- Local light sources flickering and spotlight issues should be fixed.
- Sun glare visibility is now fixed.
- Mesh group flag 0x2 is now effecting in MFDs and HUD. Pay attention to VC MFD related issues/problems those might appear.


R2-Beta4 is for Official Orbiter 2016 release.
25_4-forRev65 is for the latest Orbiter Beta.
 

Attachments

The reflections issue seems fixed.
 
The latest version R2 Beta 4 also fixes one longstanding bug with animations targeting secondary meshes.

Meaning that now my OK-GLI cockpit gauges are working! :cheers:
I'm happy!
 
What happened to my beautiful Earth textures and realistic sunsets ? They disappeared looks more like 2010 textures ?:shrug:
 
The latest version R2 Beta 4 also fixes one longstanding bug with animations targeting secondary meshes.

Meaning that now my OK-GLI cockpit gauges are working! :cheers:

Sorry, I don't recall an issue like that being reported. What do you mean by "targeting secondary meshes" ?
There are no changes made into the animations. There are texturing/emission map related bug fixes in the latest revision.

---------- Post added at 07:36 ---------- Previous post was at 07:34 ----------

What happened to my beautiful Earth textures and realistic sunsets ? They disappeared looks more like 2010 textures ?:shrug:

Check that "TileFormat" is set to "2" in your Earth.cfg. Some addons do overwrite the default Earth.cfg with an older one.
 
That was the problem. The one I had has hardly any visualization perimeters in it. I found one that did. Thanks !!!
 
There was mention a long while back of a way to switch between PBR and legacy shaders on a per-meshgroup basis. How do I do that?
 
There was mention a long while back of a way to switch between PBR and legacy shaders on a per-meshgroup basis. How do I do that?

We don't have separate shaders for PBR and legacy modes. Both are implemented in the same shader. It will switch between the two based on which texture maps are specified.

Does the attached document answer to your question ?

There is a "Data Window" added in mesh debugger that will display more detailed information about the pipeline state. The fresnel map is not fully implemented. I am not exactly sure how to implement it. Also, It would seem that most materials becomes more reflective when viewed from a very shallow angle, so, maybe it should be turned on by default.
 

Attachments

We don't have separate shaders for PBR and legacy modes. Both are implemented in the same shader. It will switch between the two based on which texture maps are specified.

Does the attached document answer to your question ?

Thanks! I think it does. If I understand it correctly, all I have to do is create a .spec texture map, and the shader will switch to legacy mode.

I've had a long hiatus, but I'm trying to get caught up with development. I like the added options in the debug window, and I'll take a look at the fresnel map implementation once I get more up to speed.
 
spacecraft.dll and Orbiter BETA

Hello there,

I have a question regarding spacecraft.dll (version 2, 3 or 4):
I like to implement a hint -for the user of D3D9Client- whether the current loading version of spacecraft.dll is "O.K."ed for the running version of Orbiter.

Now the question:
Is there any spacecraft.dll version that is working for Orbiter BETA (r64)?

Or are these the only working pairs?
Orbiter 2016|???
Orbiter 2010-P1|spacecraft4.dll
Orbiter OLDER|spacecraft3.dll
 
Last edited:
Hello there,

I have a question regarding spacecraft.dll (version 2, 3 or 4):
I like to implement a hint -for the user of D3D9Client- whether the current loading version of spacecraft.dll is "O.K."ed for the running version of Orbiter.

Now the question:
Is there any spacecraft.dll version that is working for Orbiter BETA (r64)?

Or are these the only working pairs?
Orbiter 2016|???
Orbiter 2010-P1|spacecraft4.dll
Orbiter OLDER|spacecraft3.dll

Neither for "official" Orbiter 2016 nor for the beta there is a dedicated SCx. Donamy seems to be beta-testing an SC5 version for Vinka, but that is hearsay.

Both SC3 and SC4 kind of work in 2016, but suffer from various bugs of essential features.
 
Haven't heard from Vinka in awhile, SC5 seems to work pretty well. There are still issues with attachments.
 
Any help with this log message?
Code:
D3D9: ERROR: SurfHandle=0xE5343F0, Never use Sketchpad::GetDC() hDC not available
 
Any help with this log message?
Code:
D3D9: ERROR: SurfHandle=0xE5343F0, Never use Sketchpad::GetDC() hDC not available

The sketchpad in D3D9 is using DirectX to render a graphics. Calling oapiCrerateSketchpad() will bind the target surface to a GPU and the GPU is prepared to receive a drawing instructions. At this point there is no way of getting a hDC to the target surface.

In general, DirectX 9 is internally multi-threaded therefore mixing a CPU and GPU based drawing instructions do cause a severe thread synchronization issues. Resulting lag, stalls and frame skips.

---------- Post added at 03:43 ---------- Previous post was at 03:42 ----------

Haven't heard from Vinka in awhile, SC5 seems to work pretty well. There are still issues with attachments.

Does SC5 still require symbolic links or is it able to fetch the configuration files from the right place by on it's own ?

---------- Post added at 04:08 ---------- Previous post was at 03:43 ----------

I like the added options in the debug window, and I'll take a look at the fresnel map implementation once I get more up to speed.
OK, Thanks. That would be appreciated.
 

Does SC5 still require symbolic links or is it able to fetch the configuration files from the right place by on it's own ?

I did get a warning when I started the clean install.
 
Back
Top