Search Issue Tracker
Won't Fix
Under Consideration for 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X
Votes
0
Found in
2021.3.36f1
Issue ID
UUM-66771
Regression
No
[Mobile] Game character hovers above ground when trying to move
Reproduction steps:
1. Open the attached “IN-17467.zip“ project
2. Go to Project Settings > Player > Publishing Settings > Project Keystore and uncheck the “Custom Keystore“ check box
3. Build and Run for Android
4. Walk with a character using “A“ and “D“ keys
Expected result: Character moves without any issues
Actual result: Character starts hovering above ground when trying to move
Reproducible with: 2021.3.11f1, 2022.1.19f1, 2022.2.0b10, 2023.1.0a13
Couldn’t test with: 2020.3.40f1 (Game breaks after downgrade)
Reproducible with these devices:
Huawei - (ELS-NX9), Android 10, CPU: HiSilicon Kirin 990 5G, GPU: Mali-G76
Samsung Galaxy Z Flip3 5G (SM-F711B), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
Samsung Galaxy S22 (SM-S901B), Android 12, CPU: Exynos 2200, GPU: Ltd.
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
Note:
- Character moves without any issues in the Editors Play mode
- Character doesn’t move in the Standalone Player
- Character walks without the animation in the Editors Play mode If the selected platform is iOS
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Due to the lack of information around the codebase in the project as none was provided, we don't have enough evidence to tell us that something is indeed breaking.
If the issue could be reproduced on a new project with a simpler reproduction then it would be possible to investigate further.