Search Issue Tracker
Fixed in 2023.1.X
Votes
0
Found in
2020.3
2021.1.6f1
2021.3
2022.1
2022.2
Issue ID
1336042
Regression
No
[DX12] Failure in some render target allocations when rendering HDRP & 8k resolution textures
How to reproduce:
1. Open the attached project "Dx12RenderTextures2.zip"
2. Make sure the editor is using DX12
3. Open the "SampleScene" scene in the "Scenes" folder
4. Enter Play Mode
5. Open "Statistics Window" with the "Stats" button
6. Select "Trigger" GameObject in the Hierarchy
7. Toggle "trigger" checkbox
Expected result: Performance difference from DX11 is not very significant
Actual result: Performance drops to single digits and takes more time to recover compared to DX11
Reproducible with: 2019.4.39f1, 2020.3.35f1, 2021.3.4f1, 2022.1.4f1, 2022.2.0a14
Reproducible on: Windows 10 (2004)
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
- [Remote Config] PreparePayloadWithConfigType function is looking for camelCase property names, when the JSON objects are using PascalCase naming
- UI Builder Viewport's Tool Gizmo has deadzones
- SpriteShapes are rendered using multiple draw calls when the SRP Batcher determines their nodes are incompatible in a specific project
- UI Toolkit Debugger "Pick Element" selects Scene view panel when trying to select a world space UI element in the Scene view
- MSAA warnings are thrown when custom post-processing is used and the Scene contains transparent GameObjects
Resolution Note (fix version 2023.1):
Fixed version: 2023.1.0a1