Linux Support

[fooka]

Yay! thank you for the impending Linux version!

I have a chicken/egg problem where I don't want to count as a windows sale, so forced to wait to buy it for Linux.. I was worried, but this thread is very busy, so I can happily wait.

I'll still be buying it full price..

thank you for continuing to support defenestrated gamers!

-m

[andrewpc]

Reading this

I installed the AMDVLK package (version 2.63.1120.g81fd878-1) but really have no idea what it does. I would highly appreciate help in that regard.
Also, if it is fixed in LLVM 8.x and mesa 19.x, I'll wait and not install mesa-git for example. I waited for X4 since its release. I can wait a bit longer. I'm just happy that all my Linux brethren are able to play

You can use differrent Vulkan driver by changing VK_ICD_FILENAMES environment variable. Go to /usr/share/vulkan/icd.d directory, there should several json files, notabl radeon_icd.x86_64.json and amd_icd.x86_64.json. Their names may slightly differ on different distros, but the one with "radeon" is Mesa's RADV and one with "amd" is AMDVLK. In order to use AMDVLK with X4 you need to edit command line parameters in the game's properties dialog in Steam and put following there:

Code: Select all

VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/<AMDVLK's json file>" %command%

With my RX 580 AMDVLK offered better performance than RADV.

THANK YOU SO MUCH.

I am now running the game with

Code: Select all

VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/amd_icd64.json" %command% -skipintro -logfile debug.log

And it worked. No hangs, nothing. Thank you everyone who helped me with this!

I decided it was time to compile the AMDVLK driver on my opensuse tumbleweed system and try it out. I can report back that the game is also working for me using this driver on my Vega64. Thanks for pointing me in this direction. We now need to get the RADV driver also working so I am happy to help run tests to get to the bottom of the issue a few of us are faced with.

[radcapricorn]

Looks to be the Linux version. Those files exist. No exe files.

Do you have the Vulkan ICD loader installed? (concrete package name varies between distros). What does vulkaninfo say?

[jhaand]

Hi,

Thanks for releasing the Linux build. Everything works fine except for 1 little thing.
The sound level remains too low. I got everything maxed out in the game but the sound remains on the quiet side.

Is this a known issue?

I run KDE on Debian.

[Rastuasi]

Hi,

Thanks for releasing the Linux build. Everything works fine except for 1 little thing.
The sound level remains too low. I got everything maxed out in the game but the sound remains on the quiet side.

Is this a known issue?

I run KDE on Debian.

I would go to say it's a bit too loud actually, had to turn everything to 25% for my system.

[ant1393]

Hi,

Thanks for releasing the Linux build. Everything works fine except for 1 little thing.
The sound level remains too low. I got everything maxed out in the game but the sound remains on the quiet side.

Is this a known issue?

I run KDE on Debian.

sound is normal here : pulseaudio + pulse-effects (limiter at 0 dB + stereo width to 110 %)

only when i shoot pulse lazer the sound is almost inaudible or very very low.. => FX + ambiance is inaudible.

+ i hope gamepad mouse cursor gonna be fixed !

[_JD_]

Regarding the Joystick deadzone slider not working, I did some more tests:

• X4: Foundations: does NOT work
• X Rebirth: does NOT work
• X3: Albion Prelude: works!
• X3: Terran Conflict: works!

If is useful, I can test also X3: Reunion, just let me know.

[major_bird]

Hi,

Not sure if this i really related to linux but I will post it here anyways because i am playing the linux beta:

When I am in Argon Prime, flying a ship and then standing up from the pilot seat my ship gets instantly jumped to Grand Exchange. Always to the same spot and I can repeat it easily. I always jump next to the unknown station, so maybe it has something to do with that.
This does not happen in other sectors. Only when in Argon Prime and when I am standing up from the pilot seat.

[fallenwizard]

Hi,

Not sure if this i really related to linux but I will post it here anyways because i am playing the linux beta:

