Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.3.X, 2017.4.X, 2018.1.X
Votes
34
Found in
2017.2.0p2
2017.3.0a4
Issue ID
971056
Regression
Yes
[iOS] Rigidbody interpolation causes objects to jitter
Steps to reproduce:
1. Download the user's attached project
2. Build to iOS
3. Observe the cube travelling in the screen
Expected: cube travels from left to right smoothly
Actual: cube jumps multiple times
Did not reproduce on: 2017.1.2p3, 2017.2.0a3
Reproduced on: 2017.2.0a4, 2017.2.0p3, 2017.3.0b11 (OpelGLES2 & Metal)
Regression introduced in: 2017.2.0a4
Reproduced with: iPhone 6S, iOS 11.0 (15A372)
Also reproduced on android:
Htc HTC 10*, OS:7.0, CPU:arm64-v8a, GPU:Adreno (TM) 530, Build:htc/pmeuhl_00401/htc_pmeuhl:7.0/NRD90M/857212.41:user/release-keys
Samsung SM G930F*, OS:7.0, CPU:arm64-v8a, GPU:Mali-T880, Build:samsung/heroltexx/herolte:7.0/NRD90M/G930FXXS1DQHF:user/release-keys
Xiaomi MI NOTE Pro*, OS:7.0, CPU:arm64-v8a, GPU:Adreno (TM) 430, Build:Xiaomi/leo/leo:7.0/NRD90M/7.11.2:user/release-keys (edited)
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
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
- Non-HDR color picker opens when selecting material color with HDR enabled
PhilFaily
Jul 05, 2018 22:56
9 months since this was reported and you still can't use anything newer than 2017.1.2 if you want to use Interpolated rigidbodies on iOS.
There seems to be some conjecture about it actually being fixed in 2018.2 and when that will actually be released.
Most people do not move their projects to the latest release because there is always something else that gets broken.
Killedby
Jun 29, 2018 22:07
Anybody can confirm that "Fixed in Unity 2018.2" is real ? 2018.2.0b10 ?
TheJavierD
Jun 20, 2018 19:22
Upon further testing, it is not fixed for a UWP build.
When the framerate is high and constant it works properly, but when the framerate starts dropping or being more inconsistent it does not work properly anymore.
If i compare the interpolation results between unity versions 2017.1.3f1 and 2018.2.0b9 , unity 2017.1 wins by FAR. It works properly even when the framerate is all over the place.
Please fix, this is game breaking.
CoderSi
Jun 19, 2018 09:55
This is broken on Switch (must be considered a mobile platform) and the problem goes far beyond jittery motion, the physics is completely broken when rigidbodies are set to interpolate. Not everybody can update to 2018, please can we get this fix back ported to 2017 please? We are on 2017.4.4 at the moment. Thank you.
kilosaurus
May 23, 2018 10:20
We can't update to any versions higher to 2017.1.3 due to this bug, will this be fixed soon ?
Afroman
May 22, 2018 14:41
Any ETA? This is still not fixed in Unity 2018.1.1
TheJavierD
May 11, 2018 23:19
I was wrong about it not being fixed in 2018.2.0b3
PolyVector
May 08, 2018 05:41
Still experiencing this bug in 2017.4.2f2 LTS
TheJavierD
May 05, 2018 17:37
I also tested 2018.2.0b3 and the problem still remains in a UWP build running in Hololens.
TheJavierD
May 05, 2018 17:12
This problem still remains in a UWP build running in Hololens. Tested in 2018.2.0b2
Please fix