An experiment has emerged that routes the PS5 version of Grand Theft Auto VI (GTA VI) through a PC, applying NVIDIA's DLSS 5 neural rendering and frame generation. Likely7AI, the developer of the video-processing software Veyra, has released a demo that applies neural rendering and RTX HDR to GTA VI footage and outputs it at 120fps. Another developer, Phosphenq, has published setup instructions for processing PS5 footage on a PC, along with measurements showing the frame rate rising from 29.5fps to 59.0fps. In this setup, the game itself still runs on the PS5, while the PC alters the look of the incoming video and generates intermediate frames. It does not raise the PS5's rendering performance, but it may improve image quality and display smoothness without modifying the game.

AD

How PS5 footage is processed on a PC and output at 120fps

Veyra, the software used in this experiment, is a GPU video-processing application for Windows. It accepts not only local video files but also capture-card and game-streaming input, and can apply neural rendering, super-resolution, HDR processing and more. It supports Windows 11 x64 and DirectX 12, and can add frame generation as the final stage of its live preview.

The configuration guide Phosphenq published on GitHub describes how to send video to a PC using the PS5's Remote Play feature. After enabling Remote Play on the PS5, you connect from Veyra and set the streaming quality to 1080p at 60fps and the video codec to H.265. Capturing HDMI output with a capture card is also supported. In either case, the PC processes the video the PS5 has rendered and then displays it on the monitor.

In a demo video on YouTube, Veyra creator Likely7AI shows a setup that combines neural rendering and RTX HDR with GTA VI footage and outputs it at 120fps. This 120fps is an output value that includes frame generation on the PC side; it does not mean the PS5 is rendering the game at 120fps.

On Reddit, u/THZpr0 has also posted a video titled "GTA 6 DLSS5 1 PASS FG X6". However, "FG X6" in the title is the poster's own notation for their settings and is separate from the measurements Phosphenq published. The processing methods and frame-generation multipliers used in each demo need to be kept distinct.

GTA VI footage from 29.5fps to 59.0fps, including generated frames

The key to understanding what frame generation does here is the difference between the frame rate of the input signal and the number of frames whose content actually updates. According to Phosphenq, when 30fps GTA VI footage is received from the PS5 as a 60fps signal, identical images are repeated. Although 60 frames per second are sent as a video signal, the game has newly rendered only about 30 images.

Veyra 2.1.6 and later includes a feature that automatically removes such duplicate frames. It strips the repeated images from the 60fps input, treats the result as roughly 30fps video, and then applies frame generation. If frame generation were applied with the duplicates still in place, intermediate frames would be generated between identical images, which can make motion look unnatural.

To confirm this difference, Phosphenq analyzed about 41 seconds of PS5 footage. The recording contained 2,475 frames in total, but after removing duplicates it came to 1,245 frames, meaning the actual video update rate was 30.1fps. The 1% Low frame rate was reported as 25.7fps. The measurements used the script Phosphenq published and Veyra's counter.

Phosphenq also published a measurement using about 80 seconds and 14 scenes of PS5 Pro footage released mainly by IGN, and another using about 30 seconds of footage from Digital Foundry. The GitHub README lists the following results.

Footage used Frames / rate before processing Frames / rate after processing
Mainly IGN PS5 Pro footage, about 80 seconds, 14 scenes 2,351 frames, 29.5fps 4,700 frames, 59.0fps
Digital Foundry PS5 Pro footage, about 30 seconds 863 frames, 28.8fps 1,723 frames, 57.4fps

Figures published by Phosphenq. Frame counts are totals after duplicate removal; post-processing counts include generated frames. Footage lengths are approximate, and fps values follow the author's notation.

In the roughly 80-second footage, the 2,351 frames before processing became 4,700 afterward, nearly doubling the output frame rate from 29.5fps to 59.0fps. The Digital Foundry footage also rose from 28.8fps to 57.4fps. By generating intermediate frames, the movement of objects and the camera can be displayed at finer time intervals.

However, some of the added frames are generated by the PC and were not newly rendered by the PS5's game engine. These figures reflect an improvement in video output that includes frame generation.

AD

About 12ms of video processing on an RTX 5080, separate from input latency

Phosphenq also published processing times when using a GeForce RTX 5080. In a configuration combining two layers of neural rendering, video stabilization and 2x frame generation, the total PC-side video processing time was about 12ms per frame.

Process / metric Author-published value Conditions / details
Neural rendering 4.1ms per layer 2 layers used
Frame generation 1.5ms 2X setting
Optical flow 2.1ms Estimates motion between consecutive images
Total PC video processing About 12ms per frame RTX 5080, including the above and video stabilization
Output frame rate 60.0fps, 1% Low 56.3fps Values during live processing
GPU utilization 39% Author-reported, same configuration

