Search Issue Tracker
Fixed in 2022.2.7f1
Fixed in 2022.2.X, 2023.1.X, 2023.2.X, 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
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
Resolution Note (fix version 2023.2):
Fixed GetNextFrameValue() in DX12 native rendering plugins.
Resolution Note (fix version 2023.1):
DX12: Fixed GetNextFrameValue() in DX12 native rendering plugins.
Resolution Note (fix version 2022.2):
DX12: Fixed GetNextFrameValue() in DX12 native rendering plugins.