SUBTR-CT SUBTR-CT
On this page

Viewport AutoPause — Active Framerate Cap

Idle and focus pausing only reclaim power during the stretches you’re away. But for the hours you’re actively working, the editor renders the viewport far faster than editing actually needs — by default up to 120 FPS (or 60 on battery), most of which your monitor and your eyes never benefit from. The Active Framerate Cap reclaims that waste.

It’s an independent lever, separate from the pause modes: modes decide what wakes a paused viewport, while the cap decides how fast the viewport runs while you’re using it. The two compose — turning the cap on never changes how pausing behaves.

The Active Framerate Cap section of the right-click settings menu

What it does

When enabled, the cap limits the editor’s frame rate while you’re actively working to a ceiling you choose (the Active Max FPS value). Capping a viewport at, say, 60 FPS instead of letting it free-run to 120 roughly halves the frames the GPU draws — cutting power, heat, and fan noise across the bulk of a session, the part that idle pausing never reaches.

It can only ever lower your frame rate — never raise it

This is the load-bearing guarantee. The applied cap is clamped to whatever the editor would run at on its own:

  • the editor’s own default ceiling (120 FPS, or 60 on battery), and
  • any lower t.MaxFPS you’ve already set yourself.

So if you set the cap higher than what the editor would render anyway, it’s silently clamped back down. Enabling the cap can only ever save power — it can never cost you any, and it can never speed your editor up past its normal limit.

Choosing a value

Set Active Max FPS anywhere from 15 to 60 (the default is 60):

  • 60 — a good balance of smoothness and savings; the editor still feels fluid while you draw a fraction of the frames.
  • 30 — toward maximum power reduction, ideal on battery. Still perfectly workable for most editing, with a small hit to mouse-look smoothness.

There’s deliberately no “match my monitor’s refresh rate” option — on a 144 Hz+ display that would raise the rate above the editor’s default and cost power, defeating the purpose.

Good to know

  • Off by default. It’s strictly opt-in, so updating the plugin never changes behavior for existing users.
  • Ignored during Play in Editor and Simulate. The cap never throttles a playtest — the same bypass that protects pausing protects the cap.
  • Idle still wins. When the editor goes idle the viewport is paused outright (clamped far below any active cap), so the cap only matters while you’re working.
  • When the cap is off, the settings menu reminds you that the editor manages its own frame limit (typically up to 120 FPS, or 60 on battery), so you always know what you’re opting out of.

Turning it on

Right-click the toolbar button and find the Active Framerate Cap section:

  1. Toggle Cap Framerate While Active on.
  2. Set Active Max FPS to taste (15–60).

That’s it — the cap applies immediately and persists per-user across editor sessions, like every other setting. See Settings & Toolbar for the full menu, or How It Works for the t.MaxFPS mechanics under the hood.