Search Issue Tracker
Duplicate
Votes
0
Found in
5.6.0b1
Issue ID
874241
Regression
Yes
Camera stops rendering in game view after executing Handles.DrawCamera on editor window with same camera
To reproduce:
1. Open attached project.
2. Execute menu item: BUG/Open Editor Window
3. Look at game view
Expected result: Game view should look like usual.
Actual result: Game view rendered frame becomes same size as the one rendered in custom editor window (gif). Game view even changes the rendering position according to where editor window is positioned.
notes: on 5.6.0b1 everything looks fine., while in 5.6.0b5 and 5.5.0p1 game view looks broken. It might be due to some bugfix which haven't existed in b1 yet but was later on backported to 5.5
Reproduced on: 5.6.0b5 (802d0eaaa43c), 5.5.0p1 (f43eade5c7c4)
Not reproducible: 5.6.0b1 (d37b23d9dfff), 5.4.1p2 (a8ddefd1bf1d)
Regression introduced between 5.6.0b1 - 5.6.0b5
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
This is a duplicate of issue #834204