Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

Hey! Thank you very much for making a game for Linux - few people would go for it. But I ran into a problem. The game does not start, in the terminal it gives such an error

For some reason, it is not indicated anywhere that the game requires OpenVR, and I have Vulkan support, if needed

P.S.: I forgot to say that I tried to run the game on the laptop's discrete graphics card, but that didn't help either


(+2)

Hi! Thanks for reporting the issue. From what I already know this is kind of a rare case. Right now I'm trying to reproduce the issue to figure out the reason. Regarding OpenVR, this is just a warning, no need to worry about it. It will be removed in the next patch.

I'll be back as soon as possible! 

Could you please tell me your OpenGL version? You can use the following command and tell me what is the output: 

glxinfo | grep version

You may need to install mesa-utils package in order to do this:

apt install mesa-utils

Also, if you have Vulkan support, the output of the following would be really helpful

vulkaninfo | grep Version

Hello!

I have the same problem:

$ ./UkrainianFarmy.sh  
4.27.0-0+++UE4+Release-4.27 522 0 
Disabling core dumps.
Looking for binary: ../../../UATractorSimulator/Config/BinaryConfig.ini
Unable to read VR Path Registry from /home/alexanderep/.config/openvr/openvrpaths.vrpath
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
X Error of failed request:  BadMatch (invalid parameter attributes)  Major opcode of failed request:  149 ()  Minor opcode of failed request:  4  Serial number of failed request:  302  Current serial number in output stream:  312
libc++abi: terminating with uncaught exception of type std::__1::system_error: mutex lock failed: Invalid argument
Signal 6 caught.
Segmentation fault (core dumped)
$ uname -a 
Linux *** 5.13.0-37-generic #42~20.04.1-Ubuntu SMP Tue Mar 15 15:44:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

$ glxinfo | grep version 
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
OpenGL core profile version string: 4.6.0 NVIDIA 510.39.01
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL version string: 4.6.0 NVIDIA 510.39.01
OpenGL shading language version string: 4.60 NVIDIA
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 510.39.01
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20    GL_EXT_shader_group_vote, GL_EXT_shader_implicit_conversions,
$ vulkaninfo | grep Version 
WARNING: [Loader Message] Code 0 : loader_icd_scan: Can not find 'ICD' object in ICD JSON file /usr/share/vulkan/icd.d/nvidia_layers.json.  Skipping ICD JSON
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32
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_lvp.so: wrong ELF class: ELFCLASS32
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
WARNING: lavapipe is not a conformant vulkan implementation, testing use only.
Vulkan Instance Version: 1.2.131
WARNING: lavapipe is not a conformant vulkan implementation, testing use only.         apiVersion     = 4202678 (1.2.182)         driverVersion  = 88088582 (0x5402006)         conformanceVersion = 1.2.0.0         conformanceVersion  = 1.2.0.0         apiVersion     = 4198582 (1.1.182)         driverVersion  = 1 (0x0001)         conformanceVersion = 1.0.0.0         apiVersion     = 4202690 (1.2.194)         driverVersion  = 2139734080 (0x7f89c040)         conformanceVersion = 1.2.8.0         conformanceVersion = 1.2.8.0
(1 edit) (+1)

Hi again,

Found a solution
Need to export or use  VK_ICD_FILENAMES correct for my card drivers

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json ./UkrainianFarmy.sh

Hi! That's great you've figured it out! Thank you for sharing,  I'll update known issues with your solution

Hello!

Thank you for the tip, but, unfortunately, it did not help =((

On my Debian the package nvidia-vulkan-icd  was missing. Now it runs.

I like the idea that you only have to care for the time. Makes it easy to play. 👍

glxinfo:

server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
OpenGL core profile version string: 4.6.0 NVIDIA 470.103.01
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL version string: 4.6.0 NVIDIA 470.103.01
OpenGL shading language version string: 4.60 NVIDIA
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 470.103.01
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20    GL_EXT_shader_implicit_conversions, GL_EXT_shader_integer_mix,

vulkaninfo:

MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoi

d=0
WARNING: lavapipe is not a conformant vulkan implementation, testing use only.
Vulkan Instance Version: 1.2.182        apiVersion     = 4202671 (1.2.175)        driverVersion  = 1973010496 (0x7599c040)        conformanceVersion = 1.2.6.0        conformanceVersion                                   = 1.2.6.0        apiVersion     = 4194306 (1.0.2)        driverVersion  = 1 (0x0001)        conformanceVersion = 1.0.0.0

There is one strange thing I can see here. From the glxinfo output, I can assume you have an Nvidia card. But those MESA-INTEL logs make me think that the game itself is running on the Intel video card.

Could this be the case?

To run on an Nvidia graphics card, I use the variables __NV_PRIME_RENDER_OFFLOAD=1 and __NV_PRIME_RENDER_OFFLOAD=1 - this is how I ran glxinfo to display information specifically about the Nvidia graphics card. With these variables, all games on Steam also work for me. However, your game refuses to run on both the Intel video core and the discrete Nvidia video card =(

In both cases, the launch of the game freezes with the message "Unable to read VR path registry"

Okay, I got it. Regarding the VR log, this is just a warning present due to a packaging mistake.

Unfortunately, I do not have a solution for this concrete case. I can say that all the reported issues with Linux were related to the video driver in one way or another. I will do more research about this case. 

Once again, sorry for the inconvenience

Доброго дня.

Зараз я пишу статтю для Polygon про українські ігри, що з'явилися під час війни, й ходів би отримати коротенький коментар з приводу Ukrainian fArmy. Можна якось поспілкуватися? Поштою наприклад. Телеграм, щось ще.

(1 edit) (+1)

I understand you very well =)
Thank you!

Thanks for the effort, I really appreciate it. Don't worry. If you cant get it fixed, it's not a problem.