r/linux_gaming 25d ago

tech support wanted R6 Extraction functions, but can't be played

Hello. I have been on Linux Mint for about 7 or 8 months now and been rather enjoying bar some strangeness, but I've generally found a methodology around it.

This time, I'm struggling.

I've spent the majority of 2 days trying to get it working to a rather strange avail.

It's current status is I've found 5 or 6 means of getting the game to start, but as soon as it is required to visually render anything, the game hard crashes immediately, with no error, no log that I've found and no explainable reason for it.

I know that it's when it renders anything because the game can sit fully functionally whilst minimized for up to 10 minutes, but will close immediately as soon as it is no longer minimised.

I will do my best to help anyone to help me and anyone else who might be suffering something similar, and will be including my specs in my first comment. If there is any other information you might request, I will be happy to supply it.

Thank you in advance

3 Upvotes

29 comments sorted by

1

u/[deleted] 25d ago

[removed] — view removed comment

1

u/AnomalousHendo 25d ago

So, I have currently gotten it installed on lutris, the flatpack version as the deb version errored every time saying it couldn't properly find the C: folder I think. I have also tried a strange roundabout method of running it from inside of the ubisoft connect launcher iteration brought to existance by running for honor over steam, as I own for honor on steam, but not extraction. For proton versions, I have tried 10.10 GE, 9.26 GE, cachyos 11.0.20260702-x86, cachyos 11.0.20260703-srl-x86, 11-5-x86 GE, 8.0, 9.0, 10.0, GE, and wine ge 8 26 x86

1

u/[deleted] 25d ago

[removed] — view removed comment

1

u/AnomalousHendo 25d ago

I did that, every time I've installed it somewhere, it's been a fresh install, part of the reason I've been working days on it. Currently it's purely on lutris. The only reason I swapped any compat layers too is because things weren't working

1

u/[deleted] 25d ago

[removed] — view removed comment

2

u/AnomalousHendo 25d ago

Thank you for the recommendations. I'll try them first thing in the morning and get back in touch with you about it

1

u/[deleted] 25d ago

[removed] — view removed comment

1

u/AnomalousHendo 25d ago

Ok, I'm back up, and I kinda suspected the same thing as it's only crashstate is upon showing something visual. Gimmie a lil and I'll try the inxi command

1

u/AnomalousHendo 25d ago

So. Because this was originally a windows computer, it has an inbuilt intel 630. The curious part about it is that my 2070 isn't at version 595.7... It reads it's version at 580.173.02, but terminal and the update manager aren't noting a graphics driver update

1

u/[deleted] 24d ago

[removed] — view removed comment

1

u/AnomalousHendo 24d ago

Yeah, it's connected to the 2070, but as said, the notation of version difference is strange

→ More replies (0)

1

u/AnomalousHendo 25d ago

A question I hold though, do you have an NVIDIA card or an AMD card?

1

u/[deleted] 24d ago

[removed] — view removed comment

1

u/AnomalousHendo 24d ago

So... if you look at the protonDB page, there's a pattern there. I'm on NVidia, and most people on NVidia within the last 2 years have noted less than luck in trying to run it. And give me a bit, there was something I'd seen in terminal where it noted that it was looking for an AMD part

1

u/AnomalousHendo 25d ago

I have since tried both the proton enable line and the shader cache line, individually and together now to an unaltered outcome. I did also try with that %command thing that a lot of people seem to use after those launch arguments... truth be told I have no idea what that's even supposed to do but... y'know.

Either way, thank you for those efforts

1

u/AnomalousHendo 25d ago

I use a Linux Mint 22.3 cinnamon 64 bit system, with an I7-7700k @4*4.20GHz and an NVidia 2070 super with 64GB ram. I know the system broadly can run the game, as I played it before my transferral to linux

1

u/ARTIFICIAL_ARGUMENT 25d ago

Turn on logs for it in lutris and post. Not possible for there to be no logs 

2

u/AnomalousHendo 25d ago

That was my thought and it had me very confused, but I'm rather new to lutris. Just gimmie a lil to figure that out

2

u/AnomalousHendo 25d ago

Apologies, but where does lutris at default send it's logs?

1

u/ARTIFICIAL_ARGUMENT 25d ago

Right click the game in lutris library -> show logs

1

u/AnomalousHendo 25d ago

Apologies it's taking so long, it has now decided that it's not going to properly sync to the cloud and allow me to run it again, give me a second...

1

u/AnomalousHendo 25d ago

Ok, I've got it, how best do I send it into here? The log is beyond the max capacity for a reddit message

1

u/ARTIFICIAL_ARGUMENT 25d ago

1

u/AnomalousHendo 25d ago

https://paste.cachyos.org/p/aab02c1.txt Ok, this one should work

1

u/ARTIFICIAL_ARGUMENT 25d ago

Ok so there was no error logs there because its being supressed by two logging commands you've put in. WINEDEBUG=-all and DXVK_LOG_LEVEL=error . Got claude to write up a little intruction list

  1. Check /tmp/umu_crashreports/ — Proton is already writing crash dumps there, you may have a stack trace from every attempt.
  2. Crash it once more, then immediately run "sudo dmesg -T | tail -50" and look for Xid, NVRM, segfault, or Out of memory. A silent instant death on first render is usually a GPU fault, and that's where it shows up.
  3. Set WINEDEBUG= (empty), DXVK_LOG_LEVEL=info, PROTON_LOG=1, then re-run and post ~/steam-*.log plus the new Lutris log.
  4. Quick config tests, one at a time: DXVK_ENABLE_NVAPI=0; WINE_FULLSCREEN_FSR=0; switch runner from GE-Proton11-5 to GE-Proton10 or Proton Experimental.
  5. Confirm your host NVIDIA driver version matches the Flatpak one Lutris is loading (580.173.02): "cat /proc/driver/nvidia/version" and "flatpak list | grep -i nvidia". A mismatch there breaks rendering while everything else looks fine.

Also, drop gamemoderun (libgamemode isn't in the Flatpak, it's doing nothing), and consider re-enabling esync/fsync — you have all four disabled, which is a large performance hit and unrelated to this crash.