Linux Support

[andrewpc]

I managed to get some extra logs for the lock up from the dmesg. The screen and keyboard attached to X is dead but the server is responding to SSH logins. Here is the error
Note that I have also update the vulkan and AMDGPU versions which brought along LLVM7.0.1

[ 3096.841674] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:158 vmid:2 pasid:32800, for process Main() pid 26321 thread Main() pid 26321)
[ 3096.841675] amdgpu 0000:03:00.0: in page starting at address 0x000000000174b000 from 27
[ 3096.841676] amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 3107.008511] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=114395, emitted seq=114397

What GPU and Kernel version do you have?

was in original post but here you go BTW openSUSE Tumbleweed updated to latest this morning to ensure it wasn't a version issue

Code: Select all

andrew@host:~> uname -a
Linux host 4.20.10-1-default #1 SMP PREEMPT Tue Feb 19 06:34:39 UTC 2019 (08d0345) x86_64 x86_64 x86_64 GNU/Linux

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

Vulkan Instance Version: 1.1.98
Devices         count = 2
                GPU id       : 0 (AMD RADV VEGA10 (LLVM 7.0.1))
                Layer-Device Extensions count = 0
                GPU id       : 1 (AMD RADV VEGA10 (LLVM 7.0.1))
                Layer-Device Extensions count = 0
...

Device Properties and Extensions :
==================================
GPU0
VkPhysicalDeviceProperties:
===========================
        apiVersion     = 0x401046  (1.1.70)
        driverVersion  = 75509764 (0x4803004)
        vendorID       = 0x1002
        deviceID       = 0x687f
        deviceType     = DISCRETE_GPU
        deviceName     = AMD RADV VEGA10 (LLVM 7.0.1)

[Xenon_Slayer]

Mission to nowhere?

I've taken a mission to deploy a satellite. The guidance pointed to an Inactive Jumpgate. A few minutes later, the mission completed on its own.

Save after taking the mission: https://dl.dropbox.com/s/75rbkxbtgcl49h ... 010.xml.gz

Fixed the mission pointing to the inactive Jump Gate. I can't say I had it complete on its own though.

Edit: Got the mission issue now. Looking into it.

[radcapricorn]

I'm getting weird flashes that I assume are related to a battle in progress in front of me. Gif here (composed of screenshots). They persist across reloading the game (even after exiting to desktop), but so far only in that spot (i.e. I've played ahead an haven't had a repeat so far). Huge white flash is even visible when looking the opposite way from that battle.

Save here (Reused the previous link as Xenon_Slayer is already on top of it).

GTX 980 Ti (driver 415.27, Vulkan 1.1.99).

Edit: Got the mission issue now. Looking into it.

Awesome!

[ant1393]

issues linux 2.0 :

- gamepad mouse emulation does not show cursor on map. (can't clicks..)

- sound of laser / weapons is very low / inaudible.

- map filters tabs does not show buttons sometimes.

i precise i have a formatted fresh installed system with only X4... look my config in signature, if you can fix the mouse emulated cursor not showed as fast as you released linux release it would be awesome !

(tested both xbox one pad + steam controller... no gamepad mouse emulated cursor)

actually the game/map is unplayable apart with mouse+keyboard which i don't use...

[Xenon_Slayer]

Edit: Got the mission issue now. Looking into it.

Awesome!

Fixed. Thanks for the save.

[sakuramboo]

Bought it last night and already have 4 hours of gameplay in. There are two main bugs that I face.

1) Performance when docked is pretty bad. When in space, i will be anywhere between 60-100 FPS with ultra graphics settings, FXAA, and on an nvidia 1080. When docked, it will be around 30 FPS. Still playable, but that's a huge difference in performance.

and 2) when opening up a menu, move the mouse and escape out of the menu and the camera will be in a completely different direction. My initial thought is that when the menu is open, the camera stops moving but the cursor still has control of the camera.

Otherwise, there is some lighting issue with backgrounds like in one sector (i forget which one), the planet has rings and a shadow is cast on it which darkens the rings enough that you don't see them at all. And another minor bug is the autosaving takes a bit too long. When it autosaves, it takes about 10 seconds to complete.

Otherwise, no game breaking bugs so far, but like I said, I'm only 4 hours in.

[Brianetta]

It seems that the Linux beta doesn't sign saved games as valid, and so it isn't really possible to test ventures.

[radcapricorn]

