WaitForSeconds and WaitForEndOfFrame in Unity - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of WaitForSeconds in Coroutine

What will be the output of this Unity C# coroutine code snippet?

Unity

IEnumerator ExampleCoroutine() {
    Debug.Log("Start");
    yield return new WaitForSeconds(1f);
    Debug.Log("After 1 second");
}

A Start immediately, then after 1 second print 'After 1 second'

B Print both messages immediately without delay

C Print only 'Start' and never print 'After 1 second'

D Print 'After 1 second' first, then 'Start'

💡 Hint

Think about how WaitForSeconds pauses the coroutine.

The coroutine prints 'Start' immediately, then pauses for 1 second due to WaitForSeconds(1f), and finally prints 'After 1 second'.

❓ Predict Output

intermediate

When does WaitForEndOfFrame execute?

Consider this coroutine snippet. When will the message 'End of frame reached' be printed?

Unity

IEnumerator FrameCoroutine() {
    Debug.Log("Before waiting");
    yield return new WaitForEndOfFrame();
    Debug.Log("End of frame reached");
}

A After 1 second delay

B Immediately without waiting

C Before rendering starts for the frame

D After all rendering for the current frame is done

💡 Hint

Think about the frame lifecycle in Unity and when WaitForEndOfFrame resumes.

WaitForEndOfFrame waits until the frame finishes rendering, then resumes the coroutine, so the message prints after rendering.

🔧 Debug

advanced

Why does this coroutine never print the second message?

Look at this coroutine code. Why does it never print 'Second message'?

Unity

IEnumerator TestCoroutine() {
    Debug.Log("First message");
    yield return new WaitForSeconds(-1f);
    Debug.Log("Second message");
}

A It causes a compile error and never runs

B WaitForSeconds with negative time causes the coroutine to stop and never resume

C Negative time is treated as zero, so both messages print immediately

D The coroutine throws an exception and stops

💡 Hint

Check how WaitForSeconds handles negative values.

Using a negative time in WaitForSeconds causes the coroutine to wait indefinitely and never resume, so the second message never prints.

🧠 Conceptual

advanced

Difference between WaitForSeconds and WaitForEndOfFrame

Which statement correctly describes the difference between WaitForSeconds and WaitForEndOfFrame in Unity coroutines?

A <code>WaitForSeconds</code> pauses for a set time; <code>WaitForEndOfFrame</code> waits until the current frame finishes rendering

B Both wait for a fixed time but differ in precision

C <code>WaitForSeconds</code> waits until the frame ends; <code>WaitForEndOfFrame</code> pauses for a set time

D Both wait until the next frame starts

💡 Hint

Think about timing: fixed seconds vs frame lifecycle.

WaitForSeconds delays the coroutine by a specified number of seconds. WaitForEndOfFrame waits until the frame rendering completes before continuing.

❓ Predict Output

expert

Number of times a message prints in this coroutine

Given this coroutine, how many times will 'Frame ended' print after starting it once?

Unity

IEnumerator LoopCoroutine() {
    while (true) {
        yield return new WaitForEndOfFrame();
        Debug.Log("Frame ended");
    }
}

A It prints only once and then stops

B It prints once per frame indefinitely until stopped

C It never prints because of an infinite loop error

D It prints twice per frame

💡 Hint

Consider what an infinite loop with WaitForEndOfFrame means in a coroutine.

The coroutine waits until the end of each frame, then prints the message, and repeats forever, printing once per frame.