Обновлено: 28.01.2023
ASSER HIT: ‘deviceCount >= && «No Vulkan capable device found»‘ | File: D:BuildAgentsbuildAgent_pcworkgit_checkout_per_agent_mainFledgeRendererrenderersrcvulkanFledgeRendererSystemVulkan.cpp’ | Line: ‘377’
- Mark as New
- Bookmark
- Subscribe
- Email to a Friend
EA_Kent
Would you mind sharing a DxDiag when you’ve got a chance? You can find more info on how to pull one up over at the EA Help website.
Once you have the text file please attach it to this thread. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Email to a Friend
July 2020 — last edited July 2020
Hey sorry for late response here is the dxdiag
i can also add tell you some of the trouble shooting i did on this just in case you need
- i uninstalled and reinstalled
- i moved it from a external hardrive to my actual laptop
- i ran the repair from the orgin client
- i tried some fixes i saw on the internet like adding a setting file to my folder i was having issues renaming my amdvlk64.dll file because i was having issues with system admin rights and didnt feel like digging any deeper on that solution
- i also tried updating my drivers and checking can you run it to make sure my device meets the minimum requirements which it seemed like it did
- Mark as New
- Bookmark
- Subscribe
- Email to a Friend
EA_Kent
I appreciate the details!
Your GPU supports Vulkan, so that shouldn’t be an issue. I’m wondering if the game is trying to use the integrated AMD graphics from your CPU rather than your NVIDIA GPU. Can you check something for me when you have a chance?
Open up the NVIDIA Control Panel and go to Manage 3D Settings . Under Global Settings you should see a drop down menu for Preferred Graphics Processor . It will most likely be set to Auto-select by default. Try changing this to your NVIDIA GPU and see if that helps at all.
Let me know how that goes when you have a chance. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Email to a Friend
hey that didnt work unfortunately does it matter if it is on my hard drive or external i did move it to my external after my trouble shooting didnt work
- Mark as New
- Bookmark
- Subscribe
- Email to a Friend
EA_Kent
I have seen some cases where having the game installed on a separate drive from the Origin client itself can cause some issues, but the error you’ve been seeing seems to be more driver-related.
Have you tried rolling back to a previous NVIDIA driver to see if that helps at all? It looks like the developers for The Surge 2 specifically mention that driver 436.48 or earlier should work. Let me know if you’re still running into the same errors afterward.
- Mark as New
- Bookmark
- Subscribe
- Email to a Friend
hey sorry for late response but it seems that rolling it back didnt help i also tried removing and re adding both drivers as well as running the driver once while the amd driver was closed it did seem to open but it didnt really display anything kind of like an invisible window that was full screen so i closed it but it didnt pop up with that error message. i dont know if its because of the fact that the driver was disabled but i tried running apex because i know i wouldnt be able to run any games with that driver disabled and it did still show an error message. i cant seem to replicate it though it doesnt seem to do anything if i try to run it with the driver disabled granted i did remove it and add it back so i dont know if that could have caused anything.
- Mark as New
- Bookmark
- Subscribe
- Email to a Friend
EA_Darko
July 2020 — last edited July 2020
Hey @nickross637 as someone who saw issues with getting The Surge 2 to launch there are a couple of things you can try.
I had a similar error pop up when launching No Man’s Sky on an MSI gaming laptop, I fixed the issue by running Display Driver Uninstaller (which is a third party program not affiliated or endorsed by EA so if you opt to use it you do so at you own risk) in safe mode and then doing a clean install of my GPU drivers.
You can also try playing around with your power plan in your settings to ensure that you are always using your dedicated GPU or if feeling tech-savvy enough you can enter your BIOS settings and disable the integrated card entirely.
With The Surge 2, you can see issues when running some background program running such as CCleaner Smart Cleaning or anything like those is disabled when running the game. For some reason these can cause issues with the game and result in some odd error messages.
If disabling those get the game working and you continue to see visual issue then can you try the following ensuring that you launch the game after each to see if it works:
- Run the game
- Open OPTIONS > VIDEO > DISPLAY.
- Set VSync to OFF.
- Set Frame Rate Limit to 60 FPS
- Run the game
- Open OPTIONS > VIDEO > GRAPHICS.
- Set Resolution Scale to 100%
- Run the game
- Open OPTIONS > VIDEO > GRAPHICS.
- Set Dynamic Resolution Mode to MODERATE or AGGRESSIVE
You also need to ensure that your DirectX and your VC++ are fully up to date, it’s no harm doing a clean install of both and then launching the game again to see if you see a difference.
10 дек. 2019 в 6:32
Error: failed to execute vulkan command — Possible fix
If you still have problems with game crashing once in a while with «failed to execute vulkan command.. » here is what what you can try:
1) go to C:WindowsSystem32 find vulkan-1.dll select it and copy (Ctrl+c)
2) go to game installation folder and open Bin subfolder . SteamLibrarysteamappscommonThe Surge 2bin
3) paste the vulkan-1.dll replacing the one that is already in the Bin
This fixed the constan crashed of the game for me, but there are some issues with gamma from time to time, nothing terrible.
9 ноя. 2019 в 6:05
I only recently launched the game,and for the beginning of me running around doing stuff in the first zone was fine for the first hour or 2,I entered the mall,so far so good.
entered the port,whent down the stairs killed a bunch of spider drones,walked up to a guy placing one,killed him,and after that point,started happening that error,I relaunch the game,reload the save,walk around the same area for a minute or 2 and it appears again.
the error is this.
[FLR] Error
ASSERT HIT: ‘result && ‘Failed to allocate GPU memory» I File: • DABuildAgentsbuildAgent_pcworkgitcheckoutper agent _main FledgeRendererrenderersrcvulkan FledgeRendererM emotyGpuMemoryManagerVulkan.cpp’ I Line: ‘306’
any information would be appericated,and I did try the beta branches,didnt help.
9 ноя. 2019 в 6:35
I noticed something,this error only occours,when switching to Very high settings.
even if trying to do custom and bumping up anything above high will cause an instant error.
specifically that error above,I dont mind playing on high,but I hope this issue will be resolved.
*note,this issue wasnt a thing on launch day,only recently,or to be exact,at the day of this post*
9 ноя. 2019 в 12:57
alright,this issue is now happening in high settings but only in certain areas
Following the following steps, could you provide your logs along with your dxdiag to us so that we can investigate your crashes ?
A. Enable the Game Logs (Fledge.log, fledge_foundation.log and FledgeRenderer.log files): 1. Open Windows Explorer or File Explorer from the taskbar. 2. Navigate to Documents > The Surge 2. 3. Right click on the settings.ini file > Edit. 4. Add the following lines: logging_enabled = true crashdump_level = Large 5. Run The Surge 2 and reproduce the bug. The game logs are stored in Documents > The Surge 2 > logs.
12 ноя. 2019 в 11:22
Following the following steps, could you provide your logs along with your dxdiag to us so that we can investigate your crashes ?
A. Enable the Game Logs (Fledge.log, fledge_foundation.log and FledgeRenderer.log files): 1. Open Windows Explorer or File Explorer from the taskbar. 2. Navigate to Documents > The Surge 2. 3. Right click on the settings.ini file > Edit. 4. Add the following lines: logging_enabled = true crashdump_level = Large 5. Run The Surge 2 and reproduce the bug. The game logs are stored in Documents > The Surge 2 > logs.
Thanks, the crash has been reported and is currently being investigated
One possible lead would be to enable the option «texture streaming» from the options if it’s not already the case. Enabling it will let the streaming system handle the memory.
You have a 1060 GTX 3GB and with 3GB it’s not recommended to have this option disabled.
If the option is already enabled, unfortunately it is recommeded to play on lower quality settings
13 ноя. 2019 в 11:50
One possible lead would be to enable the option «texture streaming» from the options if it’s not already the case. Enabling it will let the streaming system handle the memory.
You have a 1060 GTX 3GB and with 3GB it’s not recommended to have this option disabled.
If the option is already enabled, unfortunately it is recommeded to play on lower quality settings
that option was always enabled for me,so thats not the case,but Iv tested right now to run on your auto settings wich are suppose to lock settings to a managable to my GPUs state.
and after running around in the nixen port for a while,the same crash occours,in wich makes absolutely 0 sense how I could run the game on the same auto — high settings in the first zone,where it was completely fine while playing for an extended period of time,and suddenly entering a new zone the game suddenly decideds to give you a middle finger to the face for progression regardless of settings.
note I played trough the first zone before the vulkan patch and everything was fine,came back a few weeks later,finished up farming and mopping up the first zone,got into the mall,all seems to be fine,up next whent to the port,and literally after going trough the first bit of electric spiders,that pops up.
Im really at a loss here,is the GPU really the issue or is the newly implimented software/processing system within the game after that patch.
I would love to help,but this is literally all I can do to provide information.
Very high-instant crash
High-running trough certain areas or within a set period of time 5-10 minutes (crash)
Auto-same deal as with this option above ^
Unfortunately, if the option is already enabled I don’t have much other solutions to propose other than reducing the quality options. Only lowering the Texture quality should prove sufficient in that matters.
The changes made in the different patches should not impact this kind of issue this much so it’s weird you didn’t have them in the first place as you say.
Lowering texture quality and having the latests GPU drivers should help, if there are any improvements made in future patches I’ll let you know
15 ноя. 2019 в 3:21
Unfortunately, if the option is already enabled I don’t have much other solutions to propose other than reducing the quality options. Only lowering the Texture quality should prove sufficient in that matters.
The changes made in the different patches should not impact this kind of issue this much so it’s weird you didn’t have them in the first place as you say.
Lowering texture quality and having the latests GPU drivers should help, if there are any improvements made in future patches I’ll let you know
alright,thank you for the support,hope I will somehow resolve this issue.
16 ноя. 2019 в 1:25
Unfortunately, if the option is already enabled I don’t have much other solutions to propose other than reducing the quality options. Only lowering the Texture quality should prove sufficient in that matters.
The changes made in the different patches should not impact this kind of issue this much so it’s weird you didn’t have them in the first place as you say.
Lowering texture quality and having the latests GPU drivers should help, if there are any improvements made in future patches I’ll let you know
alright,thank you for the support,hope I will somehow resolve this issue.
Out of interest, you probably already tired all this, but did you try a steam verity check, and update drivers and or DDU and reinstall drivers ?
17 ноя. 2019 в 14:39
alright,thank you for the support,hope I will somehow resolve this issue.
Out of interest, you probably already tired all this, but did you try a steam verity check, and update drivers and or DDU and reinstall drivers ? yeah I pretty much tried every possible conventional method,and it makes no godam sense to how Iv run games at a much higher requierment than this one and none of them did a force crash just out of entering into speciffic game areas and it says (oh sorry GPU bad),I really wanna play trough the surge 2,loved the 1st one and was hyped over the 2nd.
really dont wanna offend the game Im siked for but the engine its running on is one genuine mess of bugs since day 1 :/
(some of them werent as bad,actually fixable by the posts made by the devs)
but the fact that its a full release title and contains functionality issues up to this day is astounding at this juncture.
Have no clue if its because they are using Vulkan or its because theres some internal conflict between drivers as they stated about GForce.
my drivers are up to date,did the most recent driver upgrade for literally everything,and everything is still the same as it is up to this day.
go into port nixon and walk trough the shock spider-Crash
/lower settings/
walk past the spiders and get to medbay-after 5 minutes,crash.
literally unplayable.
17 ноя. 2019 в 21:54
Out of interest, you probably already tired all this, but did you try a steam verity check, and update drivers and or DDU and reinstall drivers ?
yeah I pretty much tried every possible conventional method,and it makes no godam sense to how Iv run games at a much higher requierment than this one and none of them did a force crash just out of entering into speciffic game areas and it says (oh sorry GPU bad),I really wanna play trough the surge 2,loved the 1st one and was hyped over the 2nd.
really dont wanna offend the game Im siked for but the engine its running on is one genuine mess of bugs since day 1 :/
(some of them werent as bad,actually fixable by the posts made by the devs)
but the fact that its a full release title and contains functionality issues up to this day is astounding at this juncture.
Have no clue if its because they are using Vulkan or its because theres some internal conflict between drivers as they stated about GForce.
my drivers are up to date,did the most recent driver upgrade for literally everything,and everything is still the same as it is up to this day.
go into port nixon and walk trough the shock spider-Crash
/lower settings/
walk past the spiders and get to medbay-after 5 minutes,crash.
literally unplayable.
I think that unfortunately for most people that still can’t play S2 reliably — it’s down to vulkan 🙁 — VK doesn’t have the same spectrum of support as the other API’s yet, so yeah for a sizeable minority of people it’s the death of those games for them unfortunately.
Like for instance quite a few people were no longer able to play NMS when they switched to vulkan. There was a steam group (which got taken down. why ?) a while back that had like nine thousand people in it that all couldn’t play NMS anymore just because of vulkan 🙁 I know that VK is the future and all, but it’s just sad that right now, it’s ruining games.
10 сен в 13:57
Just bought this game for my PC and it downloaded OK but wont start. Here’s the error:
«Failed to execute Vulkan command ‘result’ (file ‘D:BuildAgentsbuildAgent_pcworkgit_checkout+mainFledgeRendererrenderersrcvulcanFledgeRendererSystemVulkan.cpp’ in line ‘376’), returned: ‘VK_ERROR_INITIALIZATION_FAILED’
There’s a good user friendly message, eh?
I have the same problem. The solutions alreadyt provided doesn’t work for me.
12 сен в 16:42
I bought this like 5 hours ago and have spent all 5 hours trying to fix the exact problem and I don’t know how, and no work arounds are working, is there any solution or should I just refund the game and get a different game?
13 сен в 6:36
I bought this like 5 hours ago and have spent all 5 hours trying to fix the exact problem and I don’t know how, and no work arounds are working, is there any solution or should I just refund the game and get a different game?
By your steam icon you already refunded.
What could have been tried before refunding was:
Checking your specs
Checking game files on Steam
Uninstalling game then deleting game folder before reinstall
Checking for anti-virus or other programs that could be a trouble
Checking windows and Steam
Checking your hardware (CPU, GPU, RAM, HD, PSU, MoBo)
Читайте также:
- Epic games ark survival evolved как установить
- Как установить шейдеры на гта сан андреас
- Ошибка warface unhandled exception
- Survarium ошибка battleye launcher
- Как убрать ограничение скорости в euro truck simulator 2
@ZereoX thanks for the fast answer! I have mesa 22.2.1 here. Double checked in package info and glxinfo -B:
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.42, 5.15.70-r1) (0x731f)
Version: 22.2.1
Accelerated: yes
Video memory: 8192MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
VBO free memory - total: 6745 MB, largest block: 6745 MB
VBO free aux. memory - total: 7631 MB, largest block: 7631 MB
Texture free memory - total: 6745 MB, largest block: 6745 MB
Texture free aux. memory - total: 7631 MB, largest block: 7631 MB
Renderbuffer free memory - total: 6745 MB, largest block: 6745 MB
Renderbuffer free aux. memory - total: 7631 MB, largest block: 7631 MB
Memory info (GL_NVX_gpu_memory_info):
Dedicated video memory: 8192 MB
Total available memory: 16368 MB
Currently available dedicated video memory: 6745 MB
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.42, 5.15.70-r1)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.2.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.2.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.2.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
Now I see that Steam shows mesa 20.3.4 in system info, which is weid. What else should I check?
Upd investigated a bit, this comes from installed 32 bit stuff (which I haven’t updated in ages) and can be found under architectures.i386-linux-gnu json key. architectures.x86_64-linux-gnu shows current 22.2.1 version correctly.
This game is 64 bit only I think, shouldn’t be an issue.
The Surge 2 (644830)
Compatibility Report
- Name of the game with compatibility issues: The Surge 2
- Steam AppID of the game: 644830
System Information
- GPU: AMD RX 5700
- Driver/LLVM version: Mesa 19.3.1
- Kernel version: 5.4
- Link to full system information report as Gist:
https://gist.github.com/Reifam/d91174379488044ec745dc51f7cfadaf - Proton version: 4.11.11
I confirm:
- that I haven’t found an existing compatibility report for this game.
- that I have checked whether there are updates for my system available.
steam-644830.log
steam-644830-ignore.log
Symptoms
When launching the game, it immediately crashes with the following message: «Failed to execute Vulkan command ‘result’ (file ‘D:BuildAgentsbuildAgent_pcworkgit_checkout_per_agent_branchFledgeRendererrenderersrcvulkanFledgeRendererSystemVulkan.cpp’ in line ‘353’), returned: VK_ERROR_INCOMPATIBLE_DRIVER’ «
This is what it looks like:
It presents this in a window with three options: Abort, Retry, and Ignore. Abort will just close the window and stop the game from running. Retry and Ignore both do the same thing. The game will technically be running, seeing as I can see the .exe running in top, but it doesn’t actually launch into a playable or viewable state (just a process running in the background). After a minute or two, that process ends and the game quits. Above, the first log is from an abort, and the second is from an Ignore.
Reproduction
Launch the game.
Hello @Reifam, the error message and log appears to be accurately telling you the game failed to initialize the vulkan driver. Assuming mesa/radv is otherwise healthy on the system, maybe the game bundled vulkan-1.dll (….local\share\Steam\steamapps\common\The Surge 2\bin\vulkan-1.dll) is interfering with the vulkan driver stack, similar to https://bugs.winehq.org/show_bug.cgi?id=47640#c2.
Hello, Kisak.
I see the issue about a bundled vulkan-1.dll In my The Surge 2/bin directory, I deleted the vulkan-1.dll that was there. However, the game crashed with the same error and the buttons have the same effects. The only copies of this dll in the .local tree are now in the common/Proton [version]/dist directories and in the compatdata directories. Any advice?
It works on Nvidia. I believe this needs to be fixed in Mesa.
Tbf ,that «it works on Nvidia» doesn’t certainly mean it is a Mesa issue imo.
Just like it happened with World War Z game ( non Steam , DX11 and VLK game ). Everybody said it is a Mesa issue since VLK works with NV at initial release builds and today VLK renderer of this WWZ game doesn’t even work with NV on Wine.
https://bugs.winehq.org/show_bug.cgi?id=47562
Update
Update on The Surge 2. Proton hit the big 5.0, which is great! I also ran a bunch of system updates recently so all my stuff is on different versions, so I figured I’d try it again. Unfortunately these updates and changes did not improve the ability to play the game
Mesa is now 20.0.0_rc1
Kernel is now 5.5.2 (-gentoo-r1)
Proton version is 5.0-1
Nothing has changed about my systems specifications/hardware
Here’s the new crash dump. Ran with just the PROTON_LOG and not the other stuff
steam-644830.log
@Reifam Are you still able to reproduce this crash with Mesa 20.0.X?
Hello, I have updated my Mesa and Kernel several times since last post, and The Surge 2 works much better now. Not exactly perfect, but I was actually able to play through the game from start to finish.
The issues I’ve noticed now are twofold. First, after playing for about an hour, the game’s framerate gets incredibly slow and choppy. Quitting the game and starting up again resolves that, but it’s weird that it happens. Also, I had about 2 major instances of the game just straight up resetting my computer. Everything would go black, and soon enough I would be back at GRUB. First was randomly in some area of the game, and second was whenever I’d try to start New Game + mode.
My current versions now:
Mesa 20.0.4-r1
Kernel 5.6.4 (-gentoo)
Proton 5.0-6
New dump. I’m not sure how the proton log works so this could either be my most recent forced hard reboot or the entire log from a full NG playthrough of The Surge 2:
steam-644830.log
Like I said, aside from these occurrences of hard reboots and slowdowns, the game is actually quite playable for me.
@Reifam I think the situation with Mesa 20.1 should be even better. Does it work fine now with RADV_PERFTEST=aco ?
Hello, I updated mesa to 20.1 and my kernel to 5.7.1. Unfortunately, the problems persist. When starting the NG+, I get screen freezes. This thankfully is not the entire computer rebooting, but it does require me to go into another TTY and kill X and restart it. Here’s my latest proton log.
steam-644830.log
I also figured I’d include a tail of what dmesg is saying.
dmesgsurge.txt
@Reifam Can you please attach the whole dmesg log next time? It looks like you got a GPU hang. What GPU is that?
Hi,
I’ve just tried to run The Surge 2 and while the game runs and the menus are shown, once the game load all graphics are rendered with black textures, the geometry seems to be working as I can see the silhouette of the protagonist if I move around and get a dialog behind the character. Other Indicators, health and hud elements work fine.
I was wondering if anyone has experienced this, I tried with LLVM and the result is the same.
I’m running: Ubuntu 18.04.x,
Proton version 5.13-4 and Experimental
Linux host 5.10.0-4.3-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 5.10-5ubuntu1~bionic (2021-01-01) x86_64 x86_64 x86_64 GNU/Linux
OpenGL renderer string: AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.40.0, 5.10.0-4.3-liquorix-amd64, LLVM 11.0.0)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.3.2 — kisak-mesa PPA
Vulkan Instance Version: 1.1.70
VK_LAYER_MESA_device_select (Linux device selection layer) Vulkan version 1.1.73, layer version 1
Device Properties and Extensions :
VkPhysicalDeviceProperties:
deviceID = 0x67df
deviceType = DISCRETE_GPU
deviceName = AMD RADV POLARIS10 (ACO)
@ZereoX I am no longer experiencing the crashing issues on the latest Mesa. The labels can be removed.
@ZereoX thanks for the fast answer! I have mesa 22.2.1 here. Double checked in package info and glxinfo -B:
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.42, 5.15.70-r1) (0x731f)
Version: 22.2.1
Accelerated: yes
Video memory: 8192MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
VBO free memory - total: 6745 MB, largest block: 6745 MB
VBO free aux. memory - total: 7631 MB, largest block: 7631 MB
Texture free memory - total: 6745 MB, largest block: 6745 MB
Texture free aux. memory - total: 7631 MB, largest block: 7631 MB
Renderbuffer free memory - total: 6745 MB, largest block: 6745 MB
Renderbuffer free aux. memory - total: 7631 MB, largest block: 7631 MB
Memory info (GL_NVX_gpu_memory_info):
Dedicated video memory: 8192 MB
Total available memory: 16368 MB
Currently available dedicated video memory: 6745 MB
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.42, 5.15.70-r1)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.2.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.2.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.2.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
Now I see that Steam shows mesa 20.3.4 in system info, which is weid. What else should I check?
Upd investigated a bit, this comes from installed 32 bit stuff (which I haven’t updated in ages) and can be found under architectures.i386-linux-gnu json key. architectures.x86_64-linux-gnu shows current 22.2.1 version correctly.
This game is 64 bit only I think, shouldn’t be an issue.
Worked fine on Deck and NixOS, except on the Deck, the fonts are all gibberish but it seems to be due to fonts not scaling down well… 🙁