Editor and Play-In-Editor

Work the editor itself: viewport camera, Play-In-Editor, console, undo and redo, saving and screenshots.

What it’s for

Ask your assistant to work the editor itself. It can move the viewport camera, switch view modes, start and stop Play-In-Editor, run console commands, undo and redo, save everything, open assets and levels, and take screenshots. If the task is something you would do in the editor’s interface, it happens here.

Common requests: frame an actor and take a screenshot to review; play the level and step it one frame at a time to debug; turn on Game View or wireframe before a capture; run a Stat or r. console command; save everything after a batch of edits.

Starting, stopping, pausing and stepping a play session are safe to ask for at any time. If the game is already running or already stopped, your assistant is told so and nothing breaks.

Console commands here run in the editor’s world, which suits Stat commands, r.ScreenPercentage and view mode changes. Engine-wide commands are covered in Builds, tests and jobs.

Things you can ask

Frame an actor and capture it for review

Your assistant points the camera at the actor and saves a PNG you can look at.

You: Point the camera at PlayerStart and take a screenshot.

Framed PlayerStart and saved Saved/Screenshots/player_start.png.

Step a play session one frame at a time

Your assistant starts the game, moves it forward one frame, then goes back to editing.

You: Play the level, step one frame, then stop.

Started Play-In-Editor, stepped one frame and returned to edit mode.

Move the camera and switch the view mode

The viewport camera moves to the spot you give and renders unlit for a clean capture.

You: Put the camera at (500, 0, 300) looking down 20 degrees and switch to Unlit.

The camera is at (500, 0, 300) looking down 20 degrees, and the viewport is set to Unlit.