Search Issue Tracker
Fixed
Fixed in 1.4.4
Votes
0
Found in [Package]
1.4.2
Issue ID
ISXB-311
Regression
No
Errors appear in the Console when selecting a GameObject with the "Player Input" Component and entering and leaving Play Mode
How to reproduce:
1. Open the attached user project
2. Open Scene “Default“ (Assets/Scenes)
3. Select the child GameObject “Player“ of the “RigidBodyPlayer“ GameObject
4. Enter and Exit Play Mode
Expected result: No "Getting control 1's position in a group with only 1 controls when doing repaint" and “ArgumentNullException: Value cannot be null.“ errors in the Console
Actual result: "Getting control 1's position in a group with only 1 controls when doing repaint" and “ArgumentNullException: Value cannot be null.“ errors in the Console
Reproducible with: 1.4.2 (2020.3.40f1, 2021.3.10f1, 2022.1.17f1, 2022.2.0b8, 2023.1.0a12)
Reproduced on: macOS (12.5)
Note: In versions 2022.2.0b8+ and 2023.1.0a2+, the "Getting control 1's position in a group with only 1 controls when doing repaint" stops appearing, but the “ArgumentNullException: Value cannot be null.“ still appears.
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-282
Resolution Note (fix version 1.4.4):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-282