Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
1
Found in
6000.0.59f1
6000.2.7f1
6000.3.0b4
6000.4.0a1
6000.5.0a1
Issue ID
UUM-120433
Regression
No
[Quality Hackweek] Activated Terrain Inspector is active only until the terrain GameObject is deselected when two or more Inspectors are open
How to reproduce:
1. Create and open a new project
2. In the Hierarchy, create a 3D → Terrain GameObject, then select it
3. In the Inspector, right-click the Inspector tab and press Add tab → Inspector
4. Focus on the first Inspector
5. Press the “Activate this inspector“ button to activate the Inspector
6. Deselect and reselect the Terrain GameObject
7. Observe the first Inspector
Expected result: The activated Inspector is the default active Inspector whenever the object is reselected
Actual result: The last added Inspector will always be the default active Inspector whenever the object is reselected
Reproducible in: 2023.1.0a1, 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment 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
- 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
- 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
Resolution Note:
Thank you for reporting a bug to Unity.
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.
Today we will be closing this case. 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.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
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.
Today we will be closing this case. 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.