!!**Official RAGE Thread**!!

Working pretty well for me except for the textures that sort of pop up when turning fast, I can live with that though.

Really enjoying it, Great game and it looks fabulous and plays amazing!

Screen tearing was a fail but I forced it on in Nvidia Control Panel.

If I looked here before I went and bought it I probably wouldn't have got it so I am glad I didn't read this thread :p


GTX 580
i5 2500k @ 3.30Ghz
 
Anyone else envisage a HUGE texture update to say the least? id should be embarrassed at some of the texture quality in this game. Basically every indoor environment is a blurry mess, you get some ok texture work indoors but if you look around theres plenty of really low res stuff. The only real decent looking textures you see are driving around in the canyons, character and weapons models. Its 2011 and its like we took a quantum leap backwards 10 years at least.

Erm Yeah. Have to say I was really looking forward to this game. So much so that I actually got out of bed at 5 am to read the initial user reviews and reactions when it was first released in the USA.

To say I couldn't believe what I was seeing and hearing is an understatement. I cancelled my pre- order the same morning.

Some of those close up textures and graphics look like they were drawn by a 10 year old with crayons. Maybe that's who this game is aimed at? Dunno really. But it's certainly not aimed at people who've invested a shed load of money in a PC with a decent graphics card who might , like , notice the difference.
 
Last edited:
******** :rolleyes:

There are comments in other forums with the 480 reporting issues.

"Outside of the screen-tearing which is awful, no. Even the 16k textures aren't pushing VRAM usage past 800MB - yet you're supposed to need a 1.5GB card for them (which i have) "

Yes of course im lying for fun :D

All i have done is force V-Sync off and evreything works fine with 8k textures
 
That is the main problem i have, but i'm afraid i can't live with it.

I will play through it (reluctantly) as there is little else out there until Skyrim, Battlefield, and Batman comes out (for me anyway). This will keep me busy till then.

By the time they fix it (I am sure they will), it will be under £15, and a bargain buy. Unfortunately, I can't see much replay value in this one, which is a shame.

So if you want the best experience, it may be best to wait. But with so many great games coming out in the coming months, playing it now is my only realistic option.

A real shame, because under the hood is a very good and enjoyable game.
 
I can't get passed the intro screen.

The intro stops and then i just get a black screen. Any ideas? I have an ATI 5850
 
That is the main problem i have, but i'm afraid i can't live with it.

Likewise tbh. Right on the edges of the screen when I'm focusing on the centre = constant distraction that I keep trying to focus on because its 'movement' = Eye strain after 10 minutes.

I'll have a quick look for config changes that might help and give it another go.
 
Vsync and mouse lag/weirdness is a common combination sadly, yeah. Have you tried enabling triple buffering?

Just an aside on vsync, 60fps and input lag for anyone that's interested:

The 60fps vs vsync issue: In principle, setting the frame output to be precisely the same as the monitor refresh rate (60Hz unless you have a 120Hz screen) should not lead to tearing, so long as the first frame output is calibrated such that the "tear" occurs at the top or bottom of the image. However in practice it's near-impossible to tune the framerate output to perfectly match the monitor refresh... Lets say you're outputting at precisely 60fps, but your monitor is updating at (say) 59.9Hz. The frame will be updated just before the monitor finishes its refresh, so the tear-line will shift upwards very slightly. You will see the tear-line moving upwards on your screen at a rate of 0.1Hz (it will take 10s to move the entire way up the screen).

You can see this effect yourself by using a game that has a fps limiting command (like HL2 for example; fps_max is the command IIRC). Set the framerate to (say) 59fps and you should see the tear-line moving up the screen at 1Hz. Try 60 and see what happens... Anyway, this would be the reason to enable vsync: A frame is stored in the frame buffer until needed. This eliminates tearing, but always storing a frame in the framebuffer means that you're always one frame behind where you would have been without vsync.


Vsync and input lag: You can predict the amount of extra lag you will feel due to vsync based on your monitor type, and whether you're using double or triple buffering. Instead of re-writing stuff, I'll just use an old post I made in the graphics card forum:

"double buffer" vsync (the most common mode) stores an extra frame in the framebuffer, and waits until the screen refreshes before outputting it, to avoid tearing. "Triple buffer" vsync is similar, but stores two extra frames in the buffer.

Double buffer vsync will only allow your framerate to be an integer division of your monitors refresh rate: That is, you will only be able to get 60fps, 30fps, 20fps, 15fps, 12fps, 10fps (etc). If your GPU is not capable of rendering 60fps, your framerate will drop to 30, and so on. These sudden changes in framerate can be a little annoying. Triple buffer vsync on the other hand allows you to output frames at any framerate.

The downside to enabling vsync is a lag between giving a command and seeing it on the screen (due to the frames being stored in the buffer for a time). This can make a game feel sluggish and "muddy". Triple buffer will have a higher lag than double buffer, and a 120Hz monitor will have a much lower lag than a 60Hz screen. The exact amount of lag depends on where the screen is in its refresh cycle when the frame is completed, but the range of lag values is as follows:


* 60Hz double buffer ('regular') vsync: 16.7 to 33.3ms lag
* 60Hz triple buffer vysnc: 33.3 to 50ms lag

* 120Hz double buffer vsync: 8.3 to 16.7ms lag
* 120Hz triple buffer vsync: 16.7 to 25ms lag



For this reason a lot of people consider a 120Hz screen to be great for gaming, even if they aren't using it for 3D. It allows vsync to be enabled with very little extra lag. Also you get more "divisions" in double buffer vsync [120, 60, 40, 30 etc]. Dropping from 60fps to 40fps is not nearly as annoying as dropping from 60fps to 30fps.



Regarding rage - I'm just about to fire it up, so I guess I'll find out what it's like shortly!
 
Most of the environment will look bad close up because all versions are using highly compressed textures. While this isn't necessarily a console port there are lot of restrictions in place to accommodate the consoles.
 
Right after a couple of hours it is runnng now. Had to uninstall my drivers as it seems like it was the bloody rage update that broke it.

Is there a tweaking guide for this game? Cos the pop ins are brutal!
 
So are the problems confined to amd drivers or is the game broken?

Is it still broken?

I got gtx470 and 1055t, will I have problems or not? It's a big download I must know whether it's worth downloading now or wait for a fix patch.
 
Just a quick question for those with nVidia cards and who have the 8k texture config working - are you using the latest beta drivers, or some previous ones. Just wondering, as nothing that I have tried will get the 8k config to work in any way at all.
 
So are the problems confined to amd drivers or is the game broken?

Is it still broken?

I got gtx470 and 1055t, will I have problems or not? It's a big download I must know whether it's worth downloading now or wait for a fix patch.

Why not just download now? I have a GTX460 and it is flawless but I have an i5 2500K CPU, no idea how different that is to your Phenom.
 
Back
Top Bottom