Running Standalone

« Notes about the userdata directory | EDGE User’s Guide | Running with multiple clients and a manager »

Simple directions

1. Run using the "run_standalone" script

NOTE: This used to be called "run_graphics". For linux and mac users, there is a symbolic link to run_standalone called "run_graphics" to provide backwards compatibility.

What's really going on

Running standalone implies that the comm plugin is removed. In this case, there is no comm server so other clients would not be able to connect to the comm server (such as a simulation or other EDGE clients).

If you want to run visuals but keep the comm in a client mode, you could use the "run_client" script. If you wanted to run a comm server only but no visuals, you could use the "run_manager" script.

Behind the scenes, these scripts are merely adjusting the "-mode" argument to the EDGE executable. The argument to the "-mode" command line switch is selecting a mode within the "MANAGER→modes" block of the config file.

Looking at the config file, you will notice that these different mode blocks are simply adjusting the arguments to the comm plugin, which is what creates the behavior described above.

If you are run into multicast issues (i.e., cannot detect the comm server), check the Multicast Issues page

« Notes about the userdata directory | EDGE User’s Guide | Running with multiple clients and a manager »