using WWW when timeScale is near 0?

Is this possible? If so, what is the secret?

As I can see, yielding for WWW result data doesn't work when timeScale is near 0 and thus it's not possible to say "get scores while paused"

Is there a yield equivalent that isn't dependent on timeScale?

 

Oh, yeah - that would be great! Something like "WaitForRealTimeSeconds" in addition to "WaitForSeconds". That's something I could definitely use (because I'm playing around a lot with Time.timeScale ;-) ).

http://unity3d.com/support/documentation/ScriptReference/WaitForSeconds.html

Who posts this to the WishList forum?

Sunny regards,
Jashan

 

OK, here ya go:

Code (csharp):

1. function Start() {
2.     yield WaitForRealTimeSeconds(1.0);
3.     print ("1 real second has passed no matter what the time scale is!");
4. }
5.  
6. function WaitForRealTimeSeconds (delay : float) {
7.     yield WaitForSeconds(delay * Time.timeScale);
8. };

No charge.

Anyway, yeah, looks like yielding for WWW doesn't like really low timeScale numbers here either. Bug?

--Eric

 

Thanks Eric, you're so right!

The funny thing is that I wrote my own time management class with which I can do my own time-scaling (I needed that for my server which has to manage different timescales simultanuously for different game sessions). But simply writing my own subclass of WaitForSeconds was beyond my imagination ;-)

Cool, that solves another issue I was having

Sunny regards,
Jashan

 

So I guess the answer is no?

 

That wouldn't help if the timeScale is 0, or if the timeScale changes while it's waiting. A more robust function might look like:

Code (csharp):

1.  
2. function WaitForRealTimeSeconds(duration : float) {
3. var started : float = Time.realtimeSinceStartup;
4. while (Time.realtimeSinceStartup < started+duration) yield;
5. }
6.  

(untested!)

....actually, I may put that on the wiki....

 

That's a cool utility, and I might be just missing it, but I don't see how that has anything to do with using WWW when timeScale is near 0.

Wanting to yield to a return on the WWW call, sure I can just wait a few seconds and test, but it's not really the same as waiting for the data.

 

Right, you're yielding on the result of WWW, not WaitForSeconds or anything else.

I guess there is a bug with that, but as a workaround you could write a loop (or coroutine) to keep polling for data and calling a callback function when/if the data finally clears. Just remember to code a timeout.

Still clunky, but it might be all you can do for now.

Seems odd that WWW would be in any way based on the timeScale though...

HTH,
-Jeremy

 

Yes this is what I was referring to by "wait a few seconds and test". It all seems very strange given the nature of the internet, but it is all I can do when paused apparently.