Linux Support (Beta)

[BerndHohmann]

X52 Pro.

Thanks JD…

One of my customers had a X52 Pro and a Trustmaster Warthog available for testing, I took the Warthog because of my athritic hands.

Problem now: I don't find the keyword for the "R" key (increase power of longrange scan) in the menu and I foobar the "R" key too.

Another problem: left mouse button is "select target under cursor" but I didn't find it in the joystick menu (nor the normal config menu). How to select the target under cursor with joystick?

Sorry for dumb questions, I had no joystick for the last 20 years.

Bernd

[radcapricorn]

Problem now: I don't find the keyword for the "R" key (increase power of longrange scan) in the menu and I foobar the "R" key too.
Another problem: left mouse button is "select target under cursor" but I didn't find it in the joystick menu (nor the normal config menu). How to select the target under cursor with joystick?

1) Fire Secondary Weapon
2) Target Object (targets whatever's directly in front of you)

[Aron]

Aron have you tried loading one of the default binding sets, then deleting/reassigning the binds?, also make sure the gamepad mode (or whatever it's called) is set to off.

I have tried that just now and even though the bindings are set better, they are still unresponsive for rotation and many buttons. Something is broke with the input for the joystick and I have no idea what it is.

[BerndHohmann]

2) Target Object (targets whatever's directly in front of you)

Thanks for the quick help.

"Target Object" is somewhat different from LMB (Mouse can select farer objects), but beta than nothing.

To be honest: X4 isn't very joystick friendly because of its many "toggle" switches (press "X" for activation and again for deactivation) and the somewhat stupid config menu.

For example: the "look around" feature accepts 4 buttons to look around (ok) but a 5th to return to default view, you cannot assign a flip-swith for "toggle map view" and so on.

I guess I have to look for a good joystickmapper under linux....

Bernd

[BerndHohmann]

Something is broke with the input for the joystick and I have no idea what it is.

I played X4 a couple of hours with Thrustmaster "Warthog" and unfortunately I cannot confirm this.

Had some beginners trouble, but after deleting every joystick related stuff from the ingame configuration menus and build it from ground up, it works fine.

I'm starting jstest-gtk after x4 was launched to show the status of the joystick devices on my 2nd monitor - maybe you should start this tool and Alt+Tab to this to check wtf is going on.

Summary: remove all joystickstuff from config, rebuild everything and check with jstest-gtk.

Bernd

[Kernel Panic]

I am running the beta! Thanks, Egosoft, for listening to your customers and providing support for Linux.

A bug report:

My Logitech Extreme 3D Pro joystick is only partially functional. The throttle, the twist action of the stick, and two of the four buttons next to the hat switch do not work in game. If I run jstest-gtk everything works fine.

Code: Select all

$ lsb_release -a
No LSB modules are available.
Distributor ID:	LinuxMint
Description:	Linux Mint 19.1 Tessa
Release:	19.1
Codename:	tessa

$ lsusb
Bus 002 Device 002: ID 8087:8001 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 05dc:a838 Lexar Media, Inc. 
Bus 004 Device 002: ID 045b:0210 Hitachi, Ltd 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 046d:0a44 Logitech, Inc. Headset H390
Bus 003 Device 006: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 003 Device 005: ID 045e:076c Microsoft Corp. Comfort Mouse 4500
Bus 003 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 007: ID 046d:c215 Logitech, Inc. Extreme 3D Pro
Bus 003 Device 002: ID 045b:0209 Hitachi, Ltd 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

If you need more info please let me know.

[Erlindur]

I am running the beta! Thanks, Egosoft, for listening to your customers and providing support for Linux.

A bug report:

My Logitech Extreme 3D Pro joystick is only partially functional. The throttle, the twist action of the stick, and two of the four buttons next to the hat switch do not work in game. If I run jstest-gtk everything works fine.

Code: Select all

$ lsb_release -a
No LSB modules are available.
Distributor ID:	LinuxMint
Description:	Linux Mint 19.1 Tessa
Release:	19.1
Codename:	tessa

$ lsusb
Bus 002 Device 002: ID 8087:8001 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 05dc:a838 Lexar Media, Inc. 
Bus 004 Device 002: ID 045b:0210 Hitachi, Ltd 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 046d:0a44 Logitech, Inc. Headset H390
Bus 003 Device 006: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 003 Device 005: ID 045e:076c Microsoft Corp. Comfort Mouse 4500
Bus 003 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 007: ID 046d:c215 Logitech, Inc. Extreme 3D Pro
Bus 003 Device 002: ID 045b:0209 Hitachi, Ltd 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

If you need more info please let me know.

I have the same problem as well. Additionally, only the x-axis of the hat switch seems to register (and as buttons while jstest-gtk reports them as analog) and the functioning button numbering seems to be a little out of order.

[Neerti]

Hello. I've had lots of fun with X3 on Linux, and I was excited to hear that there's a Linux beta for X4. Unfortunately I appear to be running into the problem of GPU hanging that some other people here have ran into, where the splash screen loads, music plays, but I am unable to do anything but move my mouse. Keyboard input did not work so I could not control-alt-f3 to enter a virtual tty, and I was unable to recover my session, instead being left with music playing and the X4 splash screen. Logging into my system remotely over SSH still worked but the GPU hang seemed to make it not possible to do a clean reboot regardless if I kill X(org) or not. The magic SysReq REISUB key combo appeared to semi-work (music stopped after the I key, which iirc SIGKILLs every process) but I had to cycle power for the actual reboot.

Upon reading this thread, it seemed that I was not the only one having this issue. Unfortunately, the workarounds I found here do not appear to work or be feasible to do, so I'm writing this to hopefully find a solution that works.


Solutions I've tried:
Setting "RADV_TRACE=/home/neerti/debug_logs/x4_trace.log %command% RADV_DEBUG=syncshaders,vmfaults,allbos %command%" environmental variables in launch settings did not help.

Setting "VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/amd_icd64.json" %command%" environmental variable is not possible for me as I do not have that specific icd file. I did try setting it to radeon_icd.x86_64.json (I assume the RADV version?), however it did not appear to fix the issue. This might be due to lacking AMDVLK.

I tried to install AMDVLK to be able to go around RADV, however after installation with apt, vulkaninfo and vulkan-smoketest would segfault immediately. X4 would fail to start (but didn't lock up my system which might be considered a very slight improvement ). That icd file also did not show up upon installation. Reverting the installation made both vulkan commands work again. The core dump didn't yield anything helpful to me in gdb since (I think this is why) I didn't compile vulkan myself.

Googling the AMDVLK segfault lead me to a series of github comments, which implied needing new firmware and a 4.19+ kernel, while still on 4.15. Unfortunately when I tried to install such a kernel (4.19, 4.20, and 5.0), it lead to me booting into a black screen, and I imagine that sort of trouble is beyond the scope of this thread but reverting back to the old kernel was thankfully simple.

Tried setting "RADV_DEBUG=nodcc %command%" in launch settings, still the same hang. If that doesn't work, I'm not sure if the upcoming mesa workaround will fix it since I think that does the same thing. I'm not sure how to apply the patch and compile myself so I do not know for certain if it will not work or not.

I'm not sure what else to do besides perhaps moving to a rolling release distro like Arch (which seems rather excessive for one game, and isn't technically supported here), so I'm now throwing in the towel and posting here. I might've done something wrong so please let me know if I did. I'd appreciate any help I could get in being able to start X4.

System information. Sorry if its too verbose, was based on what others had posted.
My specs, from neofetch

Code: Select all

OS: Ubuntu 18.04.2 LTS x86_64
Kernel: 4.15.0-46-generic
Shell: bash 4.4.19
Resolution: 1920x1080 
DE: GNOME 3.28.3
WM: GNOME Shell
WM Theme: Ambiance
Theme: Ambiance [GTK2/3] 
Icons: ubuntu-mono-dark [GTK2/3]
Terminal: gnome-terminal
CPU: AMD FX-6120 (6) @ 3.500GHz
GPU: AMD ATI Radeon HD 7970/8970
Memory: 6455MiB / 17956MiB

GPU information from lspci -v

Code: Select all

06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] (prog-if 00 [VGA controller])
	Subsystem: XFX Pine Group Inc. Tahiti XTL [Radeon R9 280X]
	Flags: bus master, fast devsel, latency 0, IRQ 45, NUMA node 0
	Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Memory at fe800000 (64-bit, non-prefetchable) [size=256K]
	I/O ports at d000 [size=256]
	Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: amdgpu
	Kernel modules: radeon, amdgpu

lsmod | grep amdgpu results

Code: Select all

neerti@desktop:~$ lsmod | grep amdgpu
amdgpu               2703360  55
chash                  16384  1 amdgpu
ttm                   106496  2 amdgpu,radeon
drm_kms_helper        172032  2 amdgpu,radeon
drm                   401408  26 drm_kms_helper,amdgpu,radeon,ttm
i2c_algo_bit           16384  2 amdgpu,radeon

ldd results, proof of libvulkan.so.1 existance

Code: Select all

neerti@desktop:/mnt/LinuxHDD/neerti/SteamLibrary/steamapps/common/X4 Foundations$ ldd -d X4 | grep -e vulkan
	libvulkan.so.1 => /usr/lib/x86_64-linux-gnu/libvulkan.so.1 (0x00007f6b27a68000)
neerti@desktop:/mnt/LinuxHDD/neerti/SteamLibrary/steamapps/common/X4 Foundations$ ls /usr/lib/x86_64-linux-gnu/libvulkan.so.1
/usr/lib/x86_64-linux-gnu/libvulkan.so.1

Truncated vulkaninfo, as full output hits character limit and might not be useful.

Code: Select all

===========
VULKAN INFO
===========

Vulkan Instance Version: 1.1.70

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
WARNING: radv is not a conformant vulkan implementation, testing use only.


Instance Extensions:
====================
Instance Extensions	count = 16
	VK_KHR_device_group_creation        : extension revision  1
	VK_KHR_external_fence_capabilities  : extension revision  1
	VK_KHR_external_memory_capabilities : extension revision  1
	VK_KHR_external_semaphore_capabilities: extension revision  1
	VK_KHR_get_physical_device_properties2: extension revision  1
	VK_KHR_get_surface_capabilities2    : extension revision  1
	VK_KHR_surface                      : extension revision 25
	VK_KHR_wayland_surface              : extension revision  6
	VK_KHR_xcb_surface                  : extension revision  6
	VK_KHR_xlib_surface                 : extension revision  6
	VK_KHR_display                      : extension revision 23
	VK_EXT_acquire_xlib_display         : extension revision  1
	VK_EXT_debug_report                 : extension revision  8
	VK_EXT_direct_mode_display          : extension revision  1
	VK_EXT_display_surface_counter      : extension revision  1
	VK_EXT_debug_utils                  : extension revision  1
Layers: count = 5
=======
VK_LAYER_VALVE_steam_overlay_32 (Steam Overlay Layer) Vulkan version 1.1.73, layer version 1
	Layer Extensions	count = 0
	Devices 	count = 1
		GPU id       : 0 (AMD RADV TAHITI (LLVM 8.0.0))
		Layer-Device Extensions	count = 0

VK_LAYER_VALVE_steam_fossilize_32 (Steam Pipeline Caching Layer) Vulkan version 1.1.73, layer version 1
	Layer Extensions	count = 0
	Devices 	count = 1
		GPU id       : 0 (AMD RADV TAHITI (LLVM 8.0.0))
		Layer-Device Extensions	count = 0

VK_LAYER_VALVE_steam_overlay_64 (Steam Overlay Layer) Vulkan version 1.1.73, layer version 1
	Layer Extensions	count = 0
	Devices 	count = 1
		GPU id       : 0 (AMD RADV TAHITI (LLVM 8.0.0))
		Layer-Device Extensions	count = 0

VK_LAYER_VALVE_steam_fossilize_64 (Steam Pipeline Caching Layer) Vulkan version 1.1.73, layer version 1
	Layer Extensions	count = 0
	Devices 	count = 1
		GPU id       : 0 (AMD RADV TAHITI (LLVM 8.0.0))
		Layer-Device Extensions	count = 0

VK_LAYER_LUNARG_standard_validation (LunarG Standard Validation Layer) Vulkan version 1.0.70, layer version 1
	Layer Extensions	count = 0
	Devices 	count = 1
		GPU id       : 0 (AMD RADV TAHITI (LLVM 8.0.0))
		Layer-Device Extensions	count = 0

Presentable Surfaces:
=====================
GPU id       : 0 (AMD RADV TAHITI (LLVM 8.0.0))
Surface type : VK_KHR_xcb_surface
Formats:		count = 2
	B8G8R8A8_SRGB
	B8G8R8A8_UNORM
Present Modes:		count = 3
	IMMEDIATE_KHR
	MAILBOX_KHR
	FIFO_KHR

[hogy]

The issue I have with my joystick is that the axes don't control the ship until I press one of the buttons (which I think is mapped to next target or something). As soon as I e.g. go to the map screen to target something, it stops responding again until I press that button. It doesn't seem to be the joystick at fault, as the input bindings config screen allows axis selection by moving the axis. It makes the joystick unusable to play with really. Is it something stupid I'm doing wrong?

lsusb:

Code: Select all

Bus 002 Device 004: ID 046d:c213 Logitech, Inc. J-UH16 (Freedom 2.4 Cordless Joystick)

[BerndHohmann]

I have the same problem as well. Additionally, only the x-axis of the hat switch seems to register (and as buttons while jstest-gtk reports them as analog) and the functioning button numbering seems to be a little out of order.

Just to rule it out: Enter Steam "Big Picture Mode", go to "Settings" (the gear wheel in the upper right corner), click "Controller" - it should read "no controller detected" somewhere below.

Bernd

[Erlindur]

I have the same problem as well. Additionally, only the x-axis of the hat switch seems to register (and as buttons while jstest-gtk reports them as analog) and the functioning button numbering seems to be a little out of order.

Just to rule it out: Enter Steam "Big Picture Mode", go to "Settings" (the gear wheel in the upper right corner), click "Controller" - it should read "no controller detected" somewhere below.

Bernd

Actually it detects it as a generic gamepad. I plugged it in and out and it is surely the joystick. I don't seem to find an option to disable it though.

[BerndHohmann]

Actually it detects it as a generic gamepad. I plugged it in and out and it is surely the joystick. I don't seem to find an option to disable it though.

Oha! Quite possible Steam tries a Pseudo-Controller -> Joystick Emulation and everything is fubar.

No Idea to disable the controller emulation for X4 because I don't have a controller to test with it Could be under "Steam -> Settings -> Controller.

Bernd

[Erlindur]

Actually it detects it as a generic gamepad. I plugged it in and out and it is surely the joystick. I don't seem to find an option to disable it though.

Oha! Quite possible Steam tries a Pseudo-Controller -> Joystick Emulation and everything is fubar.

No Idea to disable the controller emulation for X4 because I don't have a controller to test with it Could be under "Steam -> Settings -> Controller.

Bernd

Maybe that's the case. One of the first things I did though, was to "force off" the controller in X4's steam settings. I cannot find any other option to disable this functionality anywhere else.

[Aron Derik]

My lock up on loading screen stopped. I got kernel 5.02 and new drivers. but now I get random crash in game, monitor blinks because no input after crash, backlight on kbd goes out, have to hard boot to reset, seems like xserver crash. maybe problems with mesa or vulkan driver.

[Erlindur]

Actually it detects it as a generic gamepad. I plugged it in and out and it is surely the joystick. I don't seem to find an option to disable it though.

Oha! Quite possible Steam tries a Pseudo-Controller -> Joystick Emulation and everything is fubar.

No Idea to disable the controller emulation for X4 because I don't have a controller to test with it Could be under "Steam -> Settings -> Controller.

Bernd

Maybe that's the case. One of the first things I did though, was to "force off" the controller in X4's steam settings. I cannot find any other option to disable this functionality anywhere else.

Actually the opposite could work as a workaround. I mapped the joystick axis to the generic gamepad (and yes, it supports and detects all axis), I saved it and forced the steam controller on.

After playing around a bit (like setting controller mod off in-game) it seems to work rather well. It needs some work configuring it but all 3 axis and the throttle seem to work just fine.

[_JD_]

In the hope to help some of the people having issues with their Logitech Force 3D Pro I would like to share my profile where all 4 axis, all 12 buttons and the POV work correctly: https://www.dropbox.com/s/j1ebsquz6gk3b ... 3.xml?dl=0

I'm using X4 2.20 Beta4 but the same Joystick worked fine also on 2.00.

This is how the Joystick is detected by Steam: https://imgur.com/a/3B9Wqk1

A short video demonstrating that the Joystick works fine: https://youtu.be/2NR8PT0Jxtg

System:

Code: Select all

Kernel: 4.18.0-16-generic x86_64 bits: 64 
Desktop: Gnome 3.30.2 
Distro: Ubuntu 18.10 (Cosmic Cuttlefish) 

[Erlindur]

In the hope to help some of the people having issues with their Logitech Force 3D Pro I would like to share my profile where all 4 axis, all 12 buttons and the POV work correctly: https://www.dropbox.com/s/j1ebsquz6gk3b ... 3.xml?dl=0

I'm using X4 2.20 Beta4 but the same Joystick worked fine also on 2.00.

This is how the Joystick is detected by Steam: https://imgur.com/a/3B9Wqk1

A short video demonstrating that the Joystick works fine: https://youtu.be/2NR8PT0Jxtg

System:

Code: Select all

Kernel: 4.18.0-16-generic x86_64 bits: 64 
Desktop: Gnome 3.30.2 
Distro: Ubuntu 18.10 (Cosmic Cuttlefish) 

Nice work. While I hope this is only a temporary workaround, some initial digging showed that maybe this is a more complex problem (involving a separate vendor API library) and we will not see a permanent solution soon.

Maybe someone could start a separate thread/guide to help other people with the same joystick (or family? I have extreme 3d pro, not force), one that clearly shows up in searches. It could help future users with the same problem.
I would volunteer but I'm really bad at that kind of stuff.

[BerndHohmann]

Actually the opposite could work as a workaround. I mapped the joystick axis to the generic gamepad (and yes, it supports and detects all axis), I saved it and forced the steam controller on.

After playing around a bit (like setting controller mod off in-game) it seems to work rather well. It needs some work configuring it but all 3 axis and the throttle seem to work just fine.

Bernd

[kayahr]

Hello,

anyone else here having problems with configuring the Joystick dead zone or a solution for not being able to configure it? I have a X52 Pro and basically it works in X4 but the dead zone is pretty large and it just makes absolutely no fun flying like this. In other games I usually set it below 5%. But in X4, no matter what value I set the Dead Zone slider to in the controller settings, it always feels like 25% which is ridiculously high and in my opinion unplayable.

I also tried calibrating the Joystick on the command line with jscal and when I test it with jstest then there is no dead zone.

Maybe this is a bug in X4 for Linux and the Dead Zone slider in the controller settings is not used at all and the game always uses the 25% default? At least it fells like it. When I set it to 100% I expect the Joystick to be no longer really working but it doesn't make a difference, no matter if I set it to 0, 50 or 100 percent...

[Toidiboy]

Kayahr opt in to the steam open beta (the password is in the forums somewhere). The deadzone is fixed in the 2.20 build.