Obi Official Forum › Obi Users Category › Obi Softbody v
An mesh bug On iOS including iPhone 12 Pro and iPad Pro 2

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
An mesh bug On iOS including iPhone 12 Pro and iPad Pro 2
shiki1234 Offline
General User
Posts: 3
Threads: 2
Joined: Mar 2021
Reputation: 0
#1
02-03-2021, 07:39 AM
I use obi softbody 6.0.1 on my iPhone 12 Pro and my iPad Pro 2,IOS 14.4,but it cannot work normally.
Like this ,how can I deal with it.
Find
Reply
josemendez Offline
Forum Admin
*******
Posts: 6,321
Threads: 24
Joined: Jun 2017
Reputation: 400
Obi Owner:
  • Rope
  • Cloth
  • Fluid
#2
02-03-2021, 09:02 AM (This post was last modified: 02-03-2021, 09:06 AM by josemendez.)
Hi there,

I'm unable to reproduce this. Using iOS 14.4 in an iPad Pro 2 and an iPhone 7 (I don't own an iPhone 12 Pro).  Here's a video of the results on the iPhone:



What Unity version are you using? (I'm using Unity 2019.3.10f1)
What Obi backend are you using (Oni or Burst)? (I'm using Burst)
What are your build settings? (IL2CPP, Net Standard 2.0, ARM64)
What Xcode version are you using? (Xcode 12.4 12D4e here)
Website Find
Reply
josemendez Offline
Forum Admin
*******
Posts: 6,321
Threads: 24
Joined: Jun 2017
Reputation: 400
Obi Owner:
  • Rope
  • Cloth
  • Fluid
#3
02-03-2021, 12:28 PM (This post was last modified: 02-03-2021, 02:46 PM by josemendez.)
Another user reported a similar issue: http://obi.virtualmethodstudio.com/forum...-2771.html

Seems to be an issue with interpolation in the Oni backend, affecting mobile platforms only. Using the default backend (Burst), or disabling interpolation fixes it. Can you confirm whether this works for you?
Website Find
Reply
josemendez Offline
Forum Admin
*******
Posts: 6,321
Threads: 24
Joined: Jun 2017
Reputation: 400
Obi Owner:
  • Rope
  • Cloth
  • Fluid
#4
02-03-2021, 02:46 PM (This post was last modified: 02-03-2021, 02:51 PM by josemendez.)
Just confirmed this is a bug in Unity, that manifests itself when using the Oni backend as unlike Burst, it  does not clamp Time.deltaTime values.


https://forum.unity.com/threads/fixedupd...2.1067567/

Tested in Unity  2018.4, 2019.3, and 2020.1, works fine in all of them. However 2020.2 returns completely incorrect Time.deltaTime values. I suspect the origin of this are the changes introduced to Time.deltaTime in 2020.2: https://blogs.unity3d.com/es/2020/10/01/...d-it-take/

The bug has been reported and I'm awaiting feedback from the Unity staff.

For now, using Burst or disabling interpolation are the only workarounds.
Website Find
Reply