Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.0.75f1
6000.3.15f1
6000.4.7f1
6000.5.0b8
6000.6.0a5
Issue ID
UUM-141892
Regression
No
Color Curve Key values remain visible after changing Curve type
Reproduction steps:
1. Create a new project
2. Edit > Project Settings… > Graphics > Color Curves
3. Add Key by right-clicking on Color Curve graph
4. Select newly added Key
5. Select any other option in the Color Curve dropdown to change Color Curve type
6. Observe Color Curve graph
Actual result: Key values remain displayed in the Color Curve graph
Expected result: Key values disappear when Color Curve type is changed
Reproducible with: 2023.3.0a2, 6000.0.75f1, 6000.3.15f1, 6000.4.7f1, 6000.5.0b8, 6000.6.0a5
Reproduced on: macOS Tahoe 26.4 (M4), Ubuntu 24.04
Note: Clicking on the Color Curve graph makes Key values disappear
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
- AdaptiveLOD sample has missing prefabs and throws missing prefab errors when the AdaptiveLOD sample is imported and the AdaptiveLOD scene is opened
- Error "transform.position assign attempt for 'x' is not valid" is logged when Moving Game Object to View while a Scene is multi selected
- [Desktop] Plastic move detection mixes up identical files
- SVG Icon has tessellation issues in "Antialiased Arc Encodings", ok with "Basic Triangulation"
- "You may not pass null objects" and "Maximized serialized file backup not found" errors are thrown when maximizing and minimizing docked Multiplayer Play Mode window after Multiplayer Play Mode package is uninstalled
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.6.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.