You can use the Status bar at the bottom of the Stingray Editor to send simple commands to an instance of the Stingray engine that you started from the editor. This can be a local instance of the engine on your PC, the Test Engine, or the engine running on a connected console.
For example, you can execute a command that draws a performance HUD in the game viewport by entering perfhud artist or perfhud network. You can use other commands to enable and disable the built-in profiling system, toggle the display of performance statistics in the game viewport, or pause and resume the game itself.
To execute commands from the Status bar:
For a detailed reference of all available commands and parameters, see Console commands.
You can also retrieve brief descriptions of the commands by typing the help command in the Status bar command line. For brief descriptions of the parameters accepted by a single command, type help <command>, where <command> is the name of the command you want to execute. Open the Log Console window to see the output of the help command.
You can connect Visual Studio Code to any running instance of the engine. Once connected, you can send console commands and Lua scripts to the engine from Visual Studio Code, just as you can from the Log Console.
For details, see the home page of our Visual Studio Code extension.
If you need to send console commands to a standalone game that is not connected to the Stingray Editor, you can use the External Console application. From the main menu, select Window > External Console (Hotkey: Alt + 2).
Connect to localhost in the External Console application when you want to debug or view performance statistics of a deployed package.