Search Issue Tracker
Won't Fix
Unknown (hidden) 2022.1.X, 2022.2.X
Votes
1
Found in
2022.1.3f1
2022.2.0a15
Issue ID
UUM-3358
Regression
No
Editor windows become black when using "Graphics.Blit" inside the Editor
How to reproduce:
1. Open project "Black_ProjectExplorerWindow.zip"
2. Select any file in the Project window from the Editor folder (Assets > Editor)
3. Observe the view
Expected result: Project window doesn't become black
Actual result: Project window becomes black for a few seconds
Reproducible with: 2022.1.0a4, 2022.1.3f1, 2022.2.0a15
Could not test with: 2019.4.39f1, 2020.3.35f1, 2021.3.3f1, 2022.1.0a3 (Errors after project downgrade)
Reproduced on: macOS 11.6 (Intel), Windows 10
Note: Also reproducible when selecting "Main Camera" GameObject in the Hierarchy window
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
- "InvalidOperationException" and additional errors throw in the Console window when using a custom Composite
- The Visual Effect Graphs Custom HLSL node does not generate errors when the HLSL code used is incorrect
- The Capacity field in the “Particle System Info“ is not updated when changing the Visual Effects Graph is not saved
- [VFXG] Setting an exposed texture to none assigns a random texture
- Rigidbody2D with interpolation position breaks when rotation is set and Time.timeScale is adjusted
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2022.2.X):
This issue is the result of incorrect usage of the Graphics.Blit API by the user provided project.
Resolution Note (2022.1.X):
This issue is the result of incorrect usage of the Graphics.Blit API by the user provided project.
Resolution Note:
This issue is the result of incorrect usage of the Graphics.Blit API by the user provided project.
In the documentation for Graphics.Blit (https://docs.unity3d.com/ScriptReference/Graphics.Blit.html) it is explicitly called out that "Graphics.Blit changes RenderTexture.active. Keep track of the previously active RenderTexture if you need to use it after calling Graphics.Blit."
A change to the user script of storing the RenderTexture.active property before calling Graphics.Blit and resetting it afterwards resolves this issue.