The test results for this version are very old, and as such they may not represent the current state of Wine. Please consider submitting a new test report.

Selected Test Results

What works

Absolutely awesome... Runs flawlessly, everything works. Game runs fast and smooth nearly out of the box.

What does not

Found nothing.

Workarounds

What was not tested

Multiplayer

Hardware tested

Graphics:

GPU:

Driver:

Additional Comments

***System Information***
CPU: AMD Phenom x4 3,4Ghz
RAM: 16G
GPU: ATI 6990
VGA Driver: Latest Catalyst 12.4
***Game Settings***
Resolution: 1920x1080 - Fullscreen
Texture Cache: Large
Vsync: On
***Installation***
1. operating on a clean WINEPRFIX (dont know if thats nec. but im using a new PREFIX for every game/program i install...
2. env WINEPREFIX=~/yourfoolwinepath/ winetricks xact_jun2010
3. env WINEPREFIX=~/yourfoolwinepath/ wine Setup.exe
The installer runs without any problems.
After that the game crashes for me after leaving the first room and get rescued by the carguy. The game freezes. So i applyed the Update 1 from ID (normally you´ll get it from Steam if you got the arselicking Steamversion ^^)
After that the game runs really flawless without any probs (okay i got some black graphic issues, but thats not to be announcend here).
I would even give the game a platinum status.
ID´s definetly the best choice.
***Additional Notes***
Take a look at the little "dancing" character in the front of you sitting in the buggy where you get rescued from the bandits direct after starting the game.
Here wo go :-) knee down for the one and only DOOM character taken you back in the days :-D the older ones may know what i mean ^^
ID rulez!!

Thank you very much for finding some time to improve AppDB. In order to get your report immediately accepted please be sure to follow following simple rules:

Test the game under fresh clean wineprefix;

Include exact specs of the computer you had tested the game on (CPU, GPU, amount of RAM and VRAM) in the "Additional Comments" section of the report;

Specify versions of essential software components, most notably: is your system 32bit or 64bit, what is the version of the GPU display driver you use and what is the version of the OS kernel;

Include detailed information on the native dll overrides you had to use in order to get the game working. If you had installed dlls yourself - include complete information on the sources of dlls and the exact steps you took to install them.

Thank you in advance!

How to tweak Rage to get best from it under Wine

WARNING: Patch from 2011/10/08 broke the game for about half of users to the level it is barely playable. It is not Wine bug, it is the game developers fault. Same (and even worse) problems affect people on native OS this game had been developed for. Expect severe framerate drops while moving or looking around, jerky movement with stutters every 1-2 seconds, complete lack of textures on the terrain, e.t.c. What actually happen is that tweaks idSoftware had put into engine auto-detection logic fail to properly detect some essential things like optimal number of threads for your CPU, e.t.c. More details follow about how to tweak the game configuration to fit best for your system.

HINT: It is possible for nVIDIA users to get CUDA-accelerated textures decoding under Wine. It is required to install linux version of nVIDIA Cuda Toolkit 4.0 32bit and compile special Wine Cuda wrapper. Here is a link to the thread on Steam forums where you can get more details on this topic: http://forums.steampowered.com/forums/showthread.php?p=25773275

Game requires XAudio2 engine version 2.7 which is a part of Microsoft DirectX June 2010 redistributable. In case you had downloaded and launch the game in a "usual" way using Steam client in a clean Wine prefix it should automatically install DirectX runtime for you. In an unfortunate case it had failed for some reason you should use fresh version of winetricks to install xact_jun2010. Be careful not to confuse it with xact, which would install older version (2.6) of XAudio2 engine from February 2010 DirectX redist that is too old and won't fit for this game.

It had also been reported that for some people it was required to set sound into "Emulation" mode in winecfg preferences. This setting is not available (and most likely is not required) in Wine versions 1.3.29+. In case you use older Wine version and experience sound problems your best bet would be to upgrade to a more recent Wine version. If you've got some strong reasons not to proceed with Wine version upgrade then you might give "Emulation" mode a try. YMMV.

