Hitching, Stalling, 1 FPS, Reproduced and Fixed

Post » Tue May 15, 2012 9:08 pm

This might be relevant for some of you. ;)

I've been able to fully reproduce the hitching/stalling/1 FPS bug that some people have been experiencing, and even on NVIDIA hardware too. I've also determined what caused it (at least for my test case) and have fixed it.

Check your value of vt_uncompressedphysicalimages.

If you have grabbed a rageconfig file off the web, chances are that this might be set to 1. Now, Rage defaults it to 0, and by setting it to 1 the bugs come in force. So put it back to 0, issue a vt_restart and all should be good.

Doing a direct comparison of some areas that exhibit nasty compression artefaces, I'm not able to see any difference between before and after, so I'd suggest that the value of setting this to 1 is quite dubious.

It seems safe to leave vt_uncompressedvmtr at 1 and image_usecompression at 0, but if you still have problems flipping them back to their defaults (0 and 1, respectively) may not be a bad idea.
User avatar
Zoe Ratcliffe
 
Posts: 3370
Joined: Mon Feb 19, 2007 12:45 am

Post » Tue May 15, 2012 3:36 pm

This might be relevant for some of you. ;)

I've been able to fully reproduce the hitching/stalling/1 FPS bug that some people have been experiencing, and even on hardware too. I've also determined what caused it (at least for my test case) and have fixed it.

Check your value of vt_uncompressedphysicalimages.

If you have grabbed a rageconfig file off the web, chances are that this might be set to 1. Now, Rage defaults it to 0, and by setting it to 1 the bugs come in force. So put it back to 0, issue a vt_restart and all should be good.

Doing a direct comparison of some areas that exhibit nasty compression artefaces, I'm not able to see any difference between before and after, so I'd suggest that the value of setting this to 1 is quite dubious.

It seems safe to leave vt_uncompressedvmtr at 1 and image_usecompression at 0, but if you still have problems flipping them back to their defaults (0 and 1, respectively) may not be a bad idea.

Closest thing I have to that in my config files are 2 things.

vt_uncompressedVmtr "1"
image_useCompression "0"
User avatar
Lynette Wilson
 
Posts: 3424
Joined: Fri Jul 14, 2006 4:20 pm

Post » Wed May 16, 2012 3:02 am

Closest thing I have to that in my config files are 2 things.

vt_uncompressedVmtr "1"
image_useCompression "0"

I don't think they'll do any difference. AFAIK it was a command for Doom 3 to let it use the original textures on disk, whereas it normally compressed them while loading. RAGE however already has significantly compressed textures.
User avatar
Eduardo Rosas
 
Posts: 3381
Joined: Thu Oct 18, 2007 3:15 pm


Return to Othor Games