Rage problem - artifact or game bug ?

Post » Tue May 15, 2012 10:48 pm

Someone noticed this type of artifact IN RAGE? I have a geforce gtx 580 1.5 and I noticed this problem only in this game.

http://www.youtube.com/watch?v=F5xzSwa-EBM&feature=player_embedded
User avatar
Farrah Barry
 
Posts: 3523
Joined: Mon Dec 04, 2006 4:00 pm

Post » Wed May 16, 2012 4:29 am

Never seen that happen. It's possible that you might be out of video memory, although that seems to mostly affect AMD users and indications are that it would be blue rather than white. All the same, might be no harm to dial down AA if you've got it maxed out and see if it resolves anything.
User avatar
latrina
 
Posts: 3440
Joined: Mon Aug 20, 2007 4:31 pm

Post » Wed May 16, 2012 3:12 am

Agreed turn back AA, I max out my AA with my 460m/GTX480 and seen some of the same.
At times it looked some what the same as what the ATI/AMD user have been posting with there driver problems.
I just cut AA off and have had no problems on either card.
User avatar
Chris BEvan
 
Posts: 3359
Joined: Mon Jul 02, 2007 4:40 pm

Post » Wed May 16, 2012 2:32 am

Hi guys , thanks for the response, but not solved. I really think the problem is video memory. What is puzzling me is that I'm has gained a lot in the game and had not realized it yet. I will test more games to see if this happens. Where I live is very hot this time of year, close to 40C
User avatar
Julia Schwalbe
 
Posts: 3557
Joined: Wed Apr 11, 2007 3:02 pm

Post » Wed May 16, 2012 8:45 am

Could just be a bad texture in the game.
User avatar
Leah
 
Posts: 3358
Joined: Wed Nov 01, 2006 3:11 pm

Post » Wed May 16, 2012 1:27 am

Considering there is only one texture in each map -- it's unlikely but still possible. It looks as though the effect is popping in and out and the region affected is sometimes drawn fine, sometimes not.

If dialling down AA doesn't fix it then it may be fixable by dialling down some other quality settings. The trick here is normally to bring everything down to the lowest, then bring them back up gradually until you find the combination of settings that cause it - once you have that you know what to avoid.

What I'd tackle first is the rageconfig settings; a lot of the configs that sprang up online in the first few days after release have really inappropriate settings, and if you're using one you may have inherited some badness from them. I personally find - on NV hardware and since the patch and 2.85 drivers were released - that I can drop all graphics related rageconfig settings and just use the in-game menus. So the way to do that is to rename your rageconfig (rather than delete it), run once in safe mode to flush anything remaining out, then bring stuff up as desired using the menus.

Also setting everything to "Application Controlled" in your NV control panel is advised (especially AF, as this may corrupt textures if you try to force it).

Hope something in that lot gives you a few pointers to work from.
User avatar
GPMG
 
Posts: 3507
Joined: Sat Sep 15, 2007 10:55 am

Post » Tue May 15, 2012 10:08 pm

Well it's not related to the "texture" for sure.

I had the same happen to me, but only once, in Wellspring, along the border of Mick's Garage in the entrance door frame.

I agree it's probably video memory, because as I said, it only happened once, then it just stopped. Must have to do with how the textures were loaded onto the map during the loading of the level and all its assets.

Anyway I'm sure we wouldn't get this stuff it we has a better card, I didn't even think mine would run the game smooth... it doesn't exactly meet the minimum requirements, and yet it plays the game just fine :smile:
User avatar
Jason Wolf
 
Posts: 3390
Joined: Sun Jun 17, 2007 7:30 am


Return to Othor Games