+ (deltaY * ltaTime * moveSpeed / screenHeight), + (deltaX * ltaTime * moveSpeed / screenWidth), The value movementX is higher when there are something selected in Hierarchy tab, and smallest when run in 'Maximize on Play' is selected.ĬameraScreenXY = (transform.position) I found the following code would have affect by the Unity editor:

The ltaTime return different result if I didn't select anything in Hierarchy tab, or if the 'Maximize on Play' is on.Īlso the publish target has different result, the rotation works for web player, but not work in standalone full screen. My biggest concern is that the character controller Move function normally takes in a value multiplied by ltaTime and I can see this becoming a major problem. While I was able to remove it from most of the code and convert most movement systems to be based on physics, there are many other places it is used where timing is vital.ĭoes anyone know what could be causing this problem, or if it is a bug within Unity itself, and what, if anything, could be done in it's place/to fix it?

I soon discovered that although it is most obvious in this context, it appears to be distorting ALL uses of ltaTime. It was a fellow team member who first noted the bug when a few bullets which had been slowed down for testing started to move more quickly when unrelated character controllers received input from an x-box controller. The script results in inconsistent movement of objects. Using UnityEngine using System.Collections Time.fixedDeltaTime does not have this problem, and I have not tested it in Javascript.Įssentially, it appears that ltaTime is not correctly calculating or that Update is not being called consistently with each frame because when used in any form (including it's simplest) such as: Something very strange appears to be happening with ltaTime when used in the Update loop in C# Scripts.

Unity web player uninstall not working