The target of measurement differs from the frame counts tallied from recorded files. The 4.1ms for neural rendering is per layer.

The roughly 12ms figure represents the time needed to apply the various processes to the video the PC receives. It is not the total delay from controller input to the result appearing on screen.

When using Remote Play, several steps are needed before an input is reflected on screen. The PS5 accepts the input, the game engine renders a new frame, and the video is encoded and sent to the PC. The PC then decodes the incoming video, applies neural rendering and frame generation, and outputs it to the display. The time taken by this whole chain of processing and communication affects input latency.

Phosphenq himself acknowledges that Remote Play adds latency, and explains that raising the video frame rate does not change the fact that the game's responsiveness remains equivalent to 30fps. Veyra's official README likewise treats the frame rate the app outputs, the frame rate the display actually shows, and the delay from input to display as separate metrics.

In other words, even if frame generation makes on-screen motion smoother, responsiveness to input does not improve by the same proportion. Interpolating video improves display smoothness, but processing time and frame buffering can also add latency.

Note that the roughly 12ms processing time and the 60.0fps output value are figures published by Phosphenq; the editorial team has not performed hardware measurements or re-analyzed the recorded data. Independent verification, including the exact recording length, the criteria for detecting duplicate frames and how the 1% Low was calculated, has not been carried out, and no measured value for total delay from input to display has been presented.

DLSS 5 neural rendering and frame generation are separate technologies

To understand this experiment, it is necessary to distinguish between DLSS 5's neural rendering and frame generation.

In a developer blog post dated September 22, 2026, NVIDIA explains that DLSS 5 neural rendering generates one output frame from one input frame. It uses a trained AI model to improve the look of lighting and materials based on the video the game engine has rendered, and its purpose is not to increase the number of frames itself.

Frame generation, by contrast, is a technology that inserts new images between consecutive frames to increase the number of frames displayed. Veyra combines the two as separate processes.

The information available also differs between NVIDIA's game-engine DLSS 5 and Veyra's external video processing. According to a technical explanation published September 1 by NVIDIA's research group ADLR, official DLSS 5 uses as inputs the current frame generated by the game engine, along with motion vectors, past temporal state and rendering settings specified by developers.

Veyra, on the other hand, processes finished video sent from the PS5. Because it does not directly receive the engine's internal rendering information, its processing conditions differ from an official DLSS 5 integration.

Comparison item NVIDIA's official DLSS 5 integration Veyra external video processing
Input video Frames rendered by the game engine Video files, capture cards, game streaming
Motion information Uses engine motion vectors and temporal state Processes based on video received externally
Appearance adjustment Developers control the model, intensity and target area Users select processing settings within the app
Frame generation DLSS 5 neural rendering itself is 1 input, 1 output Frame generation can be added separately as a final stage

Comparison based on NVIDIA's official materials and Veyra's developer documentation. The specific way motion information is supplied inside Veyra could not be confirmed.

Official game integrations are designed to use motion vectors and similar data to maintain consistency between frames and preserve the rendering result developers intend. Because Veyra takes finished video as input, it can process footage without DLSS 5 being built into the game, but it cannot directly use the information the game engine holds.

The processing method also differs depending on the supported GPU. In the recommended settings Phosphenq published, GeForce RTX 50 series cards use two layers of "NVIDIA original," NVIDIA's neural rendering implementation, while RTX 20 to 40 series cards use one layer of "SF," a community implementation.

For the RTX 50 series configuration, Phosphenq explains that it loads "nvngx_dlssnr.dll 310.8," an NVIDIA-signed neural rendering runtime. However, the integration into Veyra is itself a community effort, and it is not a GTA VI DLSS 5 implementation officially certified by NVIDIA.

Frame generation is also set separately from neural rendering. Phosphenq lists 2X for RTX 50 and 40 series cards and 4X for 120Hz displays as options. For RTX 30 series he recommends 2X in compatibility mode, while for RTX 20 series frame generation is disabled. Veyra's author likewise advises users to check the conditions for each setup, since supported features and multipliers vary by GPU and frame-generation backend.

This attempt shows that neural rendering and frame generation can be applied to PS5 footage on the PC side without modifying the game itself. The improvement from 29.5fps to 59.0fps and the 120fps output demo are gains in display smoothness that include generated frames. To judge how well it suits actual gameplay, it will be necessary to evaluate, in the same configuration, not only image-quality comparisons with the original footage but also the delay from input to display and the visual artifacts that appear in fast-moving scenes.