Search Issue Tracker
Fixed
Fixed in 2022.2.7f1, 2023.1.0b4, 2023.2.0a1
Votes
0
Found in
2022.2.2f1
2023.1.0a25
2023.2.0a1
Issue ID
UUM-23065
Regression
Yes
GetNextFrameFenceValue() always returns 1
The native rendering plugin interface functions IUnityGraphicsD3D12v7::GetNextFrameFenceValue() always returns 1.
To reproduce:
- Write a native plugin that uses GetNextFrameFenceValue()
- Use the plugin in a C# project that renders multiple frames
Expected result: The return value increase at least by one per frame
Actual result: The return value is always 1
Comments (1)
-
vedade
Jan 30, 2023 22:04
I was looking forward to it too
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
- Memory leak occurs when focused on Player while using Direct3D12
- 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
Resolution Note (fix version 2023.2.0a1):
Fixed GetNextFrameValue() in DX12 native rendering plugins.
Resolution Note (fix version 2023.1.0b4):
DX12: Fixed GetNextFrameValue() in DX12 native rendering plugins.
Resolution Note (fix version 2022.2.7f1):
DX12: Fixed GetNextFrameValue() in DX12 native rendering plugins.