Adjust fps before amd gpu kicks in

Hey all

Since I have my new laptop I have seen that I can decide how many fps my cpu should do before my nvidia gpu kicks in. Does amd have that as well in their CCC drivers?

If they don't it would be good idea.

Thanks

 

that doesn't make sense. i think you mean "frames", not "fps", and I think you have the whole idea wrong.

It's not how many frames get rendered before the cpu kicks in. It's "can I start working on frame 2 even though frame 1 isn't displayed yet?"

 

Well my cpu (i7-2630qm will produce 8 frames per second (fps) before the nvidia card kick in.)

I did a test with and without and my frames per second did really get higher (from 30-40 til 41-50 fps).

Does amd's fusion engine (aka CCC) have that function?

 

I believe he is talking about the "maximum pre rendered frames" option that the nvidia control panel and some games (like BFBC2, although it is called the renderaheadlimit) have. It says how many frames the CPU can pre render while waiting for the GPU to do its frames. Using too high of a number can lead to input lag.

Unfortunately AMD CCC does not have this option, but I believe some tools like ATI tray tool have it, but they call it "flip queue size."

 

Thanks for the tip and for the correction I find the idea good however. I didn't get any negative side-effect.

 

This part still doesn't make any sense. Think about it. The cpu produces 8 frames per second before the nvidia card kicks in? Did you mean it produces 8 frames or 8 frames per second?

Draw out on a timeline what you mean. Do you mean that your nvidia card isn't being activated unless your frame RATE is above 8 frames per second? Do you mean that your cpu produces 8 frames for each frame your GPU produces? That would be totally different. Whatever you mean, are you sure? How are you quantifying this?

 

Doesn't make much sense either since 3D Games aren't rendered by the CPU...

But AMD does has the flip queue which just says how many frames are rendered before being displayed on screen. And as said before this leads to input lag so leaving it on default is recommended.

 

the CPU does a considerable amount of work on each frame (no where near the amount the GPU does). Even though GPU's have some general purpose capability these days, the GPU still has highly specialized hardware meant for rendering. The CPU has to set up everything for the GPU, and then the GPU blasts through the bulk of the rendering process. For each frame the GPU renders, it requires the CPU to do some work in advance.

TL;DR: For each shot fired, the CPU has to load the gun and pull the trigger.

There is still a ton of stuff that doesn't make sense. First off, the whole "per second" thing isn't related to what's happening in the hardware. Second, neither the GPU nor the CPU should be idle for longer than a single frame. Basically, if the CPU is done with frame 1, but it isn't rendered yet, then it may be allowed to move on and start working on frame 2, depending on the game and driver settings. It might even be allowed to start working on frame 3,4,5, etc. if it finishes and frame #1 still isn't done. Even if the CPU is allowed to go ahead 8 frames, the GPU would start working right after the CPU finishes frame #1. It's not like the GPU waits for 8 frames from the CPU and then starts working. In general, the CPU might be able to get a frame or two ahead of the GPU (never behind, the CPU work is prerequisite for the GPU to start), but regardless, nothing will be idle for 8 frames. If the CPU is allowed to render ahead 8 frames, and it gets to 8 ahead, then the CPU might go idle (granted, it has plenty of other work to be doing as well). The GPU might go idle if it finishes a frame quickly and the CPU isn't yet done with the next frame (because it's handling a lot of other stuff), but because a complete frame requires the GPU to complete it's job, the maximum amount of time the GPU could theoretically be idle is less than 1/framerate (seconds)

 

Nvidia only says 8 frames.

Thanks for the last post of explanation.