Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.34f1
2021.2.19f1
2022.1.1f1
2022.2.0a13
Issue ID
UUM-646
Regression
No
[Device Simulator] Getting different transform position on Device Simulator compared to a device when using EnhancedTouchSupport
Reproduction steps:
1. Open the attached Unity project "SimulatorIssue.zip" from Google Drive (link in the edit)
2. Go to Assets > Scenes and open "SampleScene.unity" Scene
3. Enter the Play mode and open the Device Simulator window
4. In the Device Simulator Game view press on a red ball
5. Observe the ball
Expected result: When pressing the ball it stays in the same position
Actual result: When pressing the ball it changes its position, errors are thrown in the Console window
Reproducible with: 2.2.4-preview, 3.0.0-preview, 3.0.3-preview (2020.3.32f1), Device Simulator package is built-in (2021.2.17f1, 2022.1.0b13, 2022.2.0a8)
Could not test with: 2019.4.37f1 (Project breaks after downgrade)
Notes: the issue is not reproducible on a physical device, tested on Samsung Galaxy S9 (SM-G960F), OS: 9.0.0, Xiaomi Redmi Note 3 (Redmi Note 3), OS: 6.0.1
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 ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.