Build and run one or more instances of your Unity game easily.
Debug.Log's stack trace for instance logs.For a full list of Unity command line arguments see: https://docs.unity3d.com/Manual/PlayerCommandLineArguments.html
Install using the Package Manager and "Add package from git URL" using the the URL below:
https://github.com/ProfButch/MultiRun.git?path=Packages/MultiRunOnce installed you'll see the MultiRun menu in the menu bar.
Configure a directory and file name to build to (MultiRun -> Settings) and you're ready to go.
It mostly works exactly how you'd expect, but there's some nuances.
There are two build paths, one which is stored at the Editor level which spans all projects, and another that you can set per proeject. You must have at least one of these set to enable the menus. The project build path takes precedence.
Once Set you can use Build, Build Current Scene or Build and Run to generate a build.
Build Current Scene will generate a build with the current scene as the scene to be run first. This only affects the build that is generated with this menu option. The scene does not need to be in the Build Settings.
When using Build Current Scene use Run -> [1-4] menu item and NOT Build and Run since that will overwite the build.
You can build and run up to 4 instances in one step using Build and Run -> [1-4]. If you already have a build (such as when using Build Current Scene) you can use Run -> [1-4] to launch up to 4 instaces of your game.
Important Instances are launched with the --logfile argument, and the log file name is specific to each instance number. This means that if you launch more instances while other instances are still running then they will write to the same log file. For example, if you launch 4 instances, then launch one additional instance then instance 1 and 5 will be writing to the same log.
All settings are saved in the UserSettings/MultiRun.yaml
The Log Watcher allows you to monitor the end of each of the instance logs. Unity does not like to display large amounts of text (or what others might consider "a not small, but by no means large" amount of text), so you will still need another tool to view logs in their entirety. You can use Multi Run -> Open build directory to quickly get to your log files.
The Log Watcher has some amount of smarts in it to ignore the large dump of memory allocation stats that Unity leaves at the end of logs. It mostly works, but it could be better. It uses crazy magic. If you notice that you have a DontDestroyOnLoad object called MultiRunGameObject, this is part of the magic to detect the application closing.
Due to a layout refresh issue, the Log Watcher is automatically closed everytime scripts are recompiled. You can assign a keyboard shortcut to the Log Watcher menu item to make this less annoying.
Some of the options in the settings are performed by MultiRun when the instance starts. This usually happens automatically by the RuntimeInitializeOnLoadMethod method MultiRun.Runner.InitializeOnLoad.
Sometimes this doesn't get kicked off. If that is the case, you can call this method directly (multiple calls do not do anything). In your own RuntimeInitializeOnLoadMethod or the Awake/Start of your first scene call:
MultiRun.Runner.InitializeOnLoad();