Search Issue Tracker
Feature Request
Feature Request in 6000.3.X
Votes
0
Found in
6000.0.58f1
6000.2.5f1
6000.3.0b2
Issue ID
UUM-119419
Regression
No
Inconsistent Terrain brush Opacity values between Scene view and Inspector
How to reproduce:
1. Create a new Unity project
2. In the Hierarchy, right-click -> 3D Object -> Terrain
3. In the Inspector, switch to the "Paint Terrain" mode
4. In the Scene view, navigate to the brush Overlay with the "Opacity" and "Size" settings
5. In the Inspector, navigate to the brush "Opacity"
6. Compare the values between the Scene view and Inspector
Expected results: The values are in the same numerical range
Actual results: The range in the Scene view is 0 to 1, in the Inspector 0.2 to 100
Reproducible with: 6000.0.58f1, 6000.2.5f1, 6000.3.0b2
Reproducible on: macOS Sequoia 15.6 (M1)
Not reproducible on: No other environment tested
Note: The Opacity values in the Scene view seem to be the correct way to represent Opacity
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:
Thanks for logging this issue. We've determined that this is a feature request and will be converting this report as such.
Alternatively, a workaround is to use the Terrain Tools package in which this feature is supported.
Resolution Note (6000.3.X):
Thanks for logging this issue. We've determined that this is a feature request and will be converting this report as such.
Alternatively, a workaround is to use the Terrain Tools package in which this feature is supported.