Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.1.0a1
2020.1.0b13
2020.2
Issue ID
1254968
Regression
No
Assertion failed on expression on selecting Direct Denoiser mode to Radeon Pro under filtering section in Lighting Window
Assertion failed on expression is thrown on selecting Direct Denoiser mode to Radeon Pro under filtering section in Lighting Window.
Steps to repro:
1. Open the attached project > Sample Scene.
2. Windows > rendering > Lighting.
3. Lightmapping Settings > Filtering > Advanced.
4. Direct Denoiser > Radeon Pro.
OR
1. Create a new project.
2. Create Cube > Make it Static.
3. Windows > Rendering > Lighting Settings.
4. Enable Auto Generate Checkbox.
5. Lightmapping Settings > Filtering > Advance.
6. Direct Denoiser > Radeon Pro.
Actual Result:
Assertion failed on expression is thrown in the console.
Expected Result:
No errors in the console.
Reproducible in:
2020.2.0a14, 2020.1.0b12, 2020.1.0a1.
Note: Radeon Pro option is disabled in 2019.3.
Environment:
Occurring only on Windows 10.
Stacktrace:
Assertion failed on expression: '!useRadeon || (!radeonDenoiser.IsNull() && radeonDenoiser->GetRefCount() <= 1)'
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (2020.2.X):
This issue has been identified as having low priority and has been closed without a fix. If the bug has no workaround and is blocking your production please feel free to reopen it with any additional information you might have. Sorry for the inconvenience this might cause.