Rage (9200)

[LeJimster]

It appears all the major bugs for this game have now been fixed. I plan to play through the game before I recommend whitelisting it.

Old bugs:
Rage 32-bit suffers from Virtual Texture bug.
Rage 64-bit renders correctly, although needs workaround to enable audio * Audio fixed as of Proton 3.16-5
Mesa bug reports:
Hang/Freeze in menus *Fixed in latest mesa-git
MegaTexture corruption *Fixed in latest mesa-git as of 24/6/22

Steam log
My System Specs

32/64 video comparison showing the Virtual Texture (aka MegaTexture) problem.

Performance tweaks
From my own experimenting I found these Launch Options produce the smoothest overall framerate on my system (RX Vega 56/Ryzen 1700)
+r_swapInterval 1 +jobs_numThreads 2 +vt_maxPPF 64 +g_fov 90

It seems like higher cpu thread usage than 2 offers little benefit while causing the frame rate to dip and stutter in certain areas. I also chose to set the fov to 90 as 80 feels too low gaming at 1440p.

[tr37ion]

Arch Linux
Kernel 4.18.3
Proton 3.7
Nvidia GTX 1070 - nvidia-beta 396.54
KDE Plasma 5.13.4
KDE Framework 5.49.0
Qt 5.11.1
§ python --version = 3.7.0

Starting Rage (32Bit) the first time it took 2-3min until the game did start (Megatextures loading?)
I set all GFX settings to MAX and did try to start the campaign. The game crashed.

I started the game again (32Bit) and now everything seems to work perfectly(!). Playing the campaign for some minutes was fine.

Candidate for [Whitelist] ?

[vpelletier]

Played from start to just before "mutant bash tv" mission, including pyros cave & refinery. The only issue I had was sound becomming distorted (a lot of cracks and pops - maybe a sound buffer being written to while it is being read by hardware ?). Onset may take time, as sound is initially fine. Only tested the default launch option (so... 32bits I guess ? the other option being "64-bits with mods", not sure whether the difference is "64 bits", "mods", or both).

Distribution: Debian sid
Kernel: 4.17.17 (package 4.17.0-3-amd64)
Proton: 3.7-4
CPU: i7-6700
GPU: GTX 1060@6GB, driver 396.51-1 (from "experimental" package repository)
pulseaudio 12.0-1, sink alsa_output.pci-0000_01_00.1.hdmi-stereo (HDMI0 on nvidia card)

[HughPH]

I'm getting a hang when trying to load Hagar Caves, which comes after the first mission that requires loading a different area (so it's not just an area loading issue)

Update: Also hangs on loading the Wasted Garage

Update: Installed Mesa 18.2 and LLVM 7 and this issue has gone away

Update: Removed Mesa 18.2 (because I have an NVidia card), purged & reinstalled LLVM 7 and this issue came back. Reinstalled Mesa 18.2 and it didn't go away again.

[whizse]

Hangs in the menu every time for me. No crash no errors, if I'm fast enough I can load a game. In-game everything including the menu is fine. Esync on or off makes no difference.

@LeJimster I filed a bug about the texture artifacts, it seems to be radeonsi specific. There's a suggested workaround there too. Check if it works for you:
https://bugs.freedesktop.org/show_bug.cgi?id=107694

[HughPH]

After the most recent update RAGE was starting with a black screen. Deleting its compatdata folder meant it was reinitialised with a clean wineprefix, but now it complains about being out of memory and ultimately loses a significant proportion of its textures (making it fairly difficult to play...)

This does mean there may be issues with the upgrade from one Proton version to the next.

[HughPH]

Still unable to get into The Wasted Garage but this time I was able to enter Hagar Caves - although I may have done so earlier, so this could be somehow related to a mission event making a global change that affects the game.

[LeJimster]

UPDATE:
I've found a fix for missing sound in the 64-bit version.
Installing xact to the Rage prefix did the trick. I used this command:
WINEPREFIX=/your path to/Steam/SteamLibrary/steamapps/compatdata/9200/pfx winetricks xact
Played the 64-bit version for 2 or 3 hours tonight, no issues.

[tr37ion]

@LeJimster I can confirm installing xact fixes 64-Bit version audio.

While it seems that xact in general has issues with DTS Patch for Pulseaudio. Very choppy sound with my system.

