Search Issue Tracker
Fixed
Fixed in 1.14.1
Votes
0
Found in [Package]
1.13.1
1.14.0
Issue ID
ISXB-1448
Regression
No
Inspector Window is constantly refreshed when the Player Input Component is expanded and Behavior is set to 'Invoke Unity Events'
Reproduction steps:
1. Open the attached “IN-95951.zip” project
2. Open the “SimpleDemo_UsingPlayerInput” Scene
3. Select the “Player” GameObject from the Hierarchy
4. Make sure the Editor is in Developer Mode
5. In the Inspector, expand the “Player Input” Component
6. Observe the debugger bubble next to the Inspector tab
Expected result: The bubble is not constantly refreshing
Actual result: The bubble is constantly refreshing (changing colors)
Reproducible with: 1.7.0 (2022.3.59f1, 6000.0.40f1, 6000.1.0b8, 6000.2.0a5), 1.13.1 (2022.3.59f1, 6000.0.40f1, 6000.1.0b8, 6000.2.0a5)
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- Does not reproduce if the “Behavior” property in the Player Input Component is set to anything other than “Invoke Unity Events”
- Also reproducible on a new project by just adding the Player Input Component onto an empty GameObject and changing the “Behavior” to “Invoke Unity Events”
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment