So its literally just an ultra dynamic over/underclocker. Does the same thing Boost modes do, just is constantly doing it instead of being boosted the moment the game starts.
Yeah, this is going to be a buggy mess. Plus likely will be some latency as it decides if and when to clock up. Try again AMD.
Last time I used Dynamic Frame Rate Control, it didn't overclock or underclock core frequencies. Personally, I think a lot of repliers on this threads have misunderstood and generalize the context of what AMD_Peter was trying to say. Simply, without the b.s., he is just stating that DFRC is going to be a new feature in the AMD CCC and Drivers. That's wonderful. I look forward to it. I honestly don't believe this has anything to do with regulating power consumptions or a counter to G-Sync as others have expressed.
Now do you truly understand what it does, NC37. It's very simple. DFRC basically (unless its been changed recently) act as a Frame Rate Lock. You pick a frame rate to lock, and whatever game you are playing, it stays at that frame rate. So say as an example, you wanted to play Planetside 2 at 100 FPS on the highest settings. Ok. So you go into RadeonPro, input 100 into the DFRC box, and click apply. What happens after that is this. You're going to see your FPS at 100 FPS. It's constant. The variants is + / - .5 fps roughly. No matter where you go, or what you do, or how many other players are in the area plus the particle effects, it's still showing an output of 100 FPS. So what's the caught. The caught is the inverse reciprocal of Framerates is Frame Time ((frames per second)^-1 = seconds per frame); QED--Ryan Shrout please take note of this because you suck at math) skyrocket from ms to seconds per frame. Frame times increase to meet the frame rates. So you're going to sit there watching your computer take more time to produce the 100 frames--plus the cpu dealing with shadows and particle effects, and you're toon could be dead in the process because you weren't able to react so fast in a 90 versus 90 plus NC-VS shet-feast of epic proportions. While your computer is trying to produce that 100 fps, you're going to be rocket-primaried to the face by an aimbotter on the NC side, and you weren't quick enough to react, even though, the output on the OST says 100 FPS.
Does it work? Yes. It works almost flawlessly, and the transition is smooth between frames. It's almost like having G-Sync without the G-Sync because you get 100% framerate uptime. So say you're only using a 60 hz display. So most likely, you're going to get 60 frames out of the 100, take a 40 frame loss, and have smooth, fluid animation without any form of screen-tearing or runt-frames at a cost of $0.00.
Now with some of the other members who have mentioned that this could be used to reduce power consumption, I can see this being true only under certain situations were you want to limit your FPS below your refresh rate throughout the game. Instead of going with 45 - 60 FPS at 98% of the game, and having those moments where it's 2% at 28FPS, this is a 6 hour play secession, you could just go with 100% 30 FPS, and you'd consume less power in the process.
I believe the goal of DFRC was really to find other ways of fixing the issue that AMD 7990 had when it was still king: Eliminate runt frames and provide a smooth, fluidic gameplay at no cost to the consumer or the manufacturers. That's good for the consumers, but that's not good for business.
Believe me. I know what I am talking about. I use to play around with DFRC on my AMD Graphic Card Rig. I don't because that rig has become my music and 3D content workstation.
50W figures while gaming but if this can slash 10% or so it would be a welcomed improvement. I guess it'll launch along the Hawaii refresh?