1) Performance when docked is pretty bad. When in space, i will be anywhere between 60-100 FPS with ultra graphics settings, FXAA, and on an nvidia 1080. When docked, it will be around 30 FPS. Still playable, but that's a huge difference in performance.

I can attest to that as well, although IIRC Windows players experience the same.

and 2) when opening up a menu, move the mouse and escape out of the menu and the camera will be in a completely different direction. My initial thought is that when the menu is open, the camera stops moving but the cursor still has control of the camera.

Yep. And also sometimes after saving the game while on platform, the steering cursor appears, and the character follows it as if it was a ship. And it stops at screen edges, so you can't even turn around :-\ It disappears after a while though.

Otherwise, there is some lighting issue with backgrounds like in one sector (i forget which one), the planet has rings and a shadow is cast on it which darkens the rings enough that you don't see them at all.

That's not a bug, that's how it's supposed to look. The whole reason you can "see" rings is because they scatter light. Shadow -> no light -> no rings.

[Toidiboy]

Haven't played much at all but can confirm that I cannnot rebind axis in game for my t flight HOTAS X. All digital inputs bind fine.

Edit: Disabled controller detection in steam game settings as per troubleshooting faq.
Went through bindings and deleted all axis binds, now detecting properly when trying to set them.

[radcapricorn]

Err... I've unlocked the achievement "Have to Start Somewhere: Build the first module of a station". I haven't built any modules. I only bought a ship for the Boron sacrifice.

[apcolvin]

A further update to this issue. I can rule out the OS version. I have just installed Ubuntu 18.04 as stated as the supported version and I get the same behaviour. X4 Foundation screen music a quick flash of a black outlined circle jut to the right and up of the centre and then lock up. Music still plays just the X session and keyboard mouse all locked up

So how do I get you additional information. BTW this happens if I run fullscreen or with -windowed

I managed to get some extra logs for the lock up from the dmesg. The screen and keyboard attached to X is dead but the server is responding to SSH logins. Here is the error
Note that I have also update the vulkan and AMDGPU versions which brought along LLVM7.0.1

What GPU and Kernel version do you have?

was in original post but here you go BTW openSUSE Tumbleweed updated to latest this morning to ensure it wasn't a version issue

Code: Select all

andrew@host:~> uname -a
Linux host 4.20.10-1-default #1 SMP PREEMPT Tue Feb 19 06:34:39 UTC 2019 (08d0345) x86_64 x86_64 x86_64 GNU/Linux

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

Vulkan Instance Version: 1.1.98
Devices         count = 2
                GPU id       : 0 (AMD RADV VEGA10 (LLVM 7.0.1))
                Layer-Device Extensions count = 0
                GPU id       : 1 (AMD RADV VEGA10 (LLVM 7.0.1))
                Layer-Device Extensions count = 0
...

Device Properties and Extensions :
==================================
GPU0
VkPhysicalDeviceProperties:
===========================
        apiVersion     = 0x401046  (1.1.70)
        driverVersion  = 75509764 (0x4803004)
        vendorID       = 0x1002
        deviceID       = 0x687f
        deviceType     = DISCRETE_GPU
        deviceName     = AMD RADV VEGA10 (LLVM 7.0.1)

[HBK]

I'm getting weird flashes that I assume are related to a battle in progress in front of me. Gif here (composed of screenshots). They persist across reloading the game (even after exiting to desktop), but so far only in that spot (i.e. I've played ahead an haven't had a repeat so far). Huge white flash is even visible when looking the opposite way from that battle.

I’ve seen very similar things happen on Windows (GTX 2070, latest drivers, Win10 up to date). In my game it seems to only happen in Scale Plate Green, and the flashes are red-ish (like bright white with red-shaded "borders"). I’ll provide a save if necessary, but that’s probably just a pure graphics issue unrelated to the specifics of a gameworld.

Edit: I first saw this bug happen during 2.0 beta, but it could have been caused by a Nvidia driver update ...

[lazy_banana]

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

Vulkan Instance Version: 1.1.98
Devices count = 2
GPU id : 0 (AMD RADV VEGA10 (LLVM 7.0.1))
Layer-Device Extensions count = 0
GPU id : 1 (AMD RADV VEGA10 (LLVM 7.0.1))
Layer-Device Extensions count = 0
...

Device Properties and Extensions :
==================================
GPU0
VkPhysicalDeviceProperties:
===========================
apiVersion = 0x401046 (1.1.70)
driverVersion = 75509764 (0x4803004)
vendorID = 0x1002
deviceID = 0x687f
deviceType = DISCRETE_GPU
deviceName = AMD RADV VEGA10 (LLVM 7.0.1)

