Search Issue Tracker
Third Party Issue
Votes
0
Found in
6000.0.0b16
Issue ID
UUM-70379
Regression
No
GraphicsBuffer write breaks when Play Mode is set to Play Maximized
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/Dev” Scene
3. In the Game View, make sure the Play Mode behavior is set to "Play Maximized"
4. Enter Play Mode
5. In the Game View, click the "Play" button
6. Press L key and look up using the mouse
7. Observe the lights appearing on the ceiling
8. Exit Play Mode
9. Observe the Console window
Expected result: The lights light up gradually and there are no messages logged in the Console
Actual result: The lights start flickering and “LockBufferForWrite: Multiple uploads in flight for buffer 00000198C32F33F0 (bufferHandle: 579) of size 10240. Falling back to slow path. LockBufferForWrite() should be called only once per frame on D3D11.” is constantly being logged in the Console
Reproducible with: 1.1.0-pre.3 (2023.3.0a19), 1.2.0 (6000.0.0b16)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- Crash on EnumerateDisabledKeywordsInVariantsArray or UNITY_XXH32 when rapidly saving ShaderGraph or VFXGraph changes
Resolution Note:
The reproduction project uses custom bootstrapping to set up the player loop and external packages which are interfering with the investigation of the issue.