Search Issue Tracker
Fixed in 2021.3.25f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.1.0b1
Votes
0
Found in
2020.3.38f1
2021.3.9f1
2022.1.16f1
2022.2.0b8
2023.1.0a9
Issue ID
UUM-15519
Regression
No
D3D12 produces low FPS when using "CommandBuffer.IssuePluginCustomTextureUpdateV2"
Reproduction steps:
- Open the attached project (“D3D12 performance.zip“)
- Enter the Play Mode
- Observe FPS rate
Expected result: D3D12 performance is similar to D3D11
Actual result: D3D12 is significantly slower than D3D11
Reproducible with: 2020.3.38f1, 2021.3.9f1, 2022.1.16f1, 2022.2.0b8, 2023.1.0a9
Reproduced on: Windows 11
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
- UI Document (UXML) UI disappears from the Game view when any asset is imported and does not reappear until clicking in the Editor
- Warnings about invalid URIs are thrown when UI Builder's Material field is set to null
- Warnings about invalid URIs are thrown when UI Builder's Variable Asset Reference field is set to null
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
- Arabic separator character (066B) is treated as a full-width character when Duospacing is enabled on a TMP text component
Resolution Note (fix version 2023.1):
Removed unnecessary blit increasing the fps substantially. It doesn't match DX11 but goes above Vulkan