OHM Falcon9 for Orbiter2016

[BrianJ]

Congrats!
Probably not relevant anymore, Crew Dragon lights do work as you described!

I'll take that to mean SLC40 now works OK.
Good!
Thanks for testing. I will update the add-on.

(code error - failure to initialize DEVMESHHANDLE value. Doh!)

Cheers,
Brian

 

[ZacharyS41]

Brian, I was wondering now that Orbiter 2024 is out; are any of your addons compatible with that latest version of Orbiter?

 

[BrianJ]

Brian, I was wondering now that Orbiter 2024 is out; are any of your addons compatible with that latest version of Orbiter?

Hi,
I don't know - haven't even had time to settle down and try Orbiter 2024 yet.
I'm focused on trying to rebuild my kitchen and bathroom. Been at it since before Christmas!
Cheers,
Brian

 

[jacquesmomo]

I'm focused on trying to rebuild my kitchen and bathroom.

 

[gamer19]

for a moment I thought he was planning to import his kitchen and bathroom into the game

guess it's time for me to take a break from gaming

 

[ZacharyS41]

Hi,
I don't know - haven't even had time to settle down and try Orbiter 2024 yet.
I'm focused on trying to rebuild my kitchen and bathroom. Been at it since before Christmas!
Cheers,
Brian

All right. Hope they turn out well.

 

[BrianJ]

All right. Hope they turn out well.

Thanks. Its coming along OK

for a moment I thought he was planning to import his kitchen and bathroom into the game

I wish. Easier and cheaper!

Anyway, I must try out the Orbiter 2024 soon and report back.
Cheers,
Brian

 

[BrianJ]

Hi,
finally had time to try out OpenOrbiter2024 - works fine for me on ancient PC, Windows8.1 - except my mouse scroll wheel gets lost sometimes (can't change view point/zoom).

But certainly some issues with Falcon9 and FalconHeavy add-ons + OpenOrbiter2024.....

1. Default Graphics & D3D9 Graphics Client: Booster landing autopilot is semi-broken leading to total depletion of RCS propellant and/or failed landing.
Fix: Turn off Orbiter "Wind Effects"

2. D3D9 Graphics Client only: Custom textures (charred booster, custom fairing) rendered incorrectly depending on viewpoint distance.
Fix: Go to Orbiter launchpad Video -> Advanced ->Texture mipmaps -> select "Load As Defined"

3. Default Graphics & D3D9 Graphics Client: OrbiterSound no longer supported (gives me CTD) so no stage sep. callouts, helicopter rotor sound, etc.
Fix: None

Cheers,
Brian

 

[ZacharyS41]

Hi,
finally had time to try out OpenOrbiter2024 - works fine for me on ancient PC, Windows8.1 - except my mouse scroll wheel gets lost sometimes (can't change view point/zoom).

But certainly some issues with Falcon9 and FalconHeavy add-ons + OpenOrbiter2024.....

1. Default Graphics & D3D9 Graphics Client: Booster landing autopilot is semi-broken leading to total depletion of RCS propellant and/or failed landing.
Fix: Turn off Orbiter "Wind Effects"

2. D3D9 Graphics Client only: Custom textures (charred booster, custom fairing) rendered incorrectly depending on viewpoint distance.
Fix: Go to Orbiter launchpad Video -> Advanced ->Texture mipmaps -> select "Load As Defined"

3. Default Graphics & D3D9 Graphics Client: OrbiterSound no longer supported (gives me CTD) so no stage sep. callouts, helicopter rotor sound, etc.
Fix: None

Cheers,
Brian

Got some work to do until then.

 

[jacquesmomo]

Finally had time to try out OpenOrbiter2024 - works fine for me on ancient PC, Windows8.1 - except my mouse scroll wheel gets lost sometimes (can't change view point/zoom).

I also noticed the same issue

And I noticed one more thing...
Do you have the same phenomenon:

When my mouse is no longer responding for zooming, if I press a key on the keyboard (like T or R for example) it works (here in this example the acceleration of the simulation).
Bbut pressing the keys (same for all keys) causes the default Windows sound "when there is a problem"...
(the usual Windows sound "ting" in french....)

Do you have this?

Default Graphics & D3D9 Graphics Client: OrbiterSound no longer supported (gives me CTD) so no stage sep. callouts, helicopter rotor sound, etc.

So I tried to install OrbiterSound : everything seems to work fine.

You just have to remember to disable XRSound and enable OrbiterSound
(and vice versa to return to "default" setting)

 

[BrianJ]

Hi Jacques,
so OrbiterSound5.0 works OK with OpenOrbiter2024 D3D9 Graphics Client - but gives me immediate CTD with OpenOrbiter2024 Default Graphics.
(I was using OrbiterSound4.0 before)

When my mouse is no longer responding for zooming, if I press a key on the keyboard (like T or R for example) it works (here in this example the acceleration of the simulation).
Bbut pressing the keys (same for all keys) causes the default Windows sound "when there is a problem"...
(the usual Windows sound "ting" in french....)

Do you have this?

No, I do not have the "ting" when the mouse wheel stops responding.

Cheers,
Brian

 

[BrianJ]

Hi,
I'm getting a CTD using OpenOrbiter2024 D3D9 GC on any saved scenario post-booster separation.
Works OK using OpenOrbiter2024 D3D7 default graphics.
Anyone else seeing this?
Thanks,
Brian

 

[francisdrake]

Hi, I am using the D3D9 client in Orbiter 2024. Tested a few scenarios by quitting and re-starting the (Current state.scn).
All went well. Tested them after booster sep, fairing sep, payload jettison, fuel dump. Found no issues.

 

[BrianJ]

Hi, I am using the D3D9 client in Orbiter 2024. Tested a few scenarios by quitting and re-starting the (Current state.scn).
All went well. Tested them after booster sep, fairing sep, payload jettison, fuel dump. Found no issues.

Thanks for the report. I tracked it down to un-initialized DEVMESHHANDLE value - if your system decides it is 0 at sim start you're OK - if not then CTD. I'm surprised it didn't bite me til now.
I fixed the booster auto-pilot problem.
The custom texture problem remains in Orbiter2024, but can be fixed as per my earlier post.
I'll upload an update soon.
Cheers,
Brian

 

[BrianJ]

Update 250122

Fixed some stuff so it works in OpenOrbiter2024.

Cheers,
Brian

 

[Max-Q]

The custom texture problem remains in Orbiter2024, but can be fixed as per my earlier post.

This is a known issue with OpenOrbiter2024, more work is needed to determine exactly what is going on.

 

[BrianJ]

This is a known issue with OpenOrbiter2024, more work is needed to determine exactly what is going on.

My guess is that its a combination of using oapiBlt(...) to swap vessel skin textures, and OpenOrbiter2024 generating texture mipmaps for vessel textures:

oapiBlt(...) only swaps the main texture, not the mipmaps.
So from a distance you get the originals mipmaps, up close you get the new texture - or actually a blend of the two.

Thats my guess.

Fix? Maybe use SetTexture(...) instead, but I think that will mean changing a bunch of other stuff also.
I haven't tried it yet, will wait until I can get my compiler to work with Orbiter2024 SDK.

Cheers,
Brian