General

[CBtom12]

Am I the only one that notices this? I thought it might be worthwhile mentioning, hoping that the SDK crew picks it up.

[Daveid]

Just tried putting Thread.Sleep(300); in my update loop and I have a very slow game now, so it's not ignored here.

I suggest the problem lies somewhere else 

edit: assuming you mean in the simulator, if device it might be a device thing

[YstadYakuza]

It's not ignored for me either in the simulator. I don't have any idea about how it works on devices though.

[jamesnorman91]

We'll take a look at this in the coming week for you Ystad.

[YstadYakuza]

In this thread I was reporting "no problems" encountered. Thread.Sleep(num) seems to be working to me.

[jamesnorman91]

Sorry I meant CBtom12

We have not been able to observe the problem on a PS Vita or in the Simulator. If you are able to provide more info on the circumstances of problem, that would be useful.

You could use the following to measure it

Stopwatch timer = new Stopwatch();

timer.Start();
Thread.Sleep(50);
timer.Stop();
Console.WriteLine("Thread slept for " + timer.ElapsedMilliseconds + "ms");
timer.Reset();

Thanks,

James

[laadron]

I'm having some strange behavior with Thread.Sleep() as well - at least in the simulator. As far as I can tell, whenever I start up a new thread, any existing thread that is sleeping will break out of sleep prematurely.