Invoke and Time.timeScale

Just looking for a quick answer, Does timeScale affect Invoke/InvokeRepeating rate?

 

The easiest way to answer that.... make a test...

Code (csharp):

1.  
2. Function Start(){
3. Invoke("MyAnimation", 2.0);
4. Time.timeScale=0.0;
5. }
6.  

If the Invoke happens, no, if not, yes.

 

Now, without spoiling the result, it might help if you also notice the syntax-typo in function.

 

To save anyone else just looking for info and without access to Unity to check the result, Time.timeScale = 0.0f will stop Invokes from being called until it is set to a value other than 0.0f.

 

To give a more specific answer, Invoke does take time.timeScale into account (it operates on game time, not real time).

Test code:

Code (csharp):

1.  
2. float startTime;
3.  
4. void Start() {
5.     startTime = Time.realtimeSinceStartup;
6.     Invoke("TestMethod", 5.0f);
7. }
8.  
9. void TestMethod() {
10.     print("Real time taken 1: " + (Time.realtimeSinceStartup - startTime));
11.     startTime = Time.realtimeSinceStartup;
12.     Time.timeScale = 0.5f;
13.     Invoke("TestMethod2", 5.0f);
14. }
15.  
16. void TestMethod2() {
17.     print("Real time taken 2: " + (Time.realtimeSinceStartup - startTime));
18. }
19.  

takes 5 seconds for the first Invoke, and 10 for the second.

 

Hey guys, I need Invoke() to be independent from the timeScale, but rather on the real time since startup. Is there any way to make it possible ?

 

Code (CSharp):

1. public void InvokeRealTime(string name, float duration) {
2.     Invoke(name, duration / Time.timeScale);
3. }

 

What happens when time scale is set to 0? Last I checked most math goes crazy when dividing by 0...

 

Code (CSharp):

1. public void InvokeRealTime(string name, float duration) {
2.     Invoke(name, Time.timeScale == 0 ? 0 : duration / Time.timeScale);
3. }

 

..still, if the timescale changes in the meantime (between the instant when you call Invoke and <duration> seconds later), the waiting time gets screwed up.
The only workaround I found is starting a coroutine and performing a realtime wait (checking against Time.realtimeSinceStartup every frame).

 

Can always do a CancelInvoke and Invoke again to avoid real-time monitoring.

 

it will can a error when Time.timescale is 0, duration / Time.timescale get a infinite value...

There has a tween plugin call DoTween ,and it provide a function call DOVirtual.DelayedCall. and you can decide wether ignore timescale or not..
follow is the assetstore link with the document links in the webpage.
https://www.assetstore.unity3d.com/en/#!/content/27676

 

Code (csharp):

1. public void InvokeRealTime(string functionName, float delay) {
2. StartCoroutine(InvokeRealTimeHelper(functionName, delay) );
3. }
4. private IEnumerator InvokeRealTimeHelper(string functionName, float delay) {
5. float timeElapsed = 0f;
6. while (timeElapsed < delay) {
7. timeElapsed += Time.unscaledDeltaTime;
8. yield return null;
9. }
10. SendMessage(functionName);
11. }
12.  

 

Couldn't you just use System.Timers.Timer for that?

 

I ended up doing something similar to that with timers. Thanks anyways!

 

Use coroutine with UnityAction and WaitForSecondsRealtime:

Code (csharp):

1.  
2. StartCoroutine(InvokeRealtimeCoroutine(DoSomething, seconds));
3.  
4. private IEnumerator InvokeRealtimeCoroutine(UnityAction action, float seconds)
5. {
6.     yield return new WaitForSecondsRealtime(_seconds);
7.     if (action != null)
8.         action();
9. }
10.  

 

Are you sure, here need divide? Maybe multiply?

 

try this:

Code (CSharp):

1.  public IEnumerator Invoke( System.Action action, float Delay)
2.     {
3.         yield return new WaitForSecondsRealtime(Delay);
4.         if (action != null)
5.             action();
6.     }

 

how come something as basic as this (whether invoke uses game time or real time) doesn't appear in the documentation?

https://docs.unity3d.com/ScriptReference/MonoBehaviour.Invoke.html

 

?

It uses seconds. What do you mean "game time"?

 

I agree this should multiply not divide. I do this:
InvokeRepeating ("GetServerDateTime", 15 * Time.timeScale, 15 * Time.timeScale);

Thanks for the tip on WaitForSecondsRealtime - I have never noticed that!