Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.4.4
Issue ID
ISXB-438
Regression
No
Mouse inputs in the Game view don't work when importing project files into an open project
How to reproduce:
1. Create a new Unity project (and open it)
2. Replace files in the Project folder with the attached “Assets“, “ProjectSettings“ and “Packages“
3. Select Scene “SampleScene“ (Assets/Scenes)
4. Enter Play Mode
5. Move the screen around with your mouse
Expected result: Mouse inputs work (can move the screen around in the Game view)
Actual result: Mouse inputs don’t work (can’t move the screen around in the Game view)
Reproducible with: 2020.3.41f1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b14, 2023.1.0a18
Reproduced on: macOS (12.5 Intel)
Note:
- Project must be open when replacing files
- Issue disappears when re-opening the project
- From version 2022.1+ an “InputEventData must specify size in bytes!“ error appears in the Console when trying to move the mouse in Play Mode (the error disappears when re-opening the project)
- This issue is not what the user reported, but could be the root cause of the reported issue
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
- Crash on ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
- [HDRP] Light doesn't bounce off terrains
- Unity Hub opens instead of the Unity Editor when launching a project from a Windows command line if a backslash is added to the end of the project path
- "ParseErrorException" is thrown when parsing a float with a very small value from JSON
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.