From 257186313b79537d6d690633b96866025f2f5140 Mon Sep 17 00:00:00 2001 From: Kevin Masson Date: Tue, 20 Apr 2021 14:31:16 +0200 Subject: [PATCH] Fix wording and code instructions for -batchmode usage `Environment.Exit(0)` didn't work for me, the process was still running. `EditorApplication.Exit(0);` works and kills the `Unity Editor` process correctly. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c3667e5..3cfb80b 100644 --- a/README.md +++ b/README.md @@ -985,7 +985,7 @@ UniTask can run on Unity Editor like an Editor Coroutine. However, there are som * UniTask.Delay's DelayType.DeltaTime, UnscaledDeltaTime do not work correctly because they can not get deltaTime in editor. Therefore run on EditMode, automatically change DelayType to `DelayType.Realtime` that wait for the right time. * All PlayerLoopTiming run on the timing `EditorApplication.update`. -* `-batchmode` with `-quit` does not work because does not run `EditorApplication.update`(quit on single frame) so should not use `-quit` and quit manually with `Environment.Exit(0)`. +* `-batchmode` with `-quit` does not work because Unity does not run `EditorApplication.update` and quit after a single frame. Instead, don't use `-quit` and quit manually with `EditorApplication.Exit(0)`. Compare with Standard Task API ---