
Diminuer le traitement de lissage a 4X
9.5/10

+com_skipIntroVideo 1 +cvaradd m_menu_sensitivity 0.20
Just make sure to add the launch options as noted and you should be good to go.

Worked out of the box and on top of that it ran way better than it ever has on Windows!

Works (update)
Idk if it's linux specific but my game would have a memory leak that forced me to restart after about 30-40 mins of gameplay. Lowest mouse sensitivity is way too high. Controller is supported but has a massive deadzone that can be resolved with Steam Input's anti-deadzone feature.
Works fine out of the box, just like on Windows.

WINEDLLOVERRIDES="dinput8=n,b" %command% +set com_allowconsole 1
I use id5 Tweaker to allow framerates above 60 (not necessary when using LCD Steam Deck). This works about 99% of the time. However, when battling vehicular enemies in the wasteland, the slow-motion effect that is used when the last enemy is killed will crash the game when the framerate is too high. The only way to work around this that I know of is to use the console to limit the framerate to 60 before you kill the last enemy, wait for the slow-motion effect to end, and then use the console to return the framerate limit to your prefered setting. The command you use is id5Tweaker_SetFpsLimit <your desired FPS>
The PCGamingWiki entry suggests you to change 3 CVar (vt_) entries. Do not change vt_uncompressedPhysicalImages
to 1
, as this will cause visual artifacts on all versions of Proton I tried. vt_pageImageSize
and vt_maxPPF
seem fine to change to any reasonable value as far as I can tell.
Setting com_allowconsole
to 1
via launch options is said to disable achivements, however, I seem to be getting them anyway. It is not necessary to use the console to modify id5 Tweaker, as you can use the config file provided with the mod. It is simply for convienence. Please use at your own risk if you care about achievements.

WINEDLLOVERRIDES="dinput8=n,b" %command% +set com_allowconsole 1
I use id5 Tweaker to allow framerates above 60 (not necessary when using LCD Steam Deck).
The PCGamingWiki entry suggests you to change 3 CVar (vt_) entries. Do not change vt_uncompressedPhysicalImages to 1, as this will cause visual artifacts on all versions of Proton I tried. vt_pageImageSize and vt_maxPPF seem fine to change to any reasonable value as far as I can tell.
On one occasion, my mouse cursor was not bound to the game window and would travel to my other monitor. This was fixed by closing and starting the game again.
Setting com_allowconsole to 1 via launch options is said to disable achivements, however, I seem to be getting them anyway. It is not necessary to use the console to modify id5 Tweaker, as you can use the config file provided with the mod. It is simply for convienence. Please use at your own risk if you care about achievements.

Game crashes after intro
This seems to be related to dynamic texture loading. At lower resolutions it takes longer to crash. At higher resolutions it crashes as soon as the video ends. Even at 640x480 it doesn't work long enough to get to the point where the player has control.

Works out the box
Did not try multiplayer

A dodgy PC port of a pretty fun game
Certain sounds are noticeably delayed during the car combat sections in the open world areas of the game. At one point, the entire audio completely gave out into silence but fixes itself again upon transitioning to a new area via loading screen. The more self contained hub areas and on-foot combat areas don't have these issues.
For most of my playthrough, all of my mouse inputs would "double click", which made certain menus completely unusable and thus forced me to keep a controller on hand to navigate them instead. However this double click issue seemed to disappear on my final session just before beating the game, so your mileage may vary.
Sometimes if you have controller enabled (which is absolutely necessary to have on hand, as some of the menus are a pain on mouse and keyboard), you will experience some really nasty performance problems every couple of seconds. Turning off the enable controller option and turning it back on solves the issue.
The issues I mentioned could very well be simply due to the PC version of Rage being quite poor in places and not related to playing via Proton itself. However, I still enjoyed my time revisiting this game nonetheless as it is still very playable on Linux.

No modifications needed
There are no cloud saves. Take that into consideration if you have this game on a different computer.

Wouldn't launch with Proton 8
7wt
Whatever update came out it fix rage plays out the box no problems artifacting is gone now.
Small text when playing on deck but not tv
Some fps drops on the wasteland
I think an common user should at this point (using Proton 7.0-6) an decent experience without having to do much tinkering.
Controller needed to be enabled manually in game settings using Steam Button and touch pad and the game had to be fully restarted afterwards.
FPS seems to drop when treversing the world down to 30s due to SMTs (which is likely to get fixed with the upcoming Steam OS update). For shooting it seems fairly smooth, though.
Rage was one of the first games I have tried on Steam Deck (then using Proton 7.0-4) and at that point it was unplayable. I am happy to see that with 7.0-6 this changed and the game seems to be fully playable without any noticable graphical corruption visible. It's only a shame that gamepad has to be manually enabled, as otherwise this would be one of the games best fit for Steam Deck.
not playable
on latest ge proton not playable didnt know how to tinker to playable state

Works well, for the most part.
Car engine audio sometimes drops when driving. Some SFX in the racing minigames (e.g. when player or AI goes through checkpoint beacon light thing) starts delayed, sometimes with degraded quality.
No Megatexture Issues with this Commandline and starting once in Desktop Mode, selecting windowed mode. Now runs absolutely fine!
+cvaradd g_fov 12 +com_allowconsole 1 +com_skipIntroVideo 1 +image_anisotropy 2 +image_usecompression 0 +g_showplayershadow 1 +m_smooth 0 +fc_maxcachememoryMB 1024 +vt_maxPPF "2"
Game runs best in 64 bi mode, mega textures not rendering correctly. Also gamepad can be turned on in the options.
Mega textures are not rendering correctly. Gamepad can be turned on in the options.
%command% +com_skipIntroVideo 1 +com_allowconsole 1 +image_anisotropy 16 +image_use +r_swapInterval 1 +jobs_numThreads 0 +vt_maxPPF 16
Installed this a year ago and had the horrible texture glitches which were mostly fixed with the command line options: %command% +com_skipIntroVideo 1 +com_allowconsole 1 +image_anisotropy 16 +image_use +r_swapInterval 1 +jobs_numThreads 0 +vt_maxPPF 16
Came back to it recently, and with mesa 22.1.7 graphics are perfect, see the (fixed) bug https://gitlab.freedesktop.org/mesa/mesa/-/issues/1326
Now only sound is still cutting out early or some effects are sometimes totally missing. It's still playable though.
Everyone experiencing texture glitches, please check your Mesa version.
Around 20-30% of the chequerboard squares on the megatextures show the wrong texture all the time.
Contrtoller not detected on initial launch, had to use external keyboard to navigate menu to activate gamepad, worked fine after that.

finally working on AMD integrated graphics
After updating my mesa version it fixed the texture issues. Everything seems to work fine now.
Works out of the box with recent Mesa release 22.1.3 which contains a fix for the game.
Current version of Mesa (22.1.2 as of this report) has issues with in-game textures being completely broken, making it completely unplayable.

Commonly reported massive texture artifacts using AMD Graphics (RX 6600 in my case). I was unable to rectify this problem either in 32bit or 64bit. Sad.
Finalmente! Perfeito com o driver RadeonSI. Antes possuia o bendito problema de texturas. gitlab.freedesktop.org/mesa/mesa-/issues/1326
Whitelist
The game doesnt start
Installed and played 32bit version with no problems
Very sensitive mouse
All the texture tiles are messed up, making it hard to see what you're looking at.
Texture artifacts are distracting and make it difficult to differentiate terrain and enemies.
GPU transcoding cannot be turned on, resulting in worse texture popup with high detail textures. Runs perfectly otherwise.
Run out of the box.
mouse input seems to be choppy