Play In Editor Settings

The Play settings panel can be opened two different ways:

  • The Play settings panel can be opened clicking Edit > Editor Preferences...

    PIE_settings.png

    Then, select the Play section of the Editor Preferences window.

    PIE_Settings_Preferences.png

  • Or you can open it by clicking on Advanced Settings... at the bottom of the Play dropdown menu.

    PIE_settings_buttonmenu.png

Play In Editor

The Play In Editor settings allow you to change the mouse control behavior when in a Play In Editor session. These settings only apply for Play In Editor sessions that display in the Level Viewport. As a result, there are no default window sizes to set.

Setting

Description

Game Gets Mouse Control

Should Play-in-Editor automatically give mouse control to the game on PIE start (default = false). Note that this does not affect VR, which will always take focus

Show Mouse Control Label

Whether to show a label for mouse control gestures in the PIE view.

Mouse Control Label Position

Location on screen to anchor the mouse control label when in PIE mode.

Play in New Window

When starting a Play In Editor session that displays in a new window, these settings determine the size and starting position of the new window that appears.

Setting

Description

New Window Size (in pixels)

Sets the width and height of floating Play in Editor windows (in pixels):

  • The width of the new view port window in pixels (0 = use the desktop's screen resolution).

  • The height of the new view port window in pixels (0 = use the desktop's screen resolution).

  • Pick from a list of common window sizes, including settings for devices like phones and tablets.

New Window Position (in pixels)

Sets the screen coordinates for the top-left corner of floating Play In Editor windows (in pixels):

  • The position of the new view port window on the screen in pixels.

  • Whether the new window should be centered on the screen.

Play in Standalone Game

When starting a Play In Editor session that displays in a standalone game window, these settings determine the size and starting position of the new window that appears. There are also options that allow you to pass additional command line settings on to the game client.

Setting

Description

Standalone Window Size (in pixels)

Sets the width and height of standalone game windows (in pixels):

  • The width of the standalone game window in pixels (0 = use the desktop's screen resolution).

  • The height of the standalone game window in pixels (0 = use the desktop's screen resolution).

  • Pick from a list of common window sizes, including settings for devices like phones and tablets.

Client Command Line Options

Generates a command line for additional settings that will be passed to the game clients:

  • Extra parameters to be include as part of the command line for the standalone game.

Multiplayer Options

These are basic and advanced options for networked Play In Editor testing . In addition to the number of players and dedicated server options from the Play In dropdown menu, there are settings for URL parameters, gamepad routing, and reverting to the multiple-process testing method.

Setting

Description

Number of Players

The editor and listen server count as players, a dedicated server will not. Clients make up the remainder.

Server Game Options

Additional options that will be passed to the server as URL parameters, in the format ?bIsLanMatch=1?listen - any additional command line switches should be passed in the Command Line Arguments field below.

Run Dedicated Server

If checked, a separate dedicated server will be launched. Otherwise the first player will act as a listen server that all other players connect to.

Route 1st Gamepad to 2nd Client

When running multiple player windows in a single process, this option determines how the game pad input gets routed. If unchecked (default) then the 1st game pad is attached to the 1st window, 2nd to the 2nd window, and so on.

            If it is checked, the 1st game pad goes the 2nd window. The 1st window can then be controlled by keyboard/mouse, which is convenient if two people are testing on the same computer.

Use Single Process

Spawn multiple player windows in a single instance of [API:UE4] . This will load much faster, but has potential to have more issues.