Fixing "game starts up OK but there are no sounds" (a.k.a. "No in-game sound")

It had been reported that sometimes Rage starts up OK but fails to produce any sound output for uncertain reasons. Chances are that you have your Wine prefix configured to emulate WinXP and you've got stale DirectSound registry entries which causes trouble for an unknown reasons. Try running Rage with a fresh and clean Wine prefix and check if it helps. You may also try to delete all HKLU/Software/Wine/DirectSound key and its subkeys from registry, in my case it helped to fix the problem and get Rage working correctly under old and polluted Wine prefix. Switching prefix to emulate Windows 7 or Vista is another possible workaround for this problem.

Tweaking the game to run best on your rig

WARNING: Doing the tweaks below is extremely important if you want to get smooth consistent FPS level and significantly reduce the "texture pop-in" effect.

RAGE is based on idTech5 engine which uses "Virtual Texture" (a.k.a. "megatexture") technology to texture the game world. This technology is very computation intensive and is extremely hungry to the CPU power, to GPU power (in case you use Cuda-accelerated VT transcode) and to the overall throughput of the disk subsystem. The engine is designed in a such way so it should be tweaked to run most effectively using all available CPU cores your system is equipped with. There's built-in CPU core count detector that is supposed to automatically tweak the engine but it fails to properly do its job due to limitation imposed by Wine (as of Wine 1.5.2). Problem is that the game uses a technique to determine CPU cores count which isn't properly implemented in Wine resulting the game to assume that the system is a single CPU single core box.

To manually tweak the engine you should set the value of two game cvars, namely "vt_maxPPF" and "jobs_numThreads". First one determines how much texture pieces should be decoded per displayed frame in the worst case, second one tells the game to use that much threads simultaneously to do its tasks.

Correct value for "jobs_numThreads" depends on the amount of cores your CPU has. Quad core CPU owners should use 3 or 4, dual core CPUs would work better with 1 or 2. In case your CPU is Hyper-Threaded you'd better set this cvar to the number of physical cores your CPU has (i.e. for 4 cores/8 HT execution threads CPU best value would be 4). At some rare cases (useful for dual core CPU + AMD GPU) it might be better not to use separate job thread at all due to limitations imposed by GPU driver. For latter case you should set jobs_numThreads to 0 to completely turn off usage of job threads.

Best place to set "jobs_numThreads" is in Steam Game Launch Options (details on how to do it). Add something like "+jobs_numThreads " and you should be fine.

With Rage path 1.2 (released on the 2th of Feb, 2012) it became possible to benchmark the speed of the texture transcode operation. Unless you had compiled and installed the wine-cuda DLL wrapper for your system the speed of this operation is mostly determined by the speed of your CPU and the amount of threads the game is instructed to use through "jobs_numThreads" variable. Don't be fooled by the number this benchmark presents to you - having best texture transcoding performance is not the same as having smooth gaming experience with consistent FPS. If you want to maximize the transcoding performance despite this warning you can try to do as follows:

Set "jobs_numThreads" to a number that is equal to the number of cores your CPU has.

Start up the game, head on to the "Video settings" menu and execute the "Transcode benchmark". Note the resulting number.

Quit the game, decrease "jobs_numThreads" value to be half of the CPU cores count (i.e. if it had been set to 4 - set it to be 2, if it had been set to 2 - change to 1, etc.) and restart the game. Try launching the transcode benchmark again. In case resulting number would be greater than it was on a first try - keep "jobs_numThreads" equal to the half of your CPU cores count. If not - repeat benchmark with "jobs_numThreads" set to be twice the CPU cores count.

Keep playing with various "jobs_numThreads" values until you find one that gives you best transcoding performance.

