Search Issue Tracker
Won't Fix
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X
In Progress in 6000.1.X, 6000.2.X
Votes
0
Found in
2021.3.47f1
2022.3.56f1
6000.0.34f1
6000.1.0b2
6000.2.0a1
Issue ID
UUM-92509
Regression
No
Camera prefab shows up in overrides after upgrade when game view is changed to Simulator
How to reproduce:
1. Open the “IN_92574” project.
2. Switch to Game View and change the mode to Simulator.
3. Navigate to the Scenes folder in the project and select the “SaView” scene.
4. In the Hierarchy window, select the Main Camera object.
5. Open the Inspector panel.
6. From the Overrides dropdown menu, observe the available options.
Expected result: Camera prefab should not be listed in overrides
Actual result: Camera prefab shows up in overrides
Reproducible with: 2021.3.47f1, 2022.3.56f1, 6000.0.34f1, 6000.1.0b2
Reproducible on: MacOS 15.1.1 (M1 Max), Windows 11, Ubuntu 24.04
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
Thank you for reporting the issue. The underlying issue here is that code in newer Unity versions modifies some properties of the component that are hidden by the inspector. Because properties are overridden, the entire component gets the override marker but, because the overridden properties are not visible, it looks like nothing has been overridden. Unfortunately, resolving this issue is difficult and risky. We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug.
Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.