Do you have multiple GPUs? Are you running the game on a desktop or a laptop?

[Cg089]

I'm having trouble figuring out the source of this bug since it locks up my system and I don't have a second computer set up right now. Nothing that seems relevant is appearing in my system logs, though I'm happy to upload them if you want. Steps to reproduce:

1. Launch X4 windowed.
2. Exit using the little red x in the top right corner of the screen. (You can start a game first, if you like, but it's not necessary to cause a crash).
3. Reboot your computer since your computer no longer responds to input.

Ubuntu 18.04 with Nvidia proprietary drivers version 415.
No getting to another TTY, no mouse movement, no keyboard, nothing. It sounds like it might related to apcolvin's issue, but I'm honestly not sure since I'm not positive what issue he was describing. But X server screen/keyboard lockup definitely fits the bill. Having done a fair bit of work with Linux, my best guess is that exiting out without using the menu option doesn't do cleanup (since it may use the default termination signal handler if another one is not provided), and thus the GPU is left stuck causing X to stop responding. But that's complete speculation.

DxDiag for my system which is below minimum specs in terms of VRAM, but I highly suspect that is not the source of the bug; if someone else could confirm, that'd be great.

Also, unrelated and minor question about the X Rebirth catalog tool. Any chance we could get a Linux binary for the XRebirth catalog tool? Obviously, if it's a significant amount of work, probably not worth doing, but I was wondering if it actually depended on Windows & Windows build tools or if we just had only seen a Windows executable distributed due to historical reasons.

Thanks guys, I really appreciate the Linux support! One less thing I need to use Windows for! And sorry CBJ, I'm sure you're getting sick of me.

[andrewpc]

Desktop - single Vega 64 graphics card - 32 GB Ram Lots of disks - moved it off of an SSD to a spinning disk just in case

Do you have multiple GPUs? Are you running the game on a desktop or a laptop?

[radcapricorn]

I was trying to see how different VSync options behaved. On my machine, I have available:
- Adaptive VSync
- VSync
- No VSync

(Triple Buffering VSync is grayed out)

Initially I was playing with "VSync" enabled, and the game indeed seems to flip on monitor sync, no tearing observed. Today before loading the game I switched it to "Adaptive VSync". This brought tearing and skips. So, without exiting the game I went to settings and switched back to "VSync", but the tearing remained.

[lazy_banana]

Desktop - single Vega 64 graphics card - 32 GB Ram Lots of disks - moved it off of an SSD to a spinning disk just in case

Starting the game works fine, it seems to do its thing... and then EVERYTHING simply hangs. Can't even access tty2. But the music keeps playing
I managed to get to the main menu ONCE, thought I could change the AA settings and whatnot before starting a new game and ended up with the same problem.

As mentioned in the main post, I already tried waiting for about 20 minutes in hope it comes back... but nope.

A more verbose log could help maybe? How would I obtain that? Or am I simply missing some dependency?

Have you guys tried both the open source (AMDGPU) and the proprietary (AMDGPU PRO) drivers? Also try having a look at this: https://wiki.archlinux.org/index.php/AMDGPU. Especially the troubleshooting and Xorg configuration sections. I never used AMD cards under Linux, I'm just trying to lend a hand, so please exercise caution when changing your system configuration.

[CBJ]

that is a step backwards

Not really. For practical reasons, beta versions for Windows are only available on GOG for people using the Galaxy client. Since there is no native Galaxy client for Linux, there is no easy way for us to deliver a Linux beta on that platform.

[tuxinvader]

Is there a way to remap joystick axis in the control settings?
The older games used to have Xn_config binary which allowed this, but X4 doesn't have that, and remapping with jstest doesn't seem to make any difference?

It would be good if you could select two Axis assignments and swap them.

I have an old ST290 PRO, and the X/Y axis are assigned for strafing, how can I reassign them for roll, pitch, yaw, etc?

Thanks

[tuxinvader]

Is there a way to remap joystick axis in the control settings?
The older games used to have Xn_config binary which allowed this, but X4 doesn't have that, and remapping with jstest doesn't seem to make any difference?

It would be good if you could select two Axis assignments and swap them.

I have an old ST290 PRO, and the X/Y axis are assigned for strafing, how can I reassign them for roll, pitch, yaw, etc?

Thanks

I edited the inputmap.xml manually and assigned the axis where I wanted them. They don't all show up in the control UI now though, but they do work