Skip to content

Console and network graph

Press F2 to open the client console. Close it with F2 or Escape. Use the category tabs, text filter and severity selector to find relevant messages. Ctrl+F focuses the filter. When you scroll back or select text, automatic scrolling pauses. Jump to latest returns to live output.

Console access is enabled by default. If F2 does nothing, check the server’s config.toml:

[client_features]
console = true

After changing this setting, restart the server and let the client reconnect.

Enter a command and press Enter. Tab completes commands and arguments, and the up/down arrows recall previous commands.

Command Action
help List available commands.
help net_graph Show usage for a command.
net_graph 1 Show FPS, ping and incoming/outgoing traffic.
net_graph 2 Show all readings.
net_graph 0 Hide the network graph.
clear Clear the console view. Log files stay unchanged. Ctrl+L does the same.

For errors inside a WebView page, use CEF debugging.

You can also enable Net Graph in the pause menu under Settings → Multiplayer, including when the server has disabled the console. Readings appear in a compact strip at the top of the screen and wrap onto additional rows on narrower screens. The default view shows FPS, ping and IN/OUT traffic. Use net_graph 2 to add frame time, packet rates, delivery quality and queue statistics.

Reading Meaning
FPS and the adjacent ms Rendered frames per second and average time per frame over the sample period.
Ping Estimated round-trip time to the game server, in milliseconds.
IN / OUT Incoming and outgoing traffic for this client’s game-server connection, in B/s, KiB/s or MiB/s.
pkt/s Incoming and outgoing transport packets per second. Packets can contain batched entity updates or transport control data.
Quality Delivery quality measured by the client, then by the server. 100% means packets arrived in order. Lower values reflect loss or out-of-order delivery.
Queue Estimated time a new outgoing message would wait before transmission, in milliseconds.
Pending Client data waiting to be sent, including reliable data scheduled for retransmission.
Unacked Reliable data already sent by the client and awaiting acknowledgement.

-- means a reading is unavailable. Offline means the game-server connection is unavailable. Stale means the display has received no new sample for more than two seconds.

Watch the readings while reproducing the issue with GTA focused. Compare them with another connected client when possible.

Observation Next check
FPS drops while ping and queues remain stable Compare a quiet area with the affected scene. Check client script errors, entity density and WebView activity.
Ping rises or quality drops on one client Compare that client’s connection with another player and check competing network traffic.
Queue and Pending keep growing Check outgoing script-event traffic and the connection’s send rate. Compare the same period in the server logs.
Several clients see delayed updates while their FPS remains stable Inspect the server’s loop time and replication queues using server monitoring.

Unacked normally rises while reliable data is in flight. Compare sustained growth with ping, queue time and delivery quality.

For errors around the same time, open the client runtime log. The console keeps a limited history, so use the file when earlier messages have scrolled out. If GTA crashes or becomes unresponsive, collect the matching local report.