Search Issue Tracker
Active
Votes
1
Found in
2021.2.4f1
Issue ID
1385924
Regression
No
DLSS increases cost of ALL GPU operations, mostly motion blur/LensFlare/FixedExposure by upwards of 5-8x perf increase.
Re-opened the bug since I managed to repro on 2021.2.10f1.
Basically the repro steps are simple, just not 100% of the time:
- Retrieve the project
- Open Profiler, under profiling modules, add GPU usage
- Select the new GPU section
- Here search for MotionBlur pass
- Press Play
- Enable / Disable DLSS and see the 5 folds increase of the GPU cost of the pass.
Additional info:
- If does not happen, quit turn unity off and on again.
- Does not seems to happen with other DRS filters.
It also happens on different passes like LensFlareDataDriven / Bloom as per user reports.
Forum thread: https://forum.unity.com/threads/dlss-increases-motion-blur-other-perf-costs-by-over-5x.1206709/
Also, it reproes on trunk as well.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Add comment