Escape from Tarkov Wiki

You noticed wrong or missing information? Tell us on our discord server or learn how to edit.

READ MORE

Escape from Tarkov Wiki
Advertisement

The Debug Console can be used to execute various commands for debug and testing purposes.

Usage

To open and close the console, use the key specified in your controls options. ESC also closes it.

It features commands with and without arguments, basic auto-complete via the arrow and TAB keys, as well as command groups separated by a dot.

Since there is no help command, you can make use of a trick in the auto-complete feature to show all commands. Simply type in a dot followed by any letter and all available commands will show up, except for command groups, in which case only the group name will be shown.

EFT Debug Console.PNG

Commands

Below, you can find a list of commands usable in the debug console. Text in square brackets, [], are parameters and need to replaced with numbers or words, depending on what fits. Keep in mind that numbers have to be full numbers without any decimal places and words can't have any spaces in them.

fps [mode]

The fps command enables a performance and debug overlay in the top-right corner of the screen. The [mode] parameter is used to control the amount of information visible in the overlay:

Mode Information
0 Overlay disabled
1 FPS Limit, Current FPS
2 FPS Limit, Current FPS, RTT/Ping, Packet Loss, Player RTT
3 FPS Limit, Current FPS, RTT/Ping, Packet Loss, Player RTT, Various "Fixed Update" Measurements, Update Time in ms, Game Update Time in ms, Render Time in ms, Total Frame Time in ms

performance.report

The performance.report command group is used for performance testing. It allows you to start and stop logging of various performance values at a fixed interval of 1 second. See below for the commands in the group:

performance.report.start [optional:filename]

The performance.report.start command is used to start a performance test, which also sets the performance overlay to mode 2. If a file name is provided, the output file can be found in the game folder, next to the games executable. If a file name is not provided, it can be found in the latest log folder in the game files, ending with "FDebug_performancereport".

performance.report.stop

The performance.report.stop command is used to stop a performance test.

perftest [overall] [every] [label]

The perftest command is an alternative, older command used for performance testing. Similarly to the performance.report command group, it is used for performance testing. Using the command also sets the performance overlay to mode 3 and, for reasons unknown and possibly a bug, forces a new log folder to be created and used for any game logs of the current session.

It is not recommended to use this command over the the performance.report command group due to its limited flexibility and less amount of logged data, as well as potential bugs.

Parameter Information
overall Total length of the performance test, in seconds.
every Interval in which performance values are logged, in seconds.
label Name of the perfomance test, so it can be found easily in the outfile file, since it can store multiple tests at the same time.

The output file can be found in the latest log folder in the game files, ending with "FDebug_perftest".

quit

The quit command can be used to force-close the game without the need for system tools, like the task manager, or system key combinations, such as ALT+F4.

quit_with_code [code]

The quit_with_code command is similar to the quit command in the sense that it can be used to force-close the game, however it takes an additional parameter, [code], which allows an exit/error code to be specified.

wait [seconds]

The wait command currently has no known use, but takes a parameter [seconds].

Advertisement