Hi, just wondering if anyone has a clue what’s going on here?
This is on a ZTE Blade, it doesn’t ever happen on my SGS2. It also only happens when in contact with something on a >45’ angle. I have tried changing the physics solver iteration count, when changing this to 100 it sends the bike straight to blue screen as soon as it moves (it blue screens when the bikes position becomes Nah due to it being blasted off the screen) it worked fine at 100 solver count on the SGS2.
So this has me very confused, any ideas of what I should try next?
if it works on one device but not the other that somehow really implies that there is one or more cases where forces or even worse position changes (should never happen) get applied in Update or LateUpdate instead of fixed update, leading to inconsistent non-continous physics which on a slower device will lead to ‘physical teleports’ which in case of a collision can have all kind of nightmare consequence because it might need to push the object out extremely far to resolve the collision and such pushes can lead to very strong forces up to ‘infinite forces’
Are you sure you are only using the physical functions and no modifications to positions and rotations otherwise?
I only use AddRelativeTorque and AddTorque to move the bike, the only exception to this is when the bike is reset, At which point it is set to kinematic and put to sleep. Also all AddTorque functions are called in fixedupdate.
What you have described dreamora is exactly what it looks like is happening, I just cant figure out why
have you sent unity a bug report? what about a logcat report?
you can either use android sdk to get the logcat or download log collector from the market, its a free app that gives you a log cat report right on your phone, it almost seems as the phone is loosing memory?
can you replicate this problem in a simplified scene? try to recreate the problem area in a new scene and see if it continues to happen…
if it does in a very simple scene then it may be the setup? if it doesnt happen it may be something in your bigger scene or the phone dumping memory
do you have specific phone models this happens on vs. not happening on?
if you want me to test it on my phone, i have a droid x, you can PM me
im not sure if any of this will help, just tossing ideas out there to test on, let me know how it goes
You can get unstuck in physics by calculating a number in update, then applying that number in physics which are in fixedupdate. In cases like that, you would need deltatiming in update.
Finally found a solution!!! although no idea why it worked :s
I put a box collider inside all my objects that had a rotation vector = (0,90,0). Then just scaled the collider to fix the shape and the glitch is gone. Seriously weird, anyone know why it would do this?
any other ideas?
keep us updated on the release!