It is important to understand that there's no point in getting maximum texture transcode performance no matter the costs because it might result in extremely unstable FPS and non smooth gaming experience. For example, with AMD FX 8120 eight core CPU one would get maximum transcoding performance (bench. result ~80 megatexels) when "jobs_numThreads" is set to 8, while most stable FPS level is achieved with "jobs_numThreads" equal to 2 (smooth and almost constant 60FPS) despite the fact that benchmark result for latter case is significantly lower - around 40 megatexels. In other words, if the benchmark result is 35-40 or more - there's no point in trying improve it. On the other hand, having benchmark result less than 20 would result in jerky gaming experience with huge FPS drops during viewport moves.

Second cvar to tweak - "vt_maxPPF" - effectively acts as a balancer between FPS stability and the amount of texture pop-ins. Depending on the speed and type of your CPU and also on whether you use Cuda-accelerated texture decoding or not the good value for "vt_maxPPF" cvar might be in range from 8 to 256. Owners of low-speed dualcore CPU should use 8 or 16, typical value for quad core AMD Phenom II X4 955 CPU would be 32 or 64. Users with Cuda-enabled setups might be happy with setting vt_maxPPF to 128 or 256. In case you can live with moderate amount of textures pop-in but can't stand FPS drops below 60 when moving viewport your best bet would be to use low value for vf_maxPPF like 8 or even 4. To set the value of this cvar add something like "+vt_maxPPF " to Steam Game Launch Options.

If your system configuration is similar to "quad-core CPU + GeForce 550 Ti with 1Gb" you could use "jobs_numThreads" set to 2 and "vt_maxPPF" set to 16 as a good starting values. It would allow you to get smooth 60FPS gaming experience when playing at 1680x1050 resolution with 4x antialiasing, "big" textures cache and "high" aniso settings.

Reducing textures pop-in effect

Note: With game patch released 2011/10/08 it is no longer necessary to edit config file to change page size. Setting "Texture Cache" to "Large" in video setting menu has the same effect.

In case your videocard have got more than 1GB of video RAM it is reasonable to increase game virtual texture page sizes (think about it­ as "some kind of texture cache") to be 8K per page. To do this create a new file in «Steam Install Dir»/steamapps/common/rage/base/ fold­er named «Rageconfig.cfg» and populate it with following lines:

Note: It might be required to specify "+com_skipIntroVideo 1" in the Steam's game "Launch properties..." for intro video skip to work. I have it set in both places and it works like a charm.

How to correctly set anti-aliasing and anisotropic filtering level (a.k.a. "How to fix visible polygons seams")

Note: With game patch released 2011/10/08 it is no longer necessary to edit config file to change anisotropic filtering level. Changing it in video setting menu has exactly the same effect.

You should never force AA/ANISO levels through GPU driver control panel. Game engine uses complicated rendering technology which is incompatible with the ways drivers force AA/ANISO levels and results in visible render glitches in case AA/ANISO level forcing is turned on. nVIDIA users should turn off "Texture Sharpening" as it causes huge render glitches too. Correct way to set the AA level is to use in-game graphical settings menu. Setting the level of anisotropic filtering requires modifying game configuration file. Create «Rageconfig.cfg» as was described earlier and populate it with the following lines:

image_anisotropy "1"
vt_maxaniso "2"

These two settings control the ANISO level the game uses for texture filtering. Official tweak guide states that the engine only supports two levels on ANISO filtering, namely 2 and 4, and to select one of them you should modify the value of vt_maxaniso cvar. My experiments showed that the visual difference between levels 2 and 4 is almost negligible while performance drop is pretty huge. YMMV, experiment and choose the best to fit your needs. I hadn't been able to notice any visual and performance difference changing image_anisotropy cvar value. Still it might be wise to set it to be 8 or 16 in case it has effect on visual quality in some rare circumstances.

Fixing "screen tearing" problem

Note: With game patch released 2011/10/08 it is no longer necessary to edit config file to change vsync mode. Changing "VSync" in video setting menu has exactly the same effect.

