[New Release] D3D9Client Development

[Interceptor]

Quote:

Originally Posted by Kendo

 Kuddel, I have only 1 Client installed and ticked in Modules-Tab at LaunchPad, but I have left the ClientDebug unticked in Modules-Tab at LaunchPad, if I tick it, thats when 2 Clientdebug shows in Custom dropdown list. In Orbiter_Ng I have 1 D3D9client and no Clientdebug (unticked in Module Tab)
But as I said it all works pefectly.

One other question, does version 11 still use separate spec files, and are they saved as DtX1.?.

Just found out it can use separate spec files, and yes, you can save in DTX1..

Yes I am also encountering the same problem,also.

[jarmonik]

Quote:

Originally Posted by Cras

 I am just throwing it out there, but how easy, or rather if it is even possible, to add a key to the client that toggles some sort of frame rate lock? Make it user configurable, or even just something simple such as refresh rate or 1/2 refresh rate.

v-sync cannot be turned on/off on the fly, only during device initalization. It should be possible to reduce the framerate by using sleep() instruction in the rendering thread.

---------- Post added at 17:10 ---------- Previous post was at 17:07 ----------

Quote:

Originally Posted by Interceptor

 Yes I am also encountering the same problem,also.

Looks like distributin two version of the client in the same package was a big mistake. Just delete the D3D9ClientDebug.dll if it is causing so much of trouble.

[Disconnect]

Quote:

Originally Posted by jarmonik

 Can't view the video due to lack of format support.

Does it happen with every vessel or just with some specific one ?.

H264/AVC is a standard, and most widely used video format these days, and since years, mkv is an opensource format that is also widely used, and known by every opensource/free players (except of course the microsoft craps)

It happens with every vessel. But not on R9, only on R11.

[Kendo]

Intercepter, Thankyou, I thought i was going mad,

[jarmonik]

I have removed the R11 release due to graphics and Debug Controls problems. R10 is now the recommended release. I don't know when I got time to sort out the problems and make a new release.

[Screamer7]

That is fine with me Jarmo.
You've already done a monumental job on this program.
Take your time.

[Kendo]

Jarmonik Version 11 is perfect if you leave D3D9clientdebug UN-ticked in Launchpad/Modules, it still gives you one to use in the Custom dropdown list.
Version 11 is far superior all round to version 10. I have no graphical problems, and I use an Ati Radeon card. Pesonally, I would stick with version 11 and just point out what I said regarding the Debug control.

[Interceptor]

Yes,I also agree with kendo,Jarmonik this is the best version ,BTW your welcome Kendo.

[Cras]

Same here, I dont seem to have run into any issues thus far. I have run into something with a CTD on loading...... the log shows me a bunch of missing meshes, but swapping shaders fixes that and lets me boot up the scenario. I am not sure yet but it might have something to do with orbiter not closing properly.....

If I figure out what the exact repeatable events are I will let you know

But other than that, R11 is the best version so far.

[Interceptor]

Quote:

Originally Posted by jarmonik

 v-sync cannot be turned on/off on the fly, only during device initalization. It should be possible to reduce the framerate by using sleep() instruction in the rendering thread.

---------- Post added at 17:10 ---------- Previous post was at 17:07 ----------


Looks like distributin two version of the client in the same package was a big mistake. Just delete the D3D9ClientDebug.dll if it is causing so much of trouble.

Yes this solved the problem,thanks

---------- Post added at 10:10 AM ---------- Previous post was at 10:04 AM ----------

I have noticed in the last couple of releases that it seems the runwaylights from bases dissapear from view a lot quicker,than in earlier versions is there a way to adjust distance in the D3d9 config for this problem?just thought I would mention this, if you could take a look when ever you get the time Jarmonik.Thanks

[Disconnect]

Quote:

Originally Posted by jarmonik

 Thank you, those are very helpful. Could you take a close-up shot from the ladder. (Let's say 2-3 meter distance using 2048x2048)

From this camera distance there are no problem but I am worried about the close-up shots when the camera is near the vessel. Also should be remembered that we can't use as advanced filters as the 3DS Max does. (Maybe 2x2 PCF)

There is an open source train simulator, which is using cascaded shadow maps+ shadow edge blur (i think it's always necessary to prevent jagged shadow eges, and i see it in every dynamic shadow implementations), and there 1024*1024 shadow map resolution(default) is enough for the most of the cases, it's good enough to shadow so thin shapes like pantograph arms, however shadow map resolution is usually can be changed by user, either by directly setting the resolution or presets like "low, medium, high".

[Kendo]

I,m getting a error. When clearly the mesh is found and showing in Orbiter.
Only relates to some SC3 mods.

Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
**** WARNING: Mesh not found: .\Meshes\.msh
D3D9Client: [Scene Initialized]
D3D9Client: [Session Closed. Scene deleted.]
**** Closing simulation session
VistaBoost 1.0: font smoothing re-enabled.

May not be a D3D9 error though.

[DaveS]

The warning message is a standard message generated by SC3.dll as it can't load a mesh for the VC. Unless a mesh is specified in the ini file it will attempt to load a undefined mesh file which Or inter can't find so it generates the warning message in the log. It's harmless and can safely be ignored.

[Kendo]

DaveS, many thanks for your answer. Ken.