FIRESTARTERS VSync and FPS Limit: Why the Numbers Differ

Why can VSync show 288 FPS on a 144 Hz display?

A player reported exactly that behavior, and the developer explained the distinction. The engine prefers a low-latency driver implementation intended to prevent tearing. It may not cap FPS to the monitor’s refresh rate; the behavior can vary with the GPU, driver, display and window mode.

The FPS number alone therefore does not demonstrate that this implementation failed. Look at which outcome you are trying to control.

Which setting should you use for an FPS cap?

Use the dedicated Framerate Limit option. That is the developer’s recommendation when the goal is restricting frame rate, including for power use. Their reply also says the limiter and VSync can be used together: one chooses a cap while the other addresses tearing.

Your goal	Setting to inspect
Restrict the game’s FPS	Framerate Limit
Address screen tearing	Vertical Sync
Apply a cap and address tearing	Both options, then check the result

The February 13 demo notes introduced frame-limit values of 30, 60, 120, 144, 240, 360 and Unlimited. This historical list is useful context, not an independently checked inventory of every option in the current release.

How can you compare settings without losing track?

Record the current display mode and limit, change one setting, and compare the behavior in the same scene. This is a general comparison method; it does not predict your hardware’s latency or performance. There is no benchmark here establishing a universally best cap for competitive play.

For a startup failure rather than a frame-rate question, use the GPU troubleshooting page and log-location guide. The PC requirements page lists the published hardware baseline.

Developer explanation and demo patch context checked November 2, 2026.