Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.6.1p1
Issue ID
914052
Regression
Yes
WaitForEndOfFrame() doesn't execute in batchmode on built project
To reproduce:
1. Download attached project "Break My Routine.zip" and open in Unity
2. Open "Start Routine" scene
3. Enter to Play mode
Note: Observe that console says the coroutine completed and the application ended
4. Build the project and run it
Note: Observe that the game starts and ends and the output_log.txt shows the coroutine finished
5. Create a shortcut to your build and append -batchmode to the target path
6. Run the shortcut
Expected result: The game starts and ends and the output_log.txt shows the coroutine finished
Actual result: The executable never quits and output_log.txt doesn't show the coroutine finishing
Reproduced on Unity 5.6.1p1, 2017.1.0b7 and 2017.2.0a1
Not reproduced on Unity 5.6.1f1
Regression on Unity 5.6.1p1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprite Asset changes are unsaved after updating sprite atlas
- Graphics.DrawProcedural doesn't work like in DX11 when used with DX12
- [Quest 2] Running Entities Graphics/BatchRendererGroup under Vulkan results in a frame rate drop compared to OpenGLES 3 and causes Tile Binning to cost more
- Filters dropdown: Window doesn't rescale on items collapse
- Sprite Preview is broken when the Sprite is too tall or too wide
ewjordan
Jan 24, 2018 20:44
Also hoping to hear an update on this, was it intended to start working? That would be great.
Julian96
Oct 15, 2017 16:19
Hey, we were really looking forward to the 2017.2 version of Unity since we were stuck with the 5.6.f3 because of this issue.
It doesnt seem to be fixed though, none of our coroutines are working on our dedicated server which of course is running in batchmode.
Might this be fixed in the 2017.3 beta?
Regards Julian Kaulitzki