Search results

From the included documentation (Doc/Orbiter User Manual.pdf):

Sounds good to me!

I live in nixos permanently, and while I can run orbiter reasonably well using wine, I can't develop for it without a windows install, which is... disappointing.

I would love to merge your efforts into the mainline so we can get native linux support going, honestly. I'm not sure how much pain that would be?

Yeah, I held off on making a thread to hold issues for this one because I, too, felt that the GH issue tracker is the better place to track such issues for 2024; creating a thread here for them too would split the discussion between OF and GH and make it more difficult to keep track of progress...

For the moment, most likely they are identical; unless you intend to follow the pre-release versions for the next release of Orbiter, you can likely replace the one for the other. I would personally keep it around for the moment while you test if all the addons you want to use work with the...

To an extent, you can; the release notes on the github release page list all the contributions made to the repository since it was made open source. This is not, however, the exhaustive list of the changes between 2016-P1 and 2024, since quite a bit of closed development had happened in the old...

Yep. API version is 241231, as you would expect.

Some of us are even women! 😂

The 2024 edition of Orbiter.

Dear Orbiter Community, Orbiter 2024 has been released. As is tradition, today is Tuesday; it just happens to be the last day of 2024. Download link: https://cdn.openorbiter.space/orbiter-releases/Orbiter-2024.zip Almost 25 years ago, the first version of Orbiter, briefly known as “Orbit” was...

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...

Merged. If everyone is happy, I'll cut the final release build this afternoon.

No worries - I've moved this to a more suitable area so you stand a better chance of getting some helpful input.

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...

Are you suggesting this here as a feature that should be added to the Orbiter-Forum website, or should this go in the other section as a suggestion for a new standalone application?

They do; as I commented there I've amended the packaging approach slightly in hopes that a minor adjustment will get 2024 clear of the tower. We can address the problems more correctly and completely for subsequent releases.

Yeah, no idea. To recap the Things that have Happened: All the documentation work is now on main There was a tex build error that @n72.75 addressed which is now also fixed in main RC4 workflow is running now, this will be the final RC if successful Edit: RC4 was successful, awaiting final...

Damn, I didn't even think to look at the target branch. Is the whole thing ready to merge into main, or just that first part?

It is merged!