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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Add comment