Hi there,
I just purchased 2.0 and Esenthel, you did a really great job on it, I like it!

But I don't know if this issue only occurs in 2.0 or also in Esenthel 1.0. I am trying to make my (first person) character controller framerate independent. So I enabled screen synchronization, but this doesn't seem to work like I expected...
Now the character controller moves way to fast, so I thought it might be a problem with dt, which isn't used by the controller.update method. So I multiplied the Tim.dt, but this results in very strange behavior (laggy movement).

This issue can be easily reproduced if you change the Physics/05 - Controllers sample:
Add D.synch(false) in the InitPre method and change Flt s = 3 to Flt s=300 * Time.d().

Am I doing something wrong or is this a bug?

Thanks in advance

I was able to reproduce it, and it does seem to be a bug or a conflict of some kind.

Thanks for reproducing this!

Esenthel, could you look into it please, I really need a working character controller which doesn't depend on a constant 60 fps framerate, and I think I am not the only one

Not sure if my problem is related but when the screen locks (because I have no idea what I'm doing!) ESC or ALT-F4 doesn't work until a minute later.

(03-04-2013 12:28 PM)Kevin Wrote:  I just purchased 2.0 and Esenthel, you did a really great job on it, I like it!

Thanks for the comment, I appreciate it

I've reproduced the bug with 05 - Controller with D.sync(false);
I'm now investigating this.

Please note that Flt s=3; is ok it should not be multiplied by Time.d();
There's something wrong with controller velocities in EE physx 3 version (I'm checking).

Temporary fix is to set Physics.timestep(PHYS_TIMESTEP_VARIABLE);
I'm checking PHYS_TIMESTEP_ROUND

Okay I managed to make this work correctly in PHYS_TIMESTEP_ROUND as well.
It should be ok in next release.

great, thanks!