Skip to content
Project ZomboidViewpoint survival notes

Graphics

Viewpoint FSR, XeSS and DLSS: diagnose blur before boosting FPS

Build 42.21 · Viewpoint alpha-0.1.6 · Sources checked October 11, 2026

The short answer

Establish a native-resolution baseline before enabling experimental FSR 3, XeSS or DLSS. Compare one available option at a time in the same scene. The release notes require additional in-game setup for supported frame-generation configurations; they do not provide a universal toggle or GPU support matrix.

On this page

Four settings that solve different problems

LayerWhat to compare
Output resolutionKeep the game’s display resolution unchanged across the test.
Anti-aliasingEvaluate edge shimmer and motion separately from output resolution. The new release lists MSAA, SSAA, FXAA and TAAU.
UpscalingLook for loss of fine detail or trailing during motion in the experimental FSR 3, XeSS or DLSS path available on your setup.
Frame generationCompare responsiveness as well as displayed smoothness; more displayed frames do not establish a cure for input delay.

Run a comparison you can interpret

  1. Record the GPU, driver, core version, resolution, preset and currently enabled reconstruction options.
  2. Open Delete and use the installed graphics menu. Establish a comparison with experimental upscaling and frame generation disabled; preserve a note of your original settings.
  3. Walk the same short route and inspect fences, text, thin objects and moving edges. Keep weather, camera and model distance fixed.
  4. Enable one supported option through its actual in-game controls. Compare image clarity and input response, then keep it or restore the baseline.

Missing option, new setup warning or unstable output

Do not download a random replacement DLL to force an unavailable mode. The author lists DLAA specifically for supported NVIDIA RTX cards, and warns about Intel Arc and macOS during setup. That is not proof of support for every DLSS or frame-generation combination.

The new wizard requires Texture compression and a restart on graphics cards with less than 12 GB of video memory. Follow the warning shown by your installed wizard; reducing one visual effect does not substitute for completing its required restart.

If an experimental option crashes or produces artifacts, disable that option and reproduce with the baseline. See the wider blur and slowdown flow when the problem remains without it.

Watch a version-specific preset comparison

WhiteZet’s alpha-0.1.6 video labels its Ultra/TAA, Extreme and Vanilla sections. Use it to recognize the update’s appearance, not as a benchmark for your hardware or a complete upscaling installation guide.

What remains unverified

We have not benchmarked these modes or validated a complete GPU compatibility list. Include the original and changed settings, an image or short clip, and console.txt in an author report. A named feature in the release notes is not a guarantee that it is available on your machine.

Sources & version

Based on author documentation and community instructions, not our own gameplay test. Later updates may change defaults.