← Tech
💻Tech

GTA 6 on PS5 With DLSS 5 via Capture Card and Veyra: The Proposed Setup Explained

GTA 6 isn't out until Nov 19. Here's how the proposed PS5 → capture card → Veyra AI pipeline works, what you need, setup steps, input lag trade-offs and limits.

T Terapep ·

TL;DR: A Reddit proposal covered by Ars Technica on Nov 5, 2026 routes a PS5 through a 4K capture card into a PC, runs the picture through the open-source app Veyra (AI super resolution, "neural rendering" and frame generation), then sends it back to the TV. GTA 6 isn't out yet: it launches on PS5 on Nov 19, 2026, with pre-load starting Nov 10. Nobody has tested this setup with GTA 6. Veyra works on the finished video image. It isn't Nvidia's native, in-game DLSS 5, and it adds input lag.

What the setup actually is

According to Ars Technica, Reddit user RevolutionaryBus8208 proposed this chain:

PS5 → 4K HDR capture card → PC running Veyra (RTX GPU) → 4K TV

To show what it might look like, the poster ran Veyra over the August GTA VI Extended Look trailer. Frame generation took the 30 fps source to 90 fps. Ars said the result looked sharper in places, with better shadows and light scattering. It also said blacks looked washed out, and some scenes picked up a "soap opera" smoothness and frame-gen artifacts.

Important: the poster said they don't own a capture card. They didn't test the setup with a real PS5. The figure of about 11 ms of added latency is their own claim, not a measurement from a console.

Native DLSS 5 vs this passthrough (what's different)

Native DLSS 5 in a PC game PS5 → capture card → Veyra
What gets processed Game render data (engine-integrated) Finished video frames from the console
Official Nvidia support Yes, per supported game No. Community runtimes, and the developer says they aren't vendor-certified
Input lag Part of the game's render pipeline Adds capture + processing + display time on top of the console
UI/HUD handling Engine knows what the HUD is Treats the HUD as part of the image (Veyra has an NR "protection region" to work around this)
Available for GTA 6 No PC version yet (reported for early 2027) Possible in theory from Nov 19 on PS5

Requirements (from Veyra's README)

  • Windows 11 x64 + DirectX 12. Veyra is a C++ app licensed under GPL-3.0 and comes as a portable zip.
  • An NVIDIA or AMD GPU. Download the package for the GPU you actually use (NVIDIA or AMD). The README's own tests mostly ran on an RTX 5070. Its NR (neural rendering) runtime options include "RTX 50 · NVIDIA original", "RTX 50 · Lecram", "RTX 20–50 · SF-v2" and an experimental AMD RX 9000 runtime.
  • A capture card that handles your target signal. For example, 4K60 HDR passthrough if you want 4K. A PCIe card is a safer choice than USB. The README specifically mentions Magewell Pro Capture (low-latency option), Elgato color compatibility, and opt-in Blackmagic native capture.
  • Headroom. Higher resolution, stacked NR layers and frame generation all increase GPU/VRAM load. The README says that long-run VRAM growth on NVIDIA is unresolved.

Step-by-step (proposed setup)

  1. PS5 HDMI out → capture card input. Connect the card's passthrough output (if it has one) to the TV as a fallback for zero-lag play.
  2. PC output → TV on a second HDMI input. This is the "enhanced" feed.
  3. On the PS5, turn off Enable HDCP (Settings → System → HDMI). Capture cards can't record an HDCP-protected signal. HDCP has to be on for streaming apps like Netflix.
  4. Download the latest Veyra NVIDIA or AMD portable zip from the GitHub repo. Extract it to a new folder and run veyra_qml_ui.exe.
  5. On Veyra's Home screen, pick Capture card. Select the device, then resolution, then refresh rate, then pixel format and audio input. Close any other app that's using the card (OBS, Elgato software).
  6. Match the color settings to the signal: HDR10/PQ vs HLG vs SDR (Rec.709), and Limited vs Full range. A mismatch is the usual cause of washed-out blacks.
  7. Start with every effect off. Check that picture and sound work, then turn effects on one at a time: SR first, then one NR layer, then frame generation last.
  8. For frame generation, choose the backend and multiplier, then check cadence, display sync and the low-queue mode. The README warns that "submitted FPS" is not the physical display FPS or the end-to-end latency.
  9. Use the NR protection region to keep the HUD, minimap and subtitles from being altered.

No capture card? Veyra can also take a PS5 feed over Remote Play. You need your PSN account ID and the console's eight-digit pairing code. This route adds network latency and compression, though.

Trade-offs to expect

  • Input lag: A pure passthrough card adds almost nothing, but capture, AI processing and frame generation all stack delay on top. Commenters who've tried similar setups called it "noticeable but tolerable". One claimed 1–2 ms, which Ars called impossible to believe.
  • Frame generation on a 30 fps source: The extra frames are interpolated. They don't respond to your controller, so it looks smoother than it feels.
  • Artifacts: Expect them around fast motion, limbs and fences (the README admits this), plus over-smoothed motion.
  • Cost: You need a capable RTX/RDNA4 GPU, a good capture card, and a PC that stays on alongside the PS5.

Should you bother?

  • PS5 Pro owners already get PSSR upscaling. Adding Veyra stacks a second AI pass on top.
  • Base PS5 owners with a strong RTX 50 PC might find it a fun experiment for slow-paced play and photo mode. It isn't a fit for competitive or fast-reaction content.
  • Everyone else may be better off waiting for the reported early-2027 PC release, which should get proper in-engine upscaling.

Sources

#gta-6#dlss-5#veyra#ps5#capture-card#frame-generation
← Back to all posts