This may be a Windows-only issue, but in 1.1, when you run the simulator from the command line with a build path as an argument, the build appears not to open, and the simulator starts with the system launcher instead.
What is actually happening is that the build does open, but the launcher is opened a frame or two later. There doesn’t seem to be a way to prevent this.
This appears to be an unintended consequence of Launcher.pdx being included (or correctly located) in the SDK, whereas previously it wasn’t. It’s possible this behavior existed previously but didn’t surface.
A workaround for this is to rename
Launcher.pdx in the SDK’s
Data/System/ folder. The attempt to open the launcher fails silently and your build remains open.