New Release D3D9Client Development

[Marg]

I also had this bitDefender warning form Orbiter2016 version d3d9client.dll like "Gen:Variant.Babar.108092" I suppose it is false?

 

[jarmonik]

I also had this bitDefender warning form Orbiter2016 version d3d9client.dll like "Gen:Variant.Babar.108092" I suppose it is false?

I can't tell, my software sees nothing there. I once had a payed security suite and it gave me a tons of false alarms. Felt like it was trying to cause panic. Would be good idea for people to make a scan of it to be sure. It's the same package that's been available for a year already. No recompile, no re-zipping.

 

[jarmonik]

So, is

http://users.kymp.net/~p501474a/D3D9Client/

forever gone?

Hosting service provider quit providing service. The page could become a live but not in that address. Right now, there's no plant to bring it back.

 

[Marg]

I can't tell, my software sees nothing there. I once had a payed security suite and it gave me a tons of false alarms. Felt like it was trying to cause panic. Would be good idea for people to make a scan of it to be sure. It's the same package that's been available for a year already. No recompile, no re-zipping.

So I assume it wasn't new "atmospheric" version...

 

[Abloheet]

So I assume it wasn't new "atmospheric" version...

Orbiter 2016 D3D9Client won't be getting the new atmosphere remake. That's only for OpenOrbiter

 

[Marg]

Orbiter 2016 D3D9Client won't be getting the new atmosphere remake. That's only for OpenOrbiter

Yes, I understood. It would be good to get some d3d9 release (compiled) at some moment later for OpenOrbiter.

 

[Abloheet]

Yes, I understood. It would be good to get some d3d9 release (compiled) at some moment later for OpenOrbiter.

AFAIK, D3D9Client is now integrated into OpenOrbiter, atleast in the d3d9_atmo_remake branch. Some time ago that branch was merged into main

 

[jarmonik]

Latest binary package for OpenOrbiter can be obtained with these instructions: Post

 

[Marg]

Latest binary package for OpenOrbiter can be obtained with these instructions: Post

Unfortunately I do not see how to download artifacts from #324 merge pull request (that seems latest). No link.

 

[Jordan]

Unfortunately I do not see how to download artifacts from #324 merge pull request (that seems latest). No link.

As martins said "select the latest merge action"
https://github.com/orbitersim/orbiter/actions/runs/3812741828

 

[Marg]

As martins said "select the latest merge action"
https://github.com/orbitersim/orbiter/actions/runs/3812741828

Oops, I just was logged out of gitHub, but now it's OK. Hm, new atmosphere is really impressive, nothing bad to say.
Only the sun's glare is not perfect (sun also shines through terrain and non-vessel objects), but it seems like a work is in the progress. Interesting when I accelerated time before sunrise, Shuttle Atlantis was suddenly erraticaly got lit by sunlight ON\OFF.

 

[DaveS]

You don't have to have a GitHub account to download the latest release. You can do so from here: https://github.com/orbitersim/orbiter/releases and clicking on "Assets".

 

[Abloheet]

I downloaded the latest release artifact from the orbiter repo on GitHub, then followed the process for installing a working copy of OpenOrbiter, which is

Get a working copy of Orbiter 2016 with all the high res textures

Then extract OpenOrbiter to another folder

Specify the PlanetTex dir in the configuration file

OpenOrbiter runs fine, but whenever I enable the planet surface markers and base and vessel markers, there seems to be a glitch with rendering of vessels in D3D9Client

There is a flickering of reflective surfaces like the solar panels of the ISS, and the retro thruster doors of the DG look inside out. There is also a black shimmering patch on the radiator doors on the back of the DG. If I disable the markers using Alt-F9, the problem goes away
Again enabling the markers causes reappearance of the issue
I have not changed any of the default settings on d3d9.cfg and when markers are disabled everything works as it should

 

[Nikogori]

Sorry for asking off-topic question. (I have asked the same question twice but didn't get answer)
@jarmonik Do you plan to re-upload IMFD and LTMFD?

Manual53.pdf says You may not sell or redistribute this software.
A few years ago I wrote IMFD tutorial for Japanese. I'd be grateful if you made them available again.

 

[jarmonik]

Sorry for asking off-topic question. (I have asked the same question twice but didn't get answer)
@jarmonik Do you plan to re-upload IMFD and LTMFD?

Sorry, The so called "reallife" been keeping me busy and haven't had time to visit the forums. I have managed to upload IMFD 4.2.2 and 5.7 but failed to upload LTMFD. I'll try again later as the error message told me to. I'll combine all tutorials I got into a single package and upload it.

 

[Nikogori]

Thank you! I have successfully downloaded both IMFD and LTMFD.

 

[BrianJ]

EDIT: Oh!! Sorry! I didn't realise the site had gone!! Never mind

Hi,
if I follow the download link on the 1st post to "Project Site", it now redirects me to:

Elisan asiakaspalvelu - Elisa

Elisan asiakaspalvelun ohjeiden avulla saat ratkaistua useimmat asiat sekä löydät ohjeita laskuihin, liittymiin, laitteisiin ja asetuksiin.

elisa.fi

Is it just me? Is this the correct site ??

Cheers,
BrianJ

 

[misha.physics]

I'm wondering what parameter corresponds to the surface brightness. I launched the same scenario in Orbiter 2016 (left) and OpenOrbiter (right), and the first one is much brighter:



So, is it possible to make the right one brighter?

And what are these colored spots on the surface? Do they related to the D3D9 MicroTexture Pack 1.0?

 

[jarmonik]

The colored spots are related to micro textures, likely a compression problem. Surface brightness can be adjusted from the atmospheric control panel. Is the darkness due to low sun angle or is the Moon globally dark ?

 

[n72.75]

Interesting bit of info: I recently ran through the default windows monitor calibration, which had me adjust the gamma by quite a bit (12%ish, up iirc).

I have since reset the D3D9 client gamma correction to the default. If anyone finds they need to correct the default gamma or color settings in D3D9 client, it's probably worth running through the basic monitor calibration first.