MuttonChops2010
Member
I made a mistake. This was indeed the problem.
And you need to remove -Werror=format-security from /etc/makepkg.conf
Linux playground
- Thread starter Gondos
- Start date
And you need to remove -Werror=format-security from /etc/makepkg.conf
Gondos
Well-known member
Nice, but seems extreme to have to disable a systemwide option for just one package
MuttonChops2010
Member
We do have many such packages
Gondos
Well-known member
Had a bit of fun with an old raspberry pi. Sadly the little guy is quite RAM starved because there is no support for S3TC. I converted some DXT1 textures to ETC1 but there is no support for ETC2 so transparent textures need to stay uncompressed and it often ends up with a segfault due to memory issues... Most likely a raspberry pi 4 would do a lot better.
You seem serious about Orbiter's portability. I'm still waiting for the mobile phone version.
Sword7
Member
Yeah. Of course, we could see Orbiter on iOS and Android platforms soon. They need to compatible with OpenGL ES.
MuttonChops2010
Member
Please test our build on an Archlinux distribution (or a derivative of it) with the command:
Matias Saibene
Development hell
Hi @Gondos!
Investigating and testing Orbiter for Linux I have come to the conclusion that the deterioration in the fluidity of the image is not due to the inclusion of normalmaps. I tell you that I have been "developing add-ons" for Orbiter Linux and I have used normalmaps in my textures, but the performance deterioration occurred when the camera was looking towards a planet. So it must be something related to the rendering of celestial bodies. I leave you a video where the Luna3 probe is seen with little fluid animation but as soon as I change the camera and stop seeing the Moon the animation becomes more fluid. I hope it helps. It would also be useful to know if other Orbinauts have performance problems, maybe it's just my computer. Anyway, the low FPS is not annoying for me.
Investigating and testing Orbiter for Linux I have come to the conclusion that the deterioration in the fluidity of the image is not due to the inclusion of normalmaps. I tell you that I have been "developing add-ons" for Orbiter Linux and I have used normalmaps in my textures, but the performance deterioration occurred when the camera was looking towards a planet. So it must be something related to the rendering of celestial bodies. I leave you a video where the Luna3 probe is seen with little fluid animation but as soon as I change the camera and stop seeing the Moon the animation becomes more fluid. I hope it helps. It would also be useful to know if other Orbinauts have performance problems, maybe it's just my computer. Anyway, the low FPS is not annoying for me.
Sword7
Member
Your video is not available.
Update: Never mind. I have to go YouTube and was now able watch video.
Matias Saibene
Development hell
Thanks for letting me know, I fixed it.
Gondos
Well-known member
Hi Matias,
I think the problem is two-fold (I'm having similar issues on the raspberry pi) :
- tile loading is not threaded so it will cause heavy choppiness whenever a new tile needs loading. I don't think this is your case here since you're not in low orbit and the moon is almost always showing the same tiles.
- the shader is really badly optimized (I'd rather say pessimized since no real effort has been made to make it faster). I guess this is your issue.
Edit : with a bit of tweaking it runs at about 30fps with vsync enabled at 1280x1024 resolution (RPi3B at 1.2GHz) :
Last edited:
Col Brubaker
Hoax Developer
Hello folks,
I joined the club. I installed Orbiter on Kali Linux. But it closes all the time at start.
Could somebody assist with the bug-fixes? I think it is the sound module?
I joined the club. I installed Orbiter on Kali Linux. But it closes all the time at start.
Could somebody assist with the bug-fixes? I think it is the sound module?
Last edited:
Gondos
Well-known member
Hi,
This looks more like missing planetary textures. Did you extract Orbiter2016.zip in the correct path?
Col Brubaker
Hoax Developer
I don't know, I actually just run your routines thru Konsole and fixed the missing parts. All I did was following the instructions from your first post.
It starts, but collapse after 3-5 seconds into the scenario.
What is the correct path?
How to remove it and do it again?
- I actually had no idea what I did.
It starts, but collapse after 3-5 seconds into the scenario.
What is the correct path?
How to remove it and do it again?
- I actually had no idea what I did.
Last edited:
Gondos
Well-known member
OK, let's suppose you did it correctly then.I don't know, I actually just run your routines thru Konsole and fixed the missing parts. All I did was following the instructions from your first post.
It starts, but collapse after 3-5 seconds into the scenario.
What is the correct path?
How to remove it and do it again?
- I actually had no idea what I did.
Try running with a debugger and post a backtrace :
gdb ./Orbiter
and type "run" when the prompt appears. Then when it crashes type "bt" in the prompt to dump the backtrace (type "quit" to exit the debugger).
Col Brubaker
Hoax Developer
I am sorry, but I don't know what a debugger is. I know it from QBasic.
Honestly I didn't understand a word.
And btw. I am on AMD.
Honestly I didn't understand a word.
And btw. I am on AMD.
Gondos
Well-known member
You must run it from the install dir :
cd ~/orbiter_test/Orbiter
gdb ./Orbiter
AMD should be OK, I've got it running on nvidia and VC4
Col Brubaker
Hoax Developer
Can I install Orbiter Addons in this directory`? Perhaps Orbiter sound is missing? Or it is my sound card?
NOW I got what you want:
NOW I got what you want:
And this:
And this:...
Loading Sound/ProjectApollo/rotary.wav
Loading Sound/ProjectApollo/circuit_breaker.wav
oapiBlt Colour key argument not supported by graphics client
[New Thread 0x7fffacceb6c0 (LWP 5827)]
Thread 1 "Orbiter" received signal SIGILL, Illegal instruction.
0x00007fffc6146641 in ProjectApolloChecklistMFD::Update(oapi::Sketchpad*) () from Modules/Plugin/libProjectApolloMFD.so
(gdb) bt
#0 0x00007fffc6146641 in ProjectApolloChecklistMFD::Update(oapi::Sketchpad*) () from Modules/Plugin/libProjectApolloMFD.so
#1 0x0000555555836d49 in Instrument_User::UpdateDraw(oapi::Sketchpad*) ()
#2 0x000055555580a70a in Instrument::Update(double) ()
#3 0x00005555557f88aa in Pane::Update(double, double) ()
#4 0x0000555555724e09 in Orbiter::EndTimeStep(bool) ()
#5 0x000055555572177c in Orbiter::StartSession(Config*, char const*) ()
#6 0x0000555555720d96 in Orbiter::Launch(char const*) ()
#7 0x000055555574988d in DlgLaunchpad:
#8 0x000055555574965f in DlgLaunchpad::Show() ()
#9 0x000055555586638e in GUIManager::RenderGUI() ()
#10 0x00005555557224fc in Orbiter::RenderGUI() ()
#11 0x000055555572282f in Orbiter::Run() ()
#12 0x000055555571f11a in main ()
(gdb) Quit
(gdb)
Last edited:
Gondos
Well-known member
This is using XRSound which is pqrt of OpenOrbiter so there should be no issue. You can disable the module if you want to make sure.
The first crash looks like a missing a texture file.
I'm on windows right now but from the directory containing the Orbiter binary you should have something like this:
Code:
Gondos@DESKTOP-HAH0M9G MINGW64 /c/github/orbiter/out/install/x64-release/Orbiter (linux)
$ find|grep tree
./Textures/Earth/Archive/Cloud.tree
./Textures/Earth/Archive/Elev.tree
./Textures/Earth/Archive/Elev_mod.tree
./Textures/Earth/Archive/Mask.tree
./Textures/Earth/Archive/Surf.tree
./Textures/Mars/Archive/Elev.tree
./Textures/Mars/Archive/Surf.tree
./Textures/Moon/Archive/Elev.tree
./Textures/Moon/Archive/Surf.treeCol Brubaker
Hoax Developer
I also tried with deactivated XRSound Module. Same result.
I have to install 64Gb? of textures? Do the Old Hi-Res work for a try?
Latest update I got - I installed this:
I have to install 64Gb? of textures? Do the Old Hi-Res work for a try?
Latest update I got - I installed this:
Similar threads
