Terrible developer (seriously)
- Jul 7, 2012
- Reaction score
- Monte Hermoso - Argentina
I usually have several installations of Orbiter on Linux, simply following @Gondos' instructions in the first post and then I can copy and paste the orbiter_test folder wherever I want. Think of the AUR version of Orbiter as an MSI that installs to \ProgramFiles\.WOW! Is this real? Orbiter is actually really meeting Arch!!
I mean, it's just both on this planet , but it's even more than that too me.
For years I have been playing with Orbiter on Windows. In recent years, I became a total Linux geek too (especially Arch).
And I also have already experimented with my existing Orbiter 2016 instance in Wine, which already worked almost seamlessly with really decent performance (it worked using a DirectX to Vulcan port if I am right), with only some really small tweaks.
But clearly what we are talking about here looks like a native Linux build (ELF instead of EXE) from the Beta open source version if I am seeing it correctly. That's really amazing (still many credits go to Martin Schweiger for all his years of work of course!).
However, can I ask a question? The thing is, installing from AUR is great, but this generally installs Orbiter on in a centralized way on your system.
On Windows I am used to the fact that I can maintain multiple copies from Orbiter in separate directories.
What options do I have for this on Linux? Can I maintain multiple instances? (What I now about many Linux binaries is that these are often built and linked to specific library paths that cannot be changed, but maybe I can still have multiple user configurations or something like that?).