Search Issue Tracker
Fixed
Fixed in 2021.3.25f1, 2022.2.16f1, 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
- SerializedPropertyChangeEvent is invoked when initially binding PropertyFields in custom Editor
- UI Panel is not visible when HDR and STP filter are enabled
- Crash on GfxDeviceD3D11Base::DrawBuffersIndirect when opening a specific project
- OnTriggerExit2D is called in Play mode when undoing component adding
- Builds fail with "Execution failed for task ':launcher:checkReleaseDuplicateClasses'" error when the newer version of the In-App Purchasing package is installed on a specific project
Resolution Note (fix version 2023.1.0b1):
Removed unnecessary blit increasing the fps substantially. It doesn't match DX11 but goes above Vulkan