When I am in Argon Prime, flying a ship and then standing up from the pilot seat my ship gets instantly jumped to Grand Exchange. Always to the same spot and I can repeat it easily. I always jump next to the unknown station, so maybe it has something to do with that.
This does not happen in other sectors. Only when in Argon Prime and when I am standing up from the pilot seat.

Did you fly through the anomaly?

If not:
Please attach the save. The devs have been hunting those kind of bugs since release. A reproducible save game will be very helpful to them.

[Knossos]

Looks to be the Linux version. Those files exist. No exe files.

Do you have the Vulkan ICD loader installed? (concrete package name varies between distros). What does vulkaninfo say?

I haven't done any installation outside of this:

sudo apt-get install libvulkan1 libvulkan1:i386
sudo apt-get install mesa-vulkan-drivers mesa-vulkan-drivers:i386

Here's my vulkaninfo - it doesn't look good.

$ vulkaninfo
==========
VULKANINFO
==========

Vulkan Instance Version: 1.1.82

ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32
/build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:3339: failed with VK_ERROR_INITIALIZATION_FAILED

[BerndHohmann]

ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32

Try to remove the two Vulcan :i386 libs you had installed before, X4 is 64bit only.

Also chdir to the X4 Steam installation directory and try

Code: Select all

ldd -d X4 | grep -e vulkan

Output should look like

Code: Select all

libvulkan.so.1 => /usr/lib/x86_64-linux-gnu/libvulkan.so.1 (0x00007f48c3a33000)

And /usr/lib/x86_64-linux-gnu/libvulcan.so.1 should exist.

Bernd

[ant1393]

Looks to be the Linux version. Those files exist. No exe files.

Do you have the Vulkan ICD loader installed? (concrete package name varies between distros). What does vulkaninfo say?

I haven't done any installation outside of this:

sudo apt-get install libvulkan1 libvulkan1:i386
sudo apt-get install mesa-vulkan-drivers mesa-vulkan-drivers:i386

Here's my vulkaninfo - it doesn't look good.

$ vulkaninfo
==========
VULKANINFO
==========

Vulkan Instance Version: 1.1.82

ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32
/build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:3339: failed with VK_ERROR_INITIALIZATION_FAILED

guyz, does vulkan update concern AMD only or also nvidia 415 ?

got issue game pad mouse cursor wont show on map.

[radcapricorn]

guyz, does vulkan update concern AMD only or also nvidia 415 ?

got issue game pad mouse cursor wont show on map.

Quit it already, you've notified just about everybody about that issue
It's not drivers, it's the game. We'll have to wait for timon37 to figure this one out.

[jonnyfahrenheit]

Hi all, It's my first post on an Egosoft forum so be gentle

I will no doubt have other posts to make but so far this is one that has not been mentioned so far in this thread (unless I am in need of spectacles!).
The issue is that the info panel for targeted ships and people on docks is partially obscured and the only way to see it all is by doing a mouse look. Is this by design? I have included a screenshot on this post. I'm guessing that a saved game is not needed but am happy to provide if needed. The resolution I play in is 1280x1024, maybe this is why I am experiencing this issue. It would be nice to be able to scale the info panel too - if it is all shown in that res, it would take even more space up on the screen.

Screenshot here:https://www.dropbox.com/s/6wzyjya4luo3y ... 1.jpg?dl=0

Performance is pretty good, loved the series since X3:R - played them all to death!

kernel:4.20.11-100.fc28.x86_64
OS:fedora 28
GPU:nvidia gtx980ti
nvidia driver:418.43
CPU:i7-6700K CPU @ 4.00GHz

Thanks in advance for your time...

Jonny

[mflayer]

Also chdir to the X4 Steam installation directory and try

Code: Select all

ldd -d X4 | grep -e vulkan

Output should look like

Code: Select all

libvulkan.so.1 => /usr/lib/x86_64-linux-gnu/libvulkan.so.1 (0x00007f48c3a33000)