Rage engine is designed in a special way to support brand-new vsync controlling style. Main idea is to dynamically control vsync turning it on in case system it fast enough to render at 60+ FPS and off in case FPS is less than 60 FPS. This technology allows tear-free 60 FPS gameplay on decent systems without undesired drops down to 30 FPS in performance-constrained situations. Unfortunately current versions of GPU drivers lack OpenGL extension that is required for this vsync control system to work. Although it had been reported by nVIDIA linux driver development team member that the implementation of this extension is complete and it would be introduced in future driver versions, as of driver version 295.40 the extension in question is still unavailable. To overcome the problem and get a tear-free gaming experience in Rage one would have to reconfigure the game to use traditional vsync controlling scheme (FPS drops down to 15/30 in case system is not fast enough to render at 60+/30+ FPS). Recommended way to enable traditional vsync control scheme is to create «Rageconfig.cfg» file as explained in previous section and add the following line into it:

r_swapInterval "1"

It should do the trick for the most cases. With some buggy GPU drivers this setting might have no effect. In such case you should try to force vsync "on" in GPU driver control panel. It might help but be prepared to face game "crash to desktop" and all kinds of render glitches as game engine wasn't designed to work with vsync forced on using GPU driver control panel.

when i have look in winetrick xact was already installed
i have the latest ubuntu (11.10) with alsa plugin
in win config when i push "test the sound" it's work great !
rage 3 DVD version and wine 1.3.31

Which version of winetricks do you use? Rage requires to use XAudio engine v.2.7 which should be installed using "winetricks xact_jun2010" and not "winetricks xact".

In case your wineprefix lacks the XAudio engine RAGE require - you would get an error message at RAGE startup about not being able to find XAudio engine and suggesting you to install latest DirectX runtime.

If you've got game starting up OK but not producing any sound - try to experiment with changing emulated windows version (change to win7 if you're using winxp, or to winxp in case you use win7/vista). If nothing helps and other Windows apps under same wineprefix are able to produce sound - file a new bug report to Wine bugzilla.

ive tried to run this game on WS8 1.3.29 but so far ive had no luck. i've followed all instructions but im not sure if im doing the XAudio2 part correctly. when i have installed everything needed, i run the game and i then get a whole load of errors popping up in the 'Rage Console'. i have no idea what the problem is, ive tried just about everything...

Unfortunately it had been reported several times by Mac OS X users that the game fails to startup under Wine on Mac OS X giving an error about failing to set the required pixel format. I'm afraid that most likely this problem is not Wine-related but rather Mac OS X related with the OpenGL implementation not meeting the requirements RAGE expects from it.

Wine version? Hardware? ALSA/OSS/Pulse? There were two bug reports about recent regression in Wine that resulted in problems with sound in Rage. You'd better post detailed info to Bugzilla rather than spaming AppDB comments section which isn't specially designated for bugreporting.

Argh, you've got pulse installed. Be sure to self-compile fresh alsa-plugins from git or you would experience the exact behavior you had described with sound stopping to work after some time. It is known bug in alsa-plugins which is believed to be fixed in git but there hadn't been official alsa-plugins release with this fix included.

Install won't complete or at least wouldn't on my rig. Just let the directx message fail and click close, then the second install will complete (c+ redist pack). Every time after that you may get the prompt to re-install directx. Use the regsvr32 trick to register the xaudio2_*.dll's and the game will start.

Steps to take:
Clean wine prefix
run rage installer, you may get a crash on directx not being able to copy files to certain locations and then crashing. Don't freak out its fine and even if this fails it will still load the game.

RE: Crash when exiting the first room by Xpander on Monday October 10th 2011, 4:21

what catalyst settings do you have?
i tested mipmap quality settings at high quality and quality, catalyst ai at disabled and advanced.
didnt make much difference. all maxed from game settings + fov settings and some rageconfig.txt settings.