War Thunder low FPS troubleshooting with a safe reset

War Thunder lists Windows 10 64-bit, 4 GB RAM, a DirectX 11-level GTX 660 or Radeon 77XX class GPU and 720p as the minimum PC baseline. Its recommended PC tier lists Windows 10 or 11, 16 GB RAM and a GTX 1060 or Radeon RX 570 class GPU. Official FAQ^[1]

These requirements are compatibility information, not a prediction of performance in a particular battle or graphics mode. Record the installed game build, Windows version, driver, resolution and active graphics API before troubleshooting.

War Thunder documents a direct-client safe mode for an invalid settings situation. Its FAQ lists -safe for minimum settings, -mode:windowed for windowed mode, -mode:fullscreen for fullscreen mode and -resolution:WidthxHeight for a selected valid resolution. The official example uses ./aces -safe -mode:windowed -resolution:1280x720.

That example is an official recovery reference, not a universal Windows launcher command. Verify the installed launcher and platform before entering launch parameters. Do not edit configuration files or copy community commands into the client.

A launch parameter is reversible because it is removed from the shortcut or launcher field that carried it. Record the original shortcut target before adding anything to it, so the previous state can be restored exactly.

The routine below records the current state first, uses the official path only for the situation it documents, then changes one value at a time and keeps the previous value whenever the new result is not preferred. Every step can be undone by restoring the value written down in step 1.

1. Record the active resolution, display mode and graphics settings if the client can open. Record the current shortcut target as well.
2. Use the official safe-start path only when invalid settings stop the client from launching normally. Remove the parameters again once the client opens.
3. Confirm that the client opens with the documented minimum settings baseline.
4. Restore one display or graphics setting at a time in the current client.
5. Test the same repeatable hangar view or mission segment after each change.
6. Keep the previous value when the new result is not preferred.

This process is a Setup workflow. It does not rank GPUs or recommend an upgrade.

War Thunder's April 2026 update states that on Intel Arc GPUs, launching with the DirectX 11 graphics API changes the game to DirectX 12 to avoid a crash. Update 2.55.1.47^[2]

This is a narrow compatibility statement for Intel Arc GPUs. It is not evidence that DirectX 12 is faster for every GPU, and it is not a reason to change the API together with other settings. Record the actual API selected by the installed client before drawing a conclusion.

The client, launcher and exact build need a local check. A field-tested version must include the PC, driver, resolution, scene, duration, repetitions and raw evidence before it reports an FPS, frame-time or latency result. This routine is now scoped as the shared general recovery baseline. Keep it free of update-specific diagnosis, which belongs in War Thunder low FPS after an update with a controlled recovery, slug war-thunder-low-fps-after-update.

• War Thunder FAQ^[1], War Thunder, checked September 13, 2026.
• Update 2.55.1.47^[2], War Thunder, published April 9, 2026.