And /usr/lib/x86_64-linux-gnu/libvulcan.so.1 should exist.

I 'm having the same problem (failed to get phys. device count). Did all the steps so far (removed the 32 bit libraries, etc.), still no luck.

ldd output:

Code: Select all

libvulkan.so.1 => /usr/lib/libvulkan.so.1 (0x00007f05d599e000)

/usr/lib/libvulkan.so.1 exists and links to /usr/lib/libvulkan.so.1.1.99

Distro: Manjaro/KDE
2 monitors on Radeon R9 280

PS: thanks for actually supporting linux, you guys are the best <3

[ant1393]

guyz, does vulkan update concern AMD only or also nvidia 415 ?

got issue game pad mouse cursor wont show on map.

Quit it already, you've notified just about everybody about that issue
It's not drivers, it's the game. We'll have to wait for timon37 to figure this one out.

BUT if that was a vulkan issue i'll have updated too...

[hakzsam]

Can you reproduce the GPU hang with 'export RADV_DEBUG=nodcc' ?
On my side, this seems to "fix" the startup hang.

[Phipsz]

Also chdir to the X4 Steam installation directory and try

Code: Select all

ldd -d X4 | grep -e vulkan

Output should look like

Code: Select all

libvulkan.so.1 => /usr/lib/x86_64-linux-gnu/libvulkan.so.1 (0x00007f48c3a33000)

And /usr/lib/x86_64-linux-gnu/libvulcan.so.1 should exist.

I 'm having the same problem (failed to get phys. device count). Did all the steps so far (removed the 32 bit libraries, etc.), still no luck.

ldd output:

Code: Select all

libvulkan.so.1 => /usr/lib/libvulkan.so.1 (0x00007f05d599e000)

/usr/lib/libvulkan.so.1 exists and links to /usr/lib/libvulkan.so.1.1.99

Distro: Manjaro/KDE
2 monitors on Radeon R9 280

PS: thanks for actually supporting linux, you guys are the best <3

A quick search for your GPU came up with this: https://forums.linuxmint.com/viewtopic.php?t=272283 , saying your GPU does support vulkan, but amd is too lazy to fix a bug that prevents usage of the respective driver on linux. may that be the cause? But since you are using manjaro, maybe the Arch wiki can help you here? https://wiki.archlinux.org/index.php/AMDGPU

[VinnieVersa]

First of all thanks egosoft for bringing the game to linux, and to everyone helping with the vega issues.

Can you reproduce the GPU hang with 'export RADV_DEBUG=nodcc' ?
On my side, this seems to "fix" the startup hang.

So I am not the person who you were asking but I was having the same problem with my vega64. I played 5 hours yesterday with the AMDVLK driver and that seemed to be fine. Now I have just seen your post and tried it out (only for 5 mins so far) and indeed the startup hang was fixed for me using 'export RADV_DEBUG=nodcc' , so thank you .

As for my setup, I am running manjaro:

Code: Select all

Linux Wrex 4.20.10-1-MANJARO #1 SMP PREEMPT Fri Feb 15 21:46:13 UTC 2019 x86_64 GNU/Linux

Code: Select all

==========
VULKANINFO
==========

Vulkan Instance Version: 1.1.99
...
Presentable Surfaces:
=====================
GPU id       : 0 (AMD RADV VEGA10 (LLVM 7.0.1))
Surface type : VK_KHR_xcb_surface

Code: Select all

Libraries
core/linux420 4.20.10-1
extra/mesa 18.3.3-2
extra/vulkan-radeon 18.3.3-2
extra/llvm-libs 7.0.1-2

[andrewpc]

I think this is aimed at me among others. I can tell you that it indeed stops the crash. Now the question is why?

Thanks for responding and working out a workaround.

Can you reproduce the GPU hang with 'export RADV_DEBUG=nodcc' ?
On my side, this seems to "fix" the startup hang.