Search Issue Tracker
Fixed
Votes
0
Found in [Package]
Issue ID
1196394
Regression
No
Scene View is resized and black offset appears when mouse.position.ReadDefaultValue() input action is invoked
How to reproduce:
1. Open the attached 'inputsystemnew_black_2.zip' project
2. Click 'Available Custom Editor Tools' button and select 'Painting Mode A' in the Scene View toolbar
Expected result: Scene View is resized and black offset appears
Actual result: Scene View remains the same
Reproducible with: 2019.2.17f1(preview-1.0.0, 1.0.0-preview.3), 2019.3.0f4(preview-1.0.0, 1.0.0-preview.3), 2020.1.0a18(preview-0.9.0, preview-1.0.0, 1.0.0-preview.3)
Could not test: 2017.4.36f1, 2018.4.15f1 Editor Tools are not introduced
Notes:
- 2019.2.17f1 Scene View is resized but there is no offset
- Video and project of reproduction attached in Edit
- Reproducible with Vector2 position = mouse.position.ReadValue() method, not reproducible with Vector2 position = mouse.delta.ReadValue()
- Could not reproduce with macOS
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
- Lightmaps are baked incorrectly for GameObjects when their Position is <=-2048 or >=2048 on any of the coordinates
- Sahder errors in Player when "Strict shader variant matching" is enabled and the rendering path is set to "Deferred"
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
Resolution Note:
Fixed in 2020.2.0a2
Resolution Note:
Fixed in: 2019.3.9f1
Resolution Note:
Fixed in: 2020.1.0b3