Search Issue Tracker
Won't Fix
Votes
0
Found in
5.5.1f1
Issue ID
898631
Regression
No
Game screen does not render after DeviceLost when using Camera.SetTargetBuffers with Direct3D9
Reproduction steps:
1. Open project attached (RTTest.zip)
2. Open the RBTest scene
3. Hit play
3. Detach game window and try to resize it. The original image should be rendered in it's original resolution in the center of the screen, while the other part of the screen should be clear black.
4. Lock (Win+L) and Unlock the PC (do not turn off play-mode). You can also make Unity to lose the device context any other way.
Expected result: Game view will remain the same, there will be no errors in console.
Actual result: Game view becomes black, appears error: "Releasing render texture whose render buffer is set as Camera's target buffer with Camera.SetTargetBuffers!"
Note: This problem only appears on Direct3D9, when using Camera.SetTargetBuffers().
The same problem persists if the game is built as a standalone windows binary, but the same error and screen blackness comes up even on window resize. It seems, Unity reinitializes device context on each window resize.
Reproduced on: 5.3.6p5, 5.4.4p4, 5.5.3p1, 5.6.0f3, 2017.1.0b1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [URP] All materials render black when building via batchmode or without rendering Scene/Game view in Editor if Decal renderer Technique is set to "Automatic"
- Player Tags list shows extra blank space behind the scrollbar in the "Player Tags" settings window
- Edit Angular Limits gizmo handles are small and easy to miss-click in the Scene view
- Duplicate Player Tag save fails silently with no error or validation message
- Letters on the left side move further as Letter Spacing is increased when Advanced Text Generator is used and Alignment is set to Center
Add comment