Search Issue Tracker
Fixed
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
- Rendering is broken with UIToolkit with many Intel GPUs (driver-bug)
- [Vulkan] Crash in Windows Standalone when Vulkan is set as rendering API and player window is out of focus
- "Can't destroy Transform component" Error is thrown when closing a scene that contains a DontSave Prefab with a Child
- [Particle System] Editor freezes when assigning a nested Particle System in the Sub Emitter Module
- Unable to switch to different material when selecting another material from Asset selector window on Particle System Material
Add comment