iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Start by turning Frame Generation off. If the HUD immediately becomes stable, the defect is in frame interpolation, UI separation, or the injected wrapper—not necessarily in DLSS Super Resolution itself. If the problem remains, compare native resolution, DLAA or the game’s normal anti-aliasing, and DLSS Quality with sharpening disabled. Shimmering, ghosting and a warped HUD have different causes, so each needs a different fix.
Older games are especially dependent on how their renderer supplies motion vectors, depth, exposure, camera-reset information and separate UI buffers. A newer graphics card cannot reconstruct inputs the game never provides. When those inputs are missing or malformed, native resolution, DLAA/TAA or a conventional spatial scaler is often the correct solution.
Identify which DLSS problem you actually have
Use the visible symptom to choose the first test instead of changing several settings at once. Capture a repeatable scene—thin railings, foliage, text, a character walking across the screen and a HUD element—and compare the same camera movement after each change.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems| Symptom | What it looks like | Most useful first test |
|---|---|---|
| Shimmering or flickering | Thin geometry, wires, foliage, text or fine textures sparkle, crawl or change detail as the camera moves. | Raise the internal render resolution to DLSS Quality or DLAA, then remove external sharpening. |
| Ghosting or smearing | Moving characters or objects leave trails, soft duplicates or a dragged edge behind them. | Disable Frame Generation. If the trails vanish, investigate motion vectors, depth, exposure, camera resets and the frame-generation path. |
| Duplicated, warped or shaking HUD | Health bars, subtitles, crosshairs or menus appear twice, wobble, stretch or trail while the 3D scene looks reasonable. | Disable Frame Generation and check whether the game or wrapper separates a Hudless scene buffer from the UI buffer. |
| Garbled image after a cut or teleport | The whole frame briefly breaks up, becomes blurry or shows unrelated fragments after a camera jump. | Retest with Frame Generation off and check camera-reset and exposure handling. |
These symptoms can occur together. Fix the lowest-level problem first: establish a clean baseline, then address reconstruction quality, then test interpolation and UI composition.
#1 Best Overall
- AI Performance: 767 AI TOPS
- OC mode: 2632 MHz (OC mode)/ 2602 MHz (Default mode)
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Axial-tech fan design features a smaller fan hub that facilitates longer blades and a barrier ring that increases downward air pressure
- A 2.5-slot design maximizes compatibility and cooling efficiency for superior performance in small chassis
Make a clean, reversible baseline
Before replacing a DLL or enabling an injected feature, preserve the original state. Retro games often use old configuration files and libraries that are difficult to recover from memory.
- Back up the game’s original DLLs and configuration. Copy the relevant files to a separate folder and note the game version. Include any DLSS library, wrapper files and configuration profiles you have added.
- Disable Frame Generation. Turn it off in the game first. If it is supplied by a wrapper, disable that wrapper’s frame-generation option rather than leaving a second path active.
- Disable injected wrappers and overlays. Temporarily remove OptiScaler or another injection layer from the test. Turn off performance overlays and capture tools so they cannot alter presentation or timing.
- Disable sharpening. Set both the game’s sharpening control and any driver or overlay sharpening filter to zero or off.
- Run the game at native output and its normal anti-aliasing mode. Record whether the original renderer already shimmers, ghosts or distorts the HUD. This is the reference image for every later comparison.
- Test DLSS Quality without Frame Generation. Change only the upscaler and repeat the same camera movement.
- Test DLAA separately. DLAA uses the DLSS anti-aliasing path at the display resolution instead of reducing the internal resolution. It is useful when the GPU can maintain the target frame rate and gives you a cleaner comparison with a lower-resolution DLSS mode.
Do not judge a setting from a menu animation alone. Test gameplay, a camera pan, a fast-moving character and a scene with fine geometry. Note the API (DirectX 11, DirectX 12 or Vulkan), game build, wrapper version, DLSS library version, GPU, display resolution and whether Frame Generation is native or injected. That record makes it possible to undo one change without losing the working baseline.
How to reduce DLSS shimmering
Shimmering is usually temporal instability: the reconstruction is trying to decide which subpixel details belong in the current frame, but the internal image or the temporal inputs do not contain enough reliable information. Thin geometry and high-frequency textures expose the problem first.
Use a higher internal render resolution
Test the modes in this order:
- Move from Performance or Balanced to Quality. Quality gives DLSS more source pixels and is the quickest way to determine whether the problem is simply an overly low internal resolution.
- Try DLAA. If DLAA is stable and your GPU can hold the desired frame rate, it is the most direct way to keep the display resolution while retaining the DLSS anti-aliasing method.
- Use a custom input-resolution override only when the game supports it. The NVIDIA App exposes per-title DLSS controls, including DLAA, Ultra Performance and custom input-resolution overrides. Raise the input resolution gradually and save the setting for that game rather than applying a global override.
A higher input resolution can reduce crawl on foliage, wires and text, but it costs performance. Change one title at a time and keep a note of the original value so a future driver or game update does not leave you wondering which override is active.
Remove sharpening before judging stability
Sharpening does not create valid temporal data. It can, however, exaggerate small changes between reconstructed frames, making a stable image look more aggressive and an unstable image look like sparkling edges. Turn off external sharpening first, then evaluate the scene at its normal viewing distance. Re-enable a mild filter only after the shimmer is under control.
Compare against a non-temporal path
Switch from DLSS to native resolution and then to a conventional spatial scaler if the game provides one. If native resolution is clean while DLSS shimmers, the issue is not your monitor: the game’s temporal inputs or the chosen internal resolution are insufficient for that renderer. A spatial scaler may look less detailed, but it avoids temporal accumulation and can be the better choice for a title that cannot supply reliable motion data.
Rank #2
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5060
- Integrated with 8GB GDDR7 128bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
Check renderer integration limits
NVIDIA’s Streamline integration guidance identifies incorrect or missing jitter as a cause of poor anti-aliasing and increased flickering. Improper exposure can also increase flickering as well as ghosting. These are engine-level inputs. Changing to a faster GPU, forcing a different DLSS DLL or increasing sharpening cannot repair a renderer that sends the wrong jitter or exposure information.
How to stop DLSS ghosting and smearing
First determine whether the trails come from Super Resolution or from frame interpolation.
Use the Frame Generation switch as an isolation test
- Leave your stable DLSS Super Resolution mode enabled.
- Turn Frame Generation off completely.
- Repeat the same movement through a scene that produced trails.
- Turn Frame Generation on only after the image is clean with it disabled.
If the trails disappear when Frame Generation is off, concentrate on the interpolation path and its inputs. If they remain, investigate the game’s motion vectors, depth, exposure and temporal history even when using Super Resolution alone.
Check the inputs that interpolation needs
NVIDIA lists incorrect inputs as causes of blurry or smudged objects, increased ghosting, disjointed characters, flickering UI and generally garbled images. In an older title, the likely failure points are:
- Motion vectors: They must describe how scene pixels move between frames. A vector that includes the wrong object, uses the wrong scale or is missing for animated geometry can produce trails.
- Depth: The depth buffer lets reconstruction distinguish near and far surfaces. A missing, reversed or incompatible depth buffer makes disocclusions difficult to resolve.
- Exposure: Stale or incorrect exposure values can make consecutive frames disagree about brightness and increase both ghosting and flicker.
- Camera resets: A cut, teleport, respawn or abrupt field-of-view change requires the temporal history to be reset. If it is not, old pixels can be dragged into the new view.
- Motion blur: Excessive in-game blur can look like DLSS ghosting. Disable it temporarily to separate the game’s optical effect from reconstruction trails.
When a wrapper cannot obtain these resources in the format it expects, the artifact is an implementation limitation, not a quality setting that can be solved by changing from Quality to Performance.
Recommended Free Tools
Update carefully, with a rollback copy
After saving the original files, update the NVIDIA driver and the game’s DLSS library or wrapper one component at a time. Retest after each change. Use per-game overrides in the NVIDIA App before trying a global override; a global setting can alter unrelated titles and make the comparison harder to interpret. If the update introduces a crash, black screen or new trails, restore the backed-up DLLs and configuration before testing another variable.
Rank #3
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5070 Ti
- Integrated with 16GB GDDR7 256bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
How to fix a duplicated, warped or shaking HUD
A HUD-only defect is a strong clue that the interface is entering the temporal or interpolation path with the world scene. NVIDIA’s Streamline guide states: “For the best image quality, it is critical to provide a Hudless (pre-UI) buffer and a UI buffer.” The Hudless buffer is the scene before HUD drawing; the UI buffer contains the interface. With both available, the scene and interface can be interpolated or reconstructed separately and composited at the end.
Disable interpolation at unstable presentation points
Manually disable Frame Generation in pause screens, menus, loading screens and while changing resolution or window mode. NVIDIA notes that automatic menu detection can miss cases, so a manual switch is preferable when the title exposes one. Test the HUD during normal gameplay after returning to the same resolution and display mode.
Put the HUD after the upscale or interpolation pass
Some games expose an option such as UI before/after upscaler or a Frame Generation HUD setting. Choose the path that draws the HUD after the upscale and interpolation stage. This keeps fixed, screen-space elements from being treated as moving world pixels. The DLSS programming pipeline places post-processing at display resolution and then draws UI/HUD, which is why a HUD rendered inside the reconstruction path can warp or duplicate.
Configure an injected wrapper conservatively
If you use OptiScaler OptiFG, check its incompatible-game list before changing settings. Its HUDFix can work only when the detected-UI mask identifies the HUD rather than the world. Enable HUDFix after confirming the mask on a static scene, then test a moving scene with subtitles, bars and crosshairs. Keep the rollback copy nearby.
OptiScaler describes this route as experimental and warns about hangs, boot crashes, runtime crashes, overlay conflicts and incomplete interpolation. It also notes that without a Hudless resource, generated frames can cause HUD ghosting or garbling. If HUDFix cannot isolate the interface, disable the wrapper instead of accepting a broken HUD.
Retro-game and wrapper compatibility checklist
Use this checklist before spending time on increasingly aggressive overrides:
Rank #4
- Powered by the NVIDIA Blackwell architecture and DLSS 4 OC mode: 2640MHz/Default mode: 2610MHz (Boost Clock)
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.125-slot design with massive fin array optimized for airflow from three Axial-tech fans
- Phase-change GPU thermal pad helps ensure optimal thermal performance and longevity, outlasting traditional thermal paste for graphics cards under heavy loads
- Write down the rendering API: DirectX 11, DirectX 12 or Vulkan.
- Record the exact game version, wrapper version and DLSS DLL version.
- Record GPU model, output resolution, window mode and refresh target.
- Identify whether Frame Generation is native to the game or injected.
- Disable overlays and reproduce the issue with a clean launch.
- Test one variable at a time: native or normal anti-aliasing, DLSS Quality, DLAA, Frame Generation off, then Frame Generation on.
- Check whether the wrapper changes input or overlay behavior. OptiScaler notes that OptiFG may disable Steam, RTSS, Ubisoft, EA App and Overwolf overlays and can affect Steam Input.
- After every change, test a gameplay camera pan, a fast character, fine geometry and the HUD.
Do not infer compatibility from the fact that a wrapper starts successfully. A title can boot and render a scene while still lacking valid depth, motion vectors, exposure, camera-reset data or Hudless/UI buffers.
Free tools Windows power users keep installed
One-click scans. No signup required.
Choosing the right fallback
The best option depends on whether you value image stability, frame rate or experimental interpolation. The table describes the practical trade-offs for older games; it is not a benchmark and does not promise identical results on every engine.
| Option | Thin-detail stability | HUD correctness | Input latency and frame rate | Compatibility and risk |
|---|---|---|---|---|
| Native resolution with the game’s normal anti-aliasing | Provides the cleanest reference for diagnosing shimmer. | Usually follows the game’s original UI path. | Highest rendering cost; no generated frames. | Most reversible and least dependent on wrapper inputs. |
| DLAA | Often cleaner than a low internal-resolution DLSS mode when the renderer’s temporal inputs are sound. | Does not by itself solve a HUD that is sent through a broken interpolation path. | Uses display-resolution rendering, so performance demand is high; no Frame Generation required. | Good diagnostic and fallback choice when the game exposes it. |
| DLSS Super Resolution Quality | More stable than Balanced or Performance when internal resolution is the limiting factor. | Depends on the game’s UI composition. | Lower rendering cost than native; no generated frames unless separately enabled. | Generally the first performance mode to test. |
| DLSS Super Resolution Balanced or Performance | More likely to reveal shimmer on wires, foliage and text because fewer source pixels are available. | Still depends on correct UI handling. | Higher potential frame rate at the cost of source resolution. | Useful only if the image remains acceptable; easy to reverse. |
| Injected Frame Generation | Can expose temporal-input errors that are invisible with Super Resolution alone. | Highest risk of duplicated or warped HUD without clean Hudless/UI separation. | Can increase displayed frame rate, but interpolation can add latency and artifacts. | Most dependent on API, wrapper and overlay compatibility; experimental paths can crash or hang. |
| Conventional spatial scaler | Avoids temporal shimmer, although it may look less detailed. | Usually leaves the original UI path intact. | Performance depends on the scaler and chosen resolution. | Useful fallback when the renderer cannot provide valid temporal inputs. |
A practical decision path
- Need a trustworthy reference? Use native resolution or the game’s normal anti-aliasing with Frame Generation off.
- Only thin details shimmer? Try DLSS Quality, then DLAA, and keep sharpening disabled while comparing.
- Trails vanish when Frame Generation is off? Leave it off unless the wrapper or game can provide correct motion vectors, depth, exposure and camera resets.
- Only the HUD is wrong? Look for a native UI-after-upscale option or a valid Hudless/UI split. If the wrapper cannot isolate the HUD, remove the wrapper.
- Native is clean but every temporal mode fails? Use native, DLAA/TAA or a spatial scaler. The title’s renderer is the limiting factor.
- Nothing is stable after an update? Restore the backed-up DLLs and configuration, then repeat the baseline procedure before trying another version.
Common mistakes that make artifacts harder to diagnose
Changing several temporal settings together
Switching resolution, DLSS mode, sharpening, Frame Generation and a wrapper in one restart hides the cause. Return to the baseline and change one item per run.
Leaving a global driver override enabled
A global override can affect other games and make an apparently fixed title look different after you switch applications. Prefer a per-title profile and record the original value.
Testing only menus
Menus may use a different render path from gameplay. Verify the same moving scene, camera cut and HUD elements that exposed the original problem.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Assuming a new GPU repairs old renderer data
DLSS can only use the data supplied by the game or wrapper. Missing depth, malformed motion vectors, stale exposure and absent Hudless/UI buffers remain integration defects regardless of GPU speed.
Ignoring rollback and overlay side effects
Injected frame-generation paths can alter overlays, input and startup behavior. Keep original files, test with overlays disabled and remove the wrapper when it causes crashes or cannot produce a correct UI mask.
What a successful fix looks like
A successful configuration has a repeatable result: fine geometry remains stable during a camera pan, moving objects do not leave trails, and HUD elements stay fixed and legible through gameplay and camera cuts. It also survives a clean restart without relying on an undocumented global override. If only a lower-quality mode or injected wrapper produces the desired frame rate but introduces visible HUD or ghosting defects, choose the stable fallback rather than treating the artifact as unavoidable.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
