Search results

Most of the B5 addons I recall seeing were published by @stevcast - this could be one of theirs; I didn't find anything in the OHM repository at a cursory glance.

It's funny, after the last time it died i set up an alert, and the alert just went off as I got the notification of this reply too, lol.

This would only ever be possible for the MFDs that ship with Orbiter, since it is up to the author of third-party modules to save and load their own state, but possibly

Oh that's my fault, some of the efforts I've been doing to try to get the debug libs to build correctly have modified the release page. The original release is still there, naturally, just the entries on the github page are a bit out of whack since the debug workflow has (incorrectly) changed...

We are working on this here: https://github.com/orbitersim/orbiter/pull/535 - progress has not been what I'd consider rapid but it is at least something that effort is being made towards resolving.

yes sorry human intervention is not immediate 😂

Yes!

all the old versions are available here; https://www.orbiter-forum.com/resources/categories/orbiter-download.15/ 010313 looks like it wasn't in the set i had though, that would be good to have for archive reasons!

Oh yeah, I meant to fix that a while ago and just forgot. It got broken by a Xenforo update. Fixed now.

I knew there was something I was forgetting to do... sorry! 😅

Yes, all the 5.4 work has been isolated to a separated branch to keep the mainline stable where it is in this regard. I don't really have particularly strong feelings one way or the other from the perspective of using 5.1 or 5.4; my concerns around this are pretty limited to what's easier to...

This error suggests a VCPKG environment variable is not set - it's supposed to be the prefix in that path. I know it seems trite but a reboot may resolve that to refresh the environment after the vcpkg installation. Edit: It looks like a manual configuration might be required, from that guide...

Where in your system did you unpack Orbiter to? This sort of behaviour might be expected if you're running from somewhere protected, like "C:\Program Files".

The ultimate goal (IMO) would be to ship a .zip package built for linux, in much the same way Orbiter is shipped for Windows for normal users. Being able to compile orbiter yourself is probably always going to require some specific knowledge that would be unreasonable to expect people to have...

Yes, it's a multi-select box. Hold CTRL while clicking to select multiple applicable options.

If you want to try out the 5.4 implementation, our WIP branch with it in is https://github.com/orbitersim/orbiter/tree/vcpkg-lua-54 - assuming you can build Orbiter, naturally, but that process should be a little more straightforward here also. I had some pain with the shipped lua scripts as...

There's a separate branch we've got held open for checking out pulling lua from vcpkg (at version 5.4 instead of 5.1) - the theory is this will make it easier to build on linux, though I haven't had much success getting a working toolchain set up for it.

This is at best off-topic for this thread and at worst, a subject that should be in the Basement, not here.

Yes, we have the tools to change the owner of an addon. It's how I uploaded the old versions of Orbiter and made them belong to Martin.

Documentation on this appears to be a little bit scarce, but the option in the ACP that controls whether this is enabled or not has this to say on the matter: It does not appear to be especially granular or adjustable. One of my design goals for OHM when it was a separate site was addon...