[LeJimster]

@tr37ion seems like the broken audio is a much wider spread issue. #54

For me the sound isn't choppy but it does appear like some of the sounds get cut or stop playing for a second here or there. I notice it mostly on engine sounds. Maybe that effect is exaggerated on your setup.

There is mention or Xaudio2 being broken on 64bit prefixes, I'm unfamiliar with these projects so I can't say what the best fix is.

[LeJimster]

@HughPH I have been playing the 64-bit fine but then it hanged when loading The Wasted Garage. These issues were apparently fixed in the proprietary drivers long ago, but it seems the game is broken in mesa. I found a strange workaround to get the level to load however. Switch to windowed mode before entering The Wasted Garage and it loads fine.

[HughPH]

Thanks @LeJimster - I don't actually have Mesa, though (mine is an Nvidia card and I'm using the latest drivers) and I was playing the 32-bit version... But I will try it and see what happens.

[whizse]

@LeJimster are you sure it's Mesa issues? If you use native xaudio on 64bit you probably run into the same pointer problems with the xaudio dlls as mentioned in https://bugs.winehq.org/show_bug.cgi?id=38668

[lucifertdark]

using Winetricks/protontricks to set override for xaudio2_7 native, builtin is enough to get the sound back in 64bit. No crashes for me so far.

ps Installing xact is what's causing the crashes for most people, DON'T DO IT! ;)

update: looks like I spoke too soon, just after posting ^ I started up the 64bit game again & it crashed in under 5 minutes. The 32bit version is working just fine though.

[LeJimster]

@lucifertdark strange. I haven't experienced any crashing on the 64bit version. Although I only quickly tested the 32bit with the latest mesa-git.

What is your system specs? Hopefully its not another regression in mesa. I will try to test later tonight.

[lucifertdark]

@lucifertdark strange. I haven't experienced any crashing on the 64bit version. Although I only quickly tested the 32bit with the latest mesa-git.

What is your system specs? Hopefully its not another regression in mesa. I will try to test later tonight.

I should have added it earlier.. I'm an Nvidia user

https://gist.github.com/lucifertdark/584c14275612e8e3c4a8070d428d8a02

[LeJimster]

I've just played 15 mins on the 64bit, no crashes on my RX Vega. So maybe you broke your prefix, or there is a driver issue. Would be nice to see if another nvidia user could test and compare.

[ziabice]

Game crashes on start complaining about a failed shader compilation: Failed to compile render prog binkyuv from binkyuv.

Using Proton 3.7-6.

I'm using Mesa 18.2.1 with LLVM 6.0.1.

The same problem happens if I use 32-bit or 64-bit version of RAGE.

My Specs

steam-9200.log

[lucifertdark]

Game crashes on start complaining about a failed shader compilation: Failed to compile render prog binkyuv from binkyuv.

Using Proton 3.7-6.

I'm using Mesa 18.2.1 with LLVM 6.0.1.

The same problem happens if I use 32-bit or 64-bit version of RAGE.

My Specs

steam-9200.log

You need LLVM 7 or higher.

[LeJimster]

@ziabice you need mesa-git for Rage to work on mesa right now. (Should be fine from 18.3 release). Also updating LLVM is a good idea as it fixes crashing in other games.

[xDShot]

The game doesn't recognize my game controller, even when I enable it in game settings and configure it in Steam Big Picture for the game.

[ziabice]

@lucifertdark @LeJimster because Wolfenstein TNO works well with my current setup, I believed Rage had to work too, my bad! :/

[flibitijibibo]

@kisak-valve Requesting an XAudio2 label for this game...

[kwahoo2]

Rage 32-bit suffers from Virtual Texture bug.
Rage 64-bit renders correctly, although needs workaround to enable audio (see below)

Mesa bug reports:
Hang/Freeze in menus *Fixed in latest mesa-git
MegaTexture corruption

Steam log
My System Specs

32/64 video comparison showing the Virtual Texture (aka MegaTexture) problem.

I can confirm both issues. The megatexture bug is a regression - with initial release of SteamPlay Rage ran fine. My specs: https://gist.github.com/kwahoo2/41bf5ea9fe74de52269c6a349d3639cb

[oblitum]

