Linux playground

[Matias Saibene]

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

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

 

[johnnymanly]

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! And amazing too is the fact that he decided to share his code with the community and make it open source, not everyone would do that).

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

The makepkg doesn't install anything, pacman does. Just don't run pacman after you build the package. Instead copy the relevant package files to whatever orbiter directory.

 

[Eduard]

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

Ah, thanks. Alright, that's a separate build. Looking at the PKGBUILD would probably also work.
Great time for me to actually start learning a bit more about cmake one day. I have written in C and C++ on moments in the past (mostly not related to Orbiter), but not yet used cmake.
And I have also compiled some existing open source applications by hand in recent years, but just not cmake yet, or they silently had, but I did not need to touch it directly
(I am a software engineer, but mostly in other programming languages, although I have really touched a ton of things)

 

[Eduard]

The makepkg doesn't install anything, pacman does. Just don't run pacman after you build the package. Instead copy the relevant package files to whatever orbiter directory.

Thanks for your good intentions, but I really know Arch very well, my question was really because I just discovered this thread yet and I just started questioning and exploring how things would work for Orbiter specifically.

 

[johnnymanly]

Thanks for your good intentions, but I really know Arch very well, my question was really because I just discovered this thread yet and I just started questioning and exploring how things would work for Orbiter specifically.

Very good.

 

[Col Brubaker]

Thank you MuttonChops2010. But at the moment I have not enough space on my disks. And I don't want to start with Arch another project.

But now I also have a Kali with Orbiter and I am able to make a .iso from it. Well, now I have remove the big planets. But it works.
If somebody is interested, please ask me.

​

 

[johnnymanly]

I reported, a while ago, that I couldn't control a vessel class written in Lua with the numpad. RCS was fine just no control surfaces.
I just compiled a vessel class (a .so) and I have the same problem. No control surfaces with the numpad. Joystick is fine and stock vessels are fine.
Any similar experiences?

 

[Matias Saibene]

I reported, a while ago, that I couldn't control a vessel class written in Lua with the numpad. RCS was fine just no control surfaces.
I just compiled a vessel class (a .so) and I have the same problem. No control surfaces with the numpad. Joystick is fine and stock vessels are fine.
Any similar experiences?

Have you tried ALT+/ to activate the control surfaces? It happened to me with my I.Ae 37.

 

[johnnymanly]

Have you tried ALT+/ to activate the control surfaces? It happened to me with my I.Ae 37.

That was it!
Very clever...