Linux Support

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

[_JD_]

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

Confirmed, same Joystick and same issue. Fixed on the beta branch: viewtopic.php?f=192&t=405397

PS
I'm developing a GUI to control the LEDs and MFD of the X52, if someone here is interested in helping with some test, get in touch with me:

[Kernel Panic]

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.

This got my Logitech Extreme 3D Pro working as well. Thanks @Erlindur.



After playing way to much in the last few days I wanted to leave some feedback and give another bug report. First off, I am getting a huge variation in my frame rate depending on where I am and what I am doing. If I am sitting on a busy docking platform with some combat close I get about 15 FPS. If there is no combat but I am sitting on the same dock I get about 17-19 FPS. If I am flying through the middle a huge battle I get 15-25 FPS, if I am flying and fighting in a small battle (no more than 5 ships) I get 30-50 FPS, and if I am flying though empty space a the edge of the map I usually get 60-100 FPS. I have an Intel i7 4970, an EVGA RTX 2070, and 16 GB of RAM. While playing the game my CPU load average varies from 3.1 to 3.6.

My minor bug report:

When riding the highway around the main loop of the map, switch to long range scan mode. Start scanning buy holding down the button for about two seconds and releasing it. Repeat this as fast as possible as you ride through various sectors. You will notice that the scan pulse exhibits some very strange behavior by sometimes occurring many kilometers ahead of your position and by being aimed in somewhat random directions. Sometimes it will even be pointed back toward your ship. This allows some small exploits. You can find ships surrounded by mines very far away from the highway. This works even if the area they spawned in is unexplored (still in the fog of war) because the mines show up and give away the location. You can also use this at the start of a new game to discover the locations of stations so you don't have to spend so much time exploring each zone.

[Kernel Panic]

More feedback.

When assigning a mining ship to a station it will go flying off to some sector I have yet to explore and start mining. Perhaps the Pilot or the Station Manager have knowledge I lack concerning the mineral richness of the X Universe. It would be nice if they shared it with me directly via notifications and map updates instead and then asking if it was OK to start mining in an unexplored and possibly hostile sector.

When I get a notification that one of my freighters has been told to drop it's cargo I fly to it's location as fast as possible and normally I arrive as it is engaged in battle with a pirate light fighter. I join the battle and kill the pirate. Then the pirate faction notifies sector security that I was unauthorized to kill their ship and I get to take a hit to my reputation with the sector owners. I should be able to defend my fleet when it is under attack. I shouldn't have to suffer penalties for doing so. I have no alternatives other than loose both time and money to the pirates. Since neither my ships nor myself can call sector security to our aid I should be be given a bonus not a penalty for doing the job of sector security.

[Rastuasi]

Has anyone had any luck using Linuxtrack to get TrackIR going in X4? Works perfectly for me in games like X-Plane 11, but it's not being detected automatically by X4.

[Rastuasi]

Then the pirate faction notifies sector security that I was unauthorized to kill their ship and I get to take a hit to my reputation with the sector owners. I should be able to defend my fleet when it is under attack.

This is by design, as the pirates are actually flying under a non-pirate identifier. The resolution is get yourself the police license and police scanner, scan them, that drops their fake ID and exposes them as a real pirate. Once done, you can then shoot them out of existence, also as far as I am aware, this only applies to Scale Plate guys. The rest do not lose rep since it's only Scale Plate and Teladi that are buddies.. cause profitsss.

[Aron Derik]

My Ch combatstick and CH pro pedals are identified and calibrated in jstest-gtk, but steam and X4 only sees the combatstick, no pedals. Don't know if this is a problem with steam or x4.

[BerndHohmann]

Don't know if this is a problem with steam or x4.

Exit Steam, plug out both devices. Open a console session and type 'steam -console'. Wait until Steam is booted. Plug-In your devices, console should show something like this:

Code: Select all

Local Device Found
  type: 044f 0402
  path: sdl://0
  Product:      Thustmaster Joystick - HOTAS Warthog
  [...]
 
Local Device Found
  type: 044f 0404
  path: sdl://1
  Product:      Thrustmaster Throttle - HOTAS Warthog
  [...]
 

"Type" and "Path" must be different and both devices should be detected. If not, its a Steam problem. Check previous postings about Steam Controller settings.

Unfortunately X4 Linux beta cannot be started without Steam running to isolate such problems.

Bernd

[Aron Derik]

I quit steam, unplug CH stick and CH pedals, start Steam in console with 'steam -console', and plug them back in, nothing in console happens. I double check JSTEST and controllers are there after plug in and can calibrate. I cant understand why such a large gaming platform is having problems with controllers. I also started IL2 1946 that I know has multiple controller support, because its pretty much necessary in game, and I used the same controllers in there on windows without Steam, and IL2 only sees the stick, not the pedals. Seems like Steam would be better off not messing with controller input or mapping at all.

[Aron]

I figured out why my joystick wasn't being detected properly. It is due to Steam.

I had to go to Big Picture mode and add bindings to a generic controller for my joystick. Only after the bindings were set could I then see the additional buttons and axis of the joystick. It also isn't good since some of the bindings in Steam control the cursor in the game.

There should be a setting in the game to not use Steam's input and use the OS level input system to mitigate these things. I suspect that lots of people are playing with joysticks and not gamepads.

[Kernel Panic]

Had something really strange happen to me a few minutes ago. I had just teleported from a new ship into my main vessel (a Cerberus) and was in the map doing some station building and ship movement. I noticed that the map kept switching focus to the lower left corner and that I had lost control of of it's movement. I left the map and found that I was falling through the geometry of my ship into it's interior. When I land I would be teleported back to the bridge and start falling again. I couldn't control my movement at all. I went back to the map and selected a another ship to teleport to from the property menu. After I teleported back to my main ship it was somehow over 32000 km from the nearest jump gate.

So I do not get use my main ship for several hours as it flies back to know space. I have a save game I could send, but I don't have any place online to store a 25MB file.