Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.44f1
Issue ID
UUM-83690
Regression
No
The Camera type is registered as Game type when it is actually a Preview Camera
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/Standard” Scene
3. In the Hierarchy window, select the “MainCamera” GameObject
4. Enter Play Mode
5. In the Console window, observe the message containing “Camera name: Preview Camera”
Expected result: The type of the Preview Camera is Preview
Actual result: The logged Camera type is Game
Reproducible with: 2021.3.44f1
Not reproducible with: 2022.3.50f1
Couldn't test with: 6000.0.23f1 (The Preview Camera's information is not being logged in the Console)
Reproducible on: Windows 11
Not reproducible on: No other environments 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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Resolution Note (2021.3.X):
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.