Minor heads-up for AMD APU users

Post » Sun Jun 03, 2012 5:00 pm

I recently discovered that on systems with both an AMD APU and a discrete GPU, OpenGL applications (not just Rage) will only use the integrated GPU from the APU rather than the much more adequate discrete GPU.
This somewhat bothers me, as it means OpenGL applications on my laptop will only use the HD 6520g GPU (which is rated at 256 GFLOPS) while Direct3D applications on my laptop will take advantage of the HD 6650M (rated at 576 GFLOPS).
..

In other news, the dynamic viewport/render-target resolution scaler in Id Tech 5 is a very useful feature. It should be implemented into every game!
User avatar
{Richies Mommy}
 
Posts: 3398
Joined: Wed Jun 21, 2006 2:40 pm

Post » Sun Jun 03, 2012 9:03 am

..

In other news, the dynamic viewport/render-target resolution scaler in Id Tech 5 is a very useful feature. It should be implemented into every game!

What exactly does this do? Or more to the point, how does it work in contrast to other games?
User avatar
Alba Casas
 
Posts: 3478
Joined: Tue Dec 12, 2006 2:31 pm

Post » Sun Jun 03, 2012 11:05 am

Short version:

To put it simply, where other games drop in framerate, Rage will get slighly pixelated instead but keep running 60 fps.
--------------------------------------

It's a feature that is by default enabled on the console versions (Xbox 360, PlayStation 3) and enabled on PC through an unpatched *.exe (before the command was locked) with the appropriate console command.

It's sole purpose is to reduce the resolution of the render-target when the framerate goes below a certain treshold (eg. 60 fps).
So eg. if you play at 1280x720 and the framerate is 50 FPS it will change the resolution of the render-target to be eg. 1168x657 which should let it run at 60 FPS.

The cool thing is that unlike just changing the screen resolution permanently, the interface elements are not scaled at all (remain at native resolution).
User avatar
Avril Louise
 
Posts: 3408
Joined: Thu Jun 15, 2006 10:37 pm

Post » Sun Jun 03, 2012 7:27 pm

It's a feature that is by default enabled on the console versions (Xbox 360, PlayStation 3) and enabled on PC through an unpatched *.exe (before the command was locked) with the appropriate console command.
So basically, if we have the patched and updated RAGE, we don't get that feature? :/
User avatar
Toby Green
 
Posts: 3365
Joined: Sun May 27, 2007 5:27 pm

Post » Sun Jun 03, 2012 8:02 am

Short version:

To put it simply, where other games drop in framerate, Rage will get slighly pixelated instead but keep running 60 fps.
--------------------------------------

It's a feature that is by default enabled on the console versions (Xbox 360, PlayStation 3) and enabled on PC through an unpatched *.exe (before the command was locked) with the appropriate console command.

It's sole purpose is to reduce the resolution of the render-target when the framerate goes below a certain treshold (eg. 60 fps).
So eg. if you play at 1280x720 and the framerate is 50 FPS it will change the resolution of the render-target to be eg. 1168x657 which should let it run at 60 FPS.

The cool thing is that unlike just changing the screen resolution permanently, the interface elements are not scaled at all (remain at native resolution).

That was really informative, cheers dude! :D

And that is a brilliant idea, I have the same hope that more developers will adopt this idea, and then allow a manual override for people who are graphics freaks, this way we get best of all possibilities.
User avatar
Quick Draw III
 
Posts: 3372
Joined: Sat Oct 20, 2007 6:27 am


Return to Othor Games