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
- Standard Unity Materials and Shaders become corrupted after importing specific Asset Packages
- [Linux][OpenGL][Vulkan] Draw calls are not shown in the Event List when taking a capture of a frame with RenderDoc
- Inaccurate collision detections when Rigidbody Collision Detection is set to "Continuous" or "Continuous Dynamic"
- Crash on Object::IncrementPersistentDirtyIndex when upgrading project version
- [iOS] Multiple Xcode project instances created before opens up when performing Build and Run for iOS Platform
Add comment