Can this game run under Intel HD Graphics in Wine? I'm on a 7700K CPU alone, the game crashes on startup:

wine: Unhandled page fault on read access to 0x00000000 at address (nil) (thread 002a), starting debugger...

But I think this is relevant, since it tries to use cuda related stuff:

4307.491:0008:0009:trace:module:load_dll looking for L"cudart32_40_17.dll" in L"E:\\Steam\\steamapps\\common\\RAGE;C:\\Program Files (x86)\\Steam;C:\\windows\\system32;C:\\windows\\system;C:\\windows;.;C:\\windows\\system32;C:\\windows;C:\\windows\\system32\\wbem"
4307.491:0008:0009:trace:module:get_load_order looking for L"E:\\Steam\\steamapps\\common\\RAGE\\cudart32_40_17.dll"
4307.491:0008:0009:trace:module:get_load_order got hardcoded default for L"E:\\Steam\\steamapps\\common\\RAGE\\cudart32_40_17.dll"
4307.491:0008:0009:trace:module:load_builtin_dll Trying built-in L"E:\\Steam\\steamapps\\common\\RAGE\\cudart32_40_17.dll"
4307.491:0008:0009:warn:module:load_builtin_dll failed to load .so lib for builtin L"E:\\Steam\\steamapps\\common\\RAGE\\cudart32_40_17.dll": /mnt/seagate/Steam/steamapps/compatdata/9200/pfx/dosdevices/e:/Steam/steamapps/common/RAGE/cudart32_40_17.dll: invalid ELF header
4307.491:0008:0009:trace:module:load_builtin_dll Trying built-in L"cudart32_40_17.dll"
4307.491:0008:0009:warn:module:load_builtin_dll cannot open .so lib for builtin L"cudart32_40_17.dll": /mnt/seagate/Steam/steamapps/common/Proton 3.16/dist/lib/wine/cudart32_40_17.dll.so: cannot open shared object file: No such file or directory
4307.491:0008:0009:trace:module:load_native_dll Trying native dll L"E:\\Steam\\steamapps\\common\\RAGE\\cudart32_40_17.dll"
4307.492:0008:0009:trace:module:map_image mapped PE file at 0x330000-0x395000
4307.492:0008:0009:trace:module:map_image mapping section .text at 0x331000 off 400 size 41000 virt 40e4e flags 60000020
4307.492:0008:0009:trace:module:map_image mapping section .rdata at 0x372000 off 41400 size 12e00 virt 12cb2 flags 40000040
4307.492:0008:0009:trace:module:map_image clearing 0x384e00 - 0x385000
4307.492:0008:0009:trace:module:map_image mapping section .data at 0x385000 off 54200 size 1200 virt 237c flags c0000040
4307.492:0008:0009:trace:module:map_image clearing 0x386200 - 0x387000
4307.492:0008:0009:trace:module:map_image mapping section .rsrc at 0x388000 off 55400 size 6a00 virt 6838 flags 40000040
4307.492:0008:0009:trace:module:map_image clearing 0x38ea00 - 0x38f000
4307.492:0008:0009:trace:module:map_image mapping section .reloc at 0x38f000 off 5be00 size 6000 virt 5fc8 flags 42000040
4307.492:0008:0009:trace:module:perform_relocations relocating from 0x10000000-0x10065000 to 0x330000-0x395000
4307.492:0008:0009:warn:module:alloc_module disabling no-exec because of L"cudart32_40_17.dll"
4307.492:0008:0009:trace:module:set_security_cookie initializing security cookie 0x3851c0

There's just a cudart32_40_17.dll in the RAGE directory.

[LeJimster]

It shouldnt be cuda causing the crash as usually the game detects and disables GPU transcoding for non nvidia cards. I haven't tested it on Intel but if you use mesa, you might need latest mesa-git.

[allanpfreitas]

Hi @LeJimster thanks for your reply. Here what you requested https://gist.github.com/allanpfreitas/73e5b787491b20286cea2dc1841e037e

[LeJimster]

@allanpfreitas can you put your full log files on here as well? If they're not too huge you can just drag drop the file into comment. Rage uses a workaround on mesa, I'm wondering if their is an issue with it on Navi.

[allanpfreitas]

@LeJimster sorry but where can I find these logs?

[LeJimster]

