Orbiter 2024 Launch readiness

A few more things that IMO have to be handled:
  • debug libs are missing (apparently the idea is to add them manually with the post-fix "D")
  • lua.lib is in the root folder instead of (probably) "Orbitersdk\lib\Lua\"
  • the Antelope Valley scenario folder should not be shipped, as that pack is not included (manually delete for now?)
 
Removing the Antelope Valley scenarios feels trivial; the other points here a little less so. I had a brief look into why lua.lib is ending up in the root folder - it looks (to my limited ability to follow the cmake lists) like it's tied to the lua.dll path, which goes into the root so orbiter can find it (I assume). A manual move during packaging would probably work, but this doesn't strike me as the best solution here (not that I currently have a better one to offer).

Regarding debug libs I've no idea. It's been a very long time since I was actively developing anything for Orbiter; others are surely more qualified to input here.
 
So... "Orbiter 2025"?
For the UTC timezone the release will cut 2024-12-31, so no, it will be 2024.

For the debug libs, I think we're best off leaving things as they currently are and packaging these separately for the 2024 release. We can look at sorting out packaging them into the main release along with pulling textures in from LFS for the next release.

I'm aware there are a long line of PRs building up that all say "for after 2024" too, so let's light this candle.

Edit: 'tis done; https://www.orbiter-forum.com/threads/orbiter-2024-release.42062/
 
Last edited:
I have prepared a hopefully adequately detailed feature request detailing what I think would be useful improvements on the current joystick support - is it appropriate to post it as an issue in GitHub?
Sounds good to me!
 
I have prepared a hopefully adequately detailed feature request detailing what I think would be useful improvements on the current joystick support - is it appropriate to post it as an issue in GitHub?

Yes please. If that improves gamepad support for us travelling folk, even better!
 
What is the relative path for placing shared DLLs for add-on modules? Also in "modules" or do they belong in the root folder?
 
I don't know what exactly you mean by shared DLLs...
  • Shared by (possibly) multiple add-ons?
    Then I would suggest: <OrbiterRoot>\Modules\Shared\ or <OrbiterRoot>\Modules\Plugin\Shared\
    Since both have their reasoning, I cannot decide :D
    ...aaaaand <OrbiterRoot>\Modules\ and <OrbiterRoot>\ all have "examples" of those, too.

  • Shared by one add-on (3rd party possibly)?
    I would still vote for <OrbiterRoot>\Modules\Plugin\<PluginName>\Shared\

  • Something completely different ;)
 
Last edited:
Has the Camera MFD been changed in Orbiter 2024 compared to Orbiter 2016? In Orbiter 2024 it looks like:

Без імені.png

But it seems to be different in Orbiter 2016, namely there were options to create new cameras, switch between them, delete cameras, rotate and shift cameras. There were buttons like RG and DEL.
 
Back
Top