Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Has AMD Destroyed DLSS 3? - FSR 3 Frame Generation Analyzed
Has AMD Destroyed DLSS 3? - FSR 3 Frame Generation Analyzed
Tim: "competitor tech, it just works"
VRR pretty much confirmed to not be working now either, amd really should not have released FSR 3 until that was working. Hopefully they can resolve the issues quickly.
Time to head over to amd reddit and grab the popcorn.
Watched the video but as expected FSR3 has early launch teething problems primarily being the VRR not working and Vsync must be on.
Tim says that AMD appear to have a newer version of FSR3 as described in the GPUOpen blog but launched an older version in the first two games. That kind of marketing failure is unforgivable imo. Whoever is head of marketing should be removed asap. Why did they not just wait for the proper working version before releasing it???
It's funny that he rolled out the meme
HUB have often made fun and rightly so of the meme "it just works - Jensen" but Tim unironically in the video says compared to fsr3, dlss3 just works, and work with any configuration you want vsync on or off, gsync on or off, VRR on or off, and any framerate or refresh rate or cap, any combination as well and delivers better visuals, smoother frames, and lower latency
He did not say that vrr was working once you get close to display’s refresh rate and only said that frame pacing is much better.However, what Tim revealed in the HUb video is that if your framerate is within around 20fps of your refresh rate then perceptually VRR will work ok and you will see decent framepacing and smoothness. This is what was going on with my tests I think!
Watched the video but as expected FSR3 has early launch teething problems primarily being the VRR not working and Vsync must be on.