@allanpfreitas
A few logs:
In the Launch Properties for Rage you can use
PROTON_LOG=1 %command%
It will give you a log file in your home directory called steam-9200.log
Also if you look in your SteamLibrary and navigate through steamapps/compatdata/9200/pfx/drive_c/users/steamuser/Saved Games/id Software/Rage/base/
you will find some Error logs.

[allanpfreitas]

@LeJimster https://gist.github.com/allanpfreitas/e5bb75df70a9c3509e76eb262642f54a

[LeJimster]

@LeJimster https://gist.github.com/allanpfreitas/e5bb75df70a9c3509e76eb262642f54a

@allanpfreitas Just looking closer at your system I can see elements of the AMDGPU-Pro driver. Maybe this is causing a conflict? I would remove the AMDGPU-Pro drivers and stick to the Mesa drivers.

https://linuxconfig.org/amd-radeon-ubuntu-20-04-driver-installation

[allanpfreitas]

Yay! Thanks @LeJimster now the game is running but I'm having some textures issues, any tip to solve this one ?

[LeJimster]

@allanpfreitas it's a well known issue as I mentioned in the first post.. The best way is to play the 64-bit version of the game for now. Others have mentioned using launch options +vt_maxPPF 128

[allanpfreitas]

Thanks @LeJimster running the 64bit version its works great.

[Shotweb]

Running the 64 bit version doesn't solve the corruption issue (like allan's screenshots) for me, neither does seemingly any launch/config options. Using AMD graphics.

[eukara]

Same problem on amdgpu as @allanpfreitas. Been trying this on and off since I got this ThinkCentre M75q 2nd Gen in January this year. Running on openSUSE Tumbleweed. I have all sorts of other problems with this type of GPU though. Like freezes in which "drm:amdgpu_cs_ioctl : Failed to initialize parser -125" is spammed into a TTY and my system is fully locked up - with only a force restart able to get me back into action. This happens in a lot of other demanding games too. No idea where to start.

https://gist.github.com/eukara/d1d95c2ac85e273989bfff1cc79516dc < My Steam Hardware report
https://bugzilla.kernel.org/show_bug.cgi?id=205089 Someone else having the exact same freezes as me. I'm wondering as to why amdgpu still suffers from this.

[kopr12]

My only problem with amdgpu is with this game, I wonder what's going on with this, I mean is the problem in Mesa or somewhere else, too bad, it's a great game.

[eukara]

Using Rage64 and +vt_maxPPF 128 also doesn't affect anything for me, the game still renders all virtual-texture pages are all over the place. The question obviously becomes whether this is a driver issue, or the game has a bug (and the Windows AMD drivers have a hack to work around this?)
Gotta get this game fixed in time for Steam Deck, which after all runs on AMD! :P

[zmike]

For anyone getting the crash on startup from binkyuv, this should be fixed in upcoming versions of mesa.

[croberts81]

Finally! Closed issue.
gitlab.freedesktop.org/mesa/mesa/-/issues/1326

[LeJimster]

Finally! Closed issue. gitlab.freedesktop.org/mesa/mesa/-/issues/1326

I need to test it to verify the fix as it's been awhile since I built mesa-git. Hopefully this does the trick though!
Update:
@croberts81 Yep, just built the latest mesa-git and it is fixed on both 32-bit and 64-bit versions of the game. No more corrupted tiles! =)

Big thanks to Timothy Arceri for putting this one finally to bed. Hopefully this title can be whitelisted now.

[eukara]

Thank you all for making this possible! This was my most anticipated game!

[kopr12]

Hmm, still broken textures in my case.
OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.1.3
Device: AMD Radeon Vega 3 Graphics (raven, LLVM 14.0.4, DRM 3.42, 5.15.41-gentoo) (0x15dd)

Tried both 32-bit and 64-bit with several Proton versions.

[LeJimster]

Hmm, still broken textures in my case. OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.1.3 Device: AMD Radeon Vega 3 Graphics (raven, LLVM 14.0.4, DRM 3.42, 5.15.41-gentoo) (0x15dd)

Tried both 32-bit and 64-bit with several Proton versions.

You need to build the latest mesa-git. It should appear as Mesa 22.2.0. There will probably be a stable version in the next few weeks.

[kopr12]

