Difference between revisions of "RAGE"
m (inter-wiki links) |
|||
Line 1: | Line 1: | ||
{{infobox | {{infobox | ||
|cover = Rage cover.jpg | |cover = Rage cover.jpg | ||
− | |developer = id Software | + | |developer = [[Wikipedia:id Software|id Software]] |
− | |publisher = Bethesda Softworks<br/>Aspyr Media | + | |publisher = [[Wikipedia:Bethesda Softworks|Bethesda Softworks]]<br/>[[Wikipedia:Aspyr Media|Aspyr Media]] |
|engine = id Tech 5 | |engine = id Tech 5 | ||
|release dates = <sup>NA</sup> October 4, 2011<br/><sup>AUS</sup> October 6, 2011<br/><sup>EU</sup> October 7, 2011 | |release dates = <sup>NA</sup> October 4, 2011<br/><sup>AUS</sup> October 6, 2011<br/><sup>EU</sup> October 7, 2011 |
Revision as of 15:05, 21 March 2012
Issues and Fixes
Graphics
- Seams may be seen between textures (dotted lines). This will occur when forcing 16x (or possibly lower) anisotropic filtering in the Nvidia control panel. Change the setting to 'application controlled' to correct this.
Stutter with ATI Cards
- If you experience stutter, even with graphics options minimized and a high end PC, simply disable Catalyst Overdrive and the issue should be resolved.
Enabling Developer Console
You can enable the developer console for RAGE by right clicking the game in your list of Steam games, then clicking Properties, then Set Launch Options. In there, enter "+set com_allowconsole 1" without the quotes. Now you can access the developer console in game via the ~ key.
Useful Console Commands
g_fov X - Sets the desired field of view, X being the number of degrees.
Customizing rageconfig.cfg
Setting game variables in rageconfig.cfg will allow you to alter various properties to adjust visual quality outside of the built in game menu. Adjusting values, especially variables related to video memory use should be taken with caution. If Rage goes over your video cards memory limit you can reduce your framerate to single digits (1-3 fps).
C:\Program Files (x86)\Bethesda\id Software\RAGE\
Steam:
C:\Program Files (x86)\Steam\steamapps\common\rage\base\
TheDailyBuggle has an article describing what most of the graphical related variables will do.
DoNotArgue has a rageconfig.cfg generator. It is recommended to start with default values and only modify variables related to the desired result.
A basic rageconfig.cfg to increase texture detail
If the configuration generator feels overwhelming, this basic rageconfig.cfg will improve texture resolutions, enable the console, save uncompressed screenshots, and skip the intro videos. You must have 1GB or more of video memory for this fix. Additionally there are diminishing returns on increasing texture resolutions, so using 16k x 16k textures is a waste of video card memory and wont be a significant upgrade over 8k x 8k.
C:\Program Files (x86)\Bethesda\id Software\RAGE\rageconfig.cfg
com_videoRam 1024 fc_maxcachememoryMB 1024 //put your VRAM value in. com_AllowConsole 1 com_SkipIntroVideo 1 vt_pageimagesizeuniquediffuseonly2 8192 // Rage defaults to 4096x4096. Note that not all textures will be improved, but this will significantly improve some indoor areas. vt_pageimagesizeuniquediffuseonly 8192 vt_pageimagesizeunique 8192 vt_pageimagesizevmtr 8192 vt_minlod -1 vt_maxlockedpages 1024 vt_maxaniso 4 vt_uncompressedvmtr 0 vt_uncompressedphysicalimages 0 image_lodbias -1 // Textures will have a slightly sharp bias image_anisotropy 4 // Maximum anisotropy image_usecompression 0 image_screenshotquality 100 com_captureTGA 1 //this forces your screenshots to be in uncompressed TGA format
Cuda transcode differences
Rage uses very highly compressed texture data as part of its MegaTexture technology engine. During gameplay textures are decompressed on the fly and streamed to the video card. A noticeable effect from this is "popping in" textures where blurry textures are rapidly replaced by sharper ones as the player turns his camera around quickly. This behavior can be adjusted either through enabling Cuda transcode or adjusting how many textures are decompressed per frame. Users with a fast video card can benefit from Cuda transcoding which will offload this task to the video card rather than the CPU. Users with 4 or more processor cores will benefit from extra CPU transcoding giving all available video card time to rendering the game.
rageconfig.cfg for a quad core processor
vt_useCudaTranscode 0 // Set this to 1 if you have a fast (nVidia GTX 560 Ti or better) video card but slower CPU. If you have a slow video card this will actually degrade performance! vt_maxPPF 128 // Setting this too high can degrade performance, and 128 is regarded as the maximum necessary for quick texture loads. Try 32 or 64 for dual core processors.
Using a value of 64 vt_maxPPF will also yield acceptable results. If you wish to simulate a poorly performing computer set this to 1.