NVIDIA Smooth Motion Unofficially Available On GeForce RTX 40 GPUs; PUBG Sees Around 60% FPS Improvement

RTX 40 series GPU owners can turn on the Smooth Motion feature early with the preview driver 590.26 and enjoy higher frame rates on their systems.

NVIDIA's Smooth Motion, which is currently supported on the GeForce RTX 50 series GPUs, might take some time before getting official support for the GeForce RTX 40 series GPUs. Smooth Motion is similar to AMD's Fluid Motion and doesn't require DLSS integration by developers. While not as good as the Frame Gen or Multi-Frame Generation techniques, Smooth Motion is still a good alternative for enhancing gaming performance in titles at the driver level.

The GeForce Driver 590.26 Preview Driver has been out for a few days now, and while you need to have an official developer NVIDIA account to access it, you can still get it from and install it via the instructions provided in the notes, followed by downloading the to enable Smooth Motion. As per the page, this is the first driver to support GeForce RTX 40 series but it's in the Preview state, which means stability isn't guaranteed, but checking different reports, we can see that numerous users have started gaining performance boost.

One of the latest is the PUBG benchmark uploaded by the YouTube channel, which showcased the difference between the performances with and without NVIDIA Smooth Motion on his GeForce RTX 4070 Ti. We can see the frame rates going from double digits to triple digits easily, offering up to a 60% performance boost. The render latency did see a small increase, but it wasn't too noticeable, while the higher frame rates provided a smoother gameplay experience.

Some users have reported a similar performance boost in games like Deep Rock Galactic Survivor, but on the flip side, there are reports of bugs and performance drops depending on the title. This is due to the unstable release, and for some, the feature didn't turn on. Some suggested updating the RTSS to v7.3.7 Beta 6 if they have MSI Afterburner installed on the system to fix this issue, and it's important to follow the exact instructions listed on this thread.