Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.2.0f1
2019.3.0a1
Issue ID
1173285
Regression
No
When having multiple windows containing CurveField the curve value changes to the one from the currently hovered window
How to reproduce:
1. Open user-submitted project (New Unity Project.zip)
2. Create two custom windows by selecting Curve Field Test > New Window
3. Adjust the curves in the two windows to be different
4. Activate the curve Editor in one of the windows by clicking on one of the curves
5. Hover the mouse over the window with the other curve
Expected result: the curve in the Curve Editor stays the same
Actual result: the curve in the Curve Editor changes to the value of the curve in the other window while the mouse is being hovered over that window
Reproducible with: 2017.4.31f1, 2018.4.6f1, 2019.1.14f1, 2019.2.1f1, 2019.3.0a12
Comments (1)
-
GamGode
Nov 21, 2019 08:04
I think it shouldn't be low priority. Curve is a very useful tool on handle data, any bug about it is unacceptable. What kind of team can't realize this.
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Resolution Note (2019.3.X):
low priority for our team, unlikely to be fixed for the moment.