You need to build the latest mesa-git. It should appear as Mesa 22.2.0. There will probably be a stable version in the next few weeks.

Well I checked release notes for 22.1.3 and it mentioned [wine] RAGE: texture problems as bug fixed

Anyway, compiling now the latest meta-git and will report back.

[LeJimster]

You need to build the latest mesa-git. It should appear as Mesa 22.2.0. There will probably be a stable version in the next few weeks.

Well I checked release notes for 22.1.3 and it mentioned [wine] RAGE: texture problems as bug fixed

Anyway, compiling now the latest meta-git and will report back.

Right. I will see about testing 22.1.3 on my laptop tomorrow. Let us know if mesa-git works.

[kopr12]

Same thing with git version.
OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.2.0-devel (git-7bb62d9dd8)

Well I don't know what to say, I tried, maybe it's just me for some odd reason, but I seriously doubt that, I run flatpak version of Steam though, maybe it has something to do with it, but unlikely, since I don't experience problems with other games.

[LeJimster]

Same thing with git version. OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.2.0-devel (git-7bb62d9dd8)

Well I don't know what to say, I tried, maybe it's just me for some odd reason, but I seriously doubt that, I run flatpak version of Steam though, maybe it has something to do with it, but unlikely, since I don't experience problems with other games.

The fix works for me on my PC and laptop. I just tested it on my laptop against mesa-git as mesa 22.1.3 hasn't been added to Arch stable yet. I have a Vega 56 in my PC and the laptop is running a 5900HX with integrated Vega graphics.

Laptop:
OpenGL vendor string: AMD OpenGL renderer string: RENOIR (renoir, LLVM 14.0.6, DRM 3.46, 5.18.8-arch1-1) OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.2.0-devel (git-8ab1e9826d)

I have never run Steam as a flatpak so I cant comment on whether that would be causing issues. I always use Steam (runtime). I'm not really up on flatpaks but could it be that its using an old 00-mesa-defaults.conf for the flatpak and not applying the new workaround.....? the workaround requires force_gl_map_buffer_synchronized to be enabled.

        <application name="RAGE (64-bit)" executable="Rage64.exe">
            <option name="allow_glsl_builtin_variable_redeclaration" value="true" />
            <option name="force_gl_map_buffer_synchronized" value="true" />
        </application>

        <application name="RAGE (32-bit)" executable="Rage.exe">
            <option name="allow_glsl_builtin_variable_redeclaration" value="true" />
            <option name="force_gl_map_buffer_synchronized" value="true" />

Try adding force_gl_map_buffer_synchronized=true %command% to your launch options see if that helps?

[kopr12]

Yeah, that could be the problem, I've updated flatpak version of mesa to 22.1-branchpoint-3487-gb28efd80ebb , that's the latest one that's available I'm afraid for flatpak, and I think the fix came after that snapshot, so I'll just have to wait it out a little more. Glad that it's finally fixed though, there's time for me to play it :)

[LeJimster]

Can confirm the latest mesa stable does indeed fix the virtual texture bug.

OpenGL vendor string: AMD
OpenGL renderer string: AMD RENOIR (LLVM 14.0.6, DRM 3.46, 5.18.9-arch1-1)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.1.3

[kopr12]

Switched from flatpak version to regular native Steam and it works.
Had some issues with 5.1 sound speakers, but I had that with some other Proton games as well, the only Proton version where the sound is working fine is 4.11, but that's another issue I guess.

[uqs]

Can confirm that upgrading to mesa 22.1.7 fixed the texture glitches for me, no command line overrides required anymore. I still experienced sounds not playing or cutting out, and it might be that a combination of PROTON_NO_ESYNC=1 and +jobs_numThreads 2 has fixed this for me, but I need a bit more mileage with it still to see if dialogue sounds or car noises are cutting off.

32bit Steam version, with Proton 7 or something

OS: Arch Linux
KERNEL: 5.19.6-arch1-1
CPU: AMD Ryzen 5 5600X 6-Core
GPU: AMD Radeon RX 6800 (sienna_cichlid, LLVM 14.0.6, DRM 3.47, 5.19.6-arch1-1)
GPU DRIVER: 4.6 Mesa 22.1.7
RAM: 32 GB

[kopr12]

I solved my sound problems with PULSE_LATENCY_MSEC=60 %command%