Search Issue Tracker
Fix in review
Votes
0
Found in
5.5.0f3
Issue ID
861189
Regression
Yes
EditorApplication.delayCall does not work in the command line if WS platform is installed
To reproduce:
1) Download attached project
2) Test this on 5.4 with WSA installed by using command "<Unity.exe location> -batchmode -nographics -projectPath "<Path_To_Project>/CommandLineDelayCall" -executeMethod MyDelayedCall.MyMethod
Note: Don't add -quit. DelayedCall sometimes doesn't trigger if it is quit too quickly
3) Wait a bit to make sure the call is run
4) Open Editor.log - notice that both Debug.Log have been triggered
5) Repeat steps 2-4 on 5.5+ without WSA installed - nothing changes
6) Repeat steps 2-4 on 5.5+ with WSA installed - this time EditorApplication.delayCall never calls the other method
Reproduced in 5.5.0f3, 5.6.0b1
Not reproduced in 5.4.3p4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [LWRP] Add to list button gives empty list when trying to add features to the Forward Renderer
- In the Editor terrain is not rendered correctly when "Draw Instanced" on custom shader is enabled
- There is a refresh prompt even when there are no new Cloud projects available when Unity Hub is opened
- EditorSceneManager.sceneOpened and EditorSceneManager.sceneOpening events are not called when the scene is reloaded
- [IL2CPP] Fails to generate generic method struct variant when calling itself and causing ExecutionEngineException
Add comment