Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.2.0f2
Issue ID
960598
Regression
No
Field value target changes if a new element appears above the field that is being scrolled
How to reproduce:
1. Open a new (any) project
2. Open the Navigation window
3. Expand the Advanced section
4. Enable "Manual Voxel Size"
5. Click and hold on the "Voxel Size" text, then move mouse to the right (to increase the value in the field)
- Note that after a threshold passes, a warning appears in the window
- Additionally, the field being scrolled is now the Jump Distance field rather than the Voxel Size field
- This does not happen with any other fields that produce similar warnings such as Agent Radius, Agent Height and Step Height. This might be because the Warning is produced below those fields rather than above
- This also does not happen if a different warning is already present in the window, in the same location (such as the Step Height is greater than Agent Height warning)
- Reproduced with 2018.1.0a1 (65dac02ac102), 2017.2.0f2 (472de62575d5)
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
Add comment