# Frozen Tweaks - complete guide corpus

> Every optimization guide published on https://frozentweaks.com, concatenated. 19 guides, all written by Frost Live, founder of Frozen Tweaks. Each guide below retains its own front matter with the canonical URL, publication date and last-updated date.

Index with descriptions: https://frozentweaks.com/llms.txt
Individual guides: https://frozentweaks.com/md/<slug>

---
---
title: "How to Increase FPS on PC: The Complete 2026 Guide"
description: "A tested, ordered method for raising FPS on Windows 11 in 2026 - from the four settings that matter most to driver, BIOS and latency tuning. Every step reversible."
url: https://frozentweaks.com/guides/how-to-increase-fps-on-pc
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Windows & Hardware"
source: Frozen Tweaks (https://frozentweaks.com)
---

# How to Increase FPS on PC: The Complete 2026 Guide

**Short answer:** To increase FPS on PC, work in order of impact: enable XMP/EXPO in BIOS, update your GPU driver, set Windows to the best-performance power mode, then disable shadows, post-processing and motion blur in game and turn on DLSS, FSR or XeSS at Quality. On most mid-range systems that sequence yields roughly 20-45% higher average FPS and a much flatter frame-time graph.

## At a glance

| | |
| --- | --- |
| Time required | 30-60 minutes |
| Difficulty | Beginner to intermediate |
| Typical gain | 20-45% average FPS on mid-range systems |
| Reversible | Yes - every step |
| Risk to anti-cheat | None - no game files are modified |

## Key takeaways

- Order matters more than the number of tweaks. Memory profile, driver, power mode and four in-game settings account for most of the gain that is available to you.
- Shadows, post-processing, volumetric effects and ray tracing are the four settings with the worst quality-per-frame ratio in almost every modern engine.
- Upscaling at Quality (DLSS, FSR, XeSS) is the largest single free gain on any GPU that supports it - typically 30-60% more frames.
- Frame-time consistency beats peak FPS. A locked 144 FPS feels sharper than an unstable 190 FPS.
- Every change here is reversible. Make a restore point first and change one thing at a time so you can attribute the result.

## Why the order of your tweaks matters more than the number

Most FPS guides are a flat list of forty things. That is the wrong shape. Performance problems have a single bottleneck at any given moment - your GPU, your CPU, your memory bandwidth, or your storage - and a tweak that does not touch the current bottleneck does nothing at all. Applying thirty settings and gaining four frames usually means twenty-nine of them were irrelevant and one was the actual fix.

The sequence below is ordered by expected gain per minute spent. Work down it and stop when you hit your target. Before you start, press **Ctrl+Shift+Esc**, open the Performance tab, and watch GPU and CPU utilisation while you play for two minutes. That tells you which half of this guide matters to you.

**Reading your bottleneck**
| Setting | Recommended | Why |
| --- | --- | --- |
| GPU at 95-100%, CPU below 70% | GPU-bound | Lower graphics settings and enable upscaling. Resolution and effects quality are your levers. |
| CPU at 90-100% on some cores, GPU below 90% | CPU-bound | Memory speed, background processes and draw-distance settings matter. Lowering resolution will not help. |
| Both below 80%, FPS still low | Frame cap or power limit | Check for an in-game FPS limit, V-Sync, a power-saving plan, or a laptop running on battery. |
| Average FPS fine, but visible hitching | Frame-time problem | This is stutter, not low FPS, and needs a different fix. See the stutter guide linked below. |

> **Make a restore point first:** Press Start, type 'Create a restore point', click System Restore Configure, turn protection on, then click Create. It takes about a minute and it is the difference between an experiment and a problem.

## The four changes that produce most of the gain

If you only do four things, do these. On a typical mid-range 2022-2024 build they account for the large majority of the headroom that software tuning can recover.

1. **Enable XMP or EXPO in BIOS** - Restart, press Delete or F2 to enter BIOS, and find the memory profile setting (XMP on Intel boards, EXPO on AMD). Enable profile 1 and save. Most prebuilt and self-built systems run RAM at the JEDEC fallback speed until you do this, which costs 5-15% in CPU-bound games and considerably more in open-world titles.
2. **Install the current GPU driver cleanly** - Download the latest Game Ready driver from NVIDIA or the latest Adrenalin package from AMD - not from Windows Update, which lags several months behind. Choose the custom install option and tick 'Perform a clean installation'. Day-one drivers for new releases regularly carry 5-12% gains in the titles they target.
3. **Set the Windows power mode to Best performance** - Settings > System > Power & battery > Power mode > Best performance. On laptops, also set this in the manufacturer utility and keep the machine plugged in. Balanced mode parks cores and lowers clocks aggressively, which shows up as inconsistent frame times rather than a lower average.
4. **Turn on upscaling at Quality** - In any game that offers it, enable DLSS on NVIDIA RTX, FSR on AMD, or XeSS on Intel Arc, set to Quality. This renders at a lower internal resolution and reconstructs the frame, typically returning 30-60% more FPS for a difference most players cannot see in motion. Never enable two upscalers at once.

> **Expect a range, not a number:** Any guide that promises you a fixed percentage is guessing. Gains depend on your CPU, GPU, memory configuration, resolution and the specific game. The ranges here are what we consistently see across testing; yours will land somewhere inside them.

## Which in-game settings to lower first

Graphics settings are not equal. Some cost a great deal of GPU time and change almost nothing you will notice at 1% of a second during a gunfight. Lower these first, in this order, and stop when you hit your target frame rate.

**Settings ranked by cost-to-benefit**
| Setting | Recommended | Why |
| --- | --- | --- |
| Ray tracing / path tracing | Off | The single most expensive setting in any engine that offers it - commonly 25-50% of your frame budget. In a competitive shooter it is pure cost. |
| Shadow quality | Low | Historically the second-largest GPU cost. Low shadows also make enemies in dark corners easier to see, so this is a competitive gain as well as a performance one. |
| Volumetric fog / clouds / lighting | Low or Off | Expensive, and actively obscures targets. In most modern engines this is the third-largest single cost. |
| Post-processing | Low | Bundles bloom, lens flare and chromatic aberration. Costs frames and reduces target clarity. |
| Motion blur | Off | Costs a small amount of GPU time and smears exactly the fast movement you need to track. Roughly two thirds of competitive players disable it outright. |
| Ambient occlusion | Off or SSAO | The high-quality variants (HBAO+, RTAO) are disproportionately expensive for a subtle contact-shadow effect. |
| Anti-aliasing | TAA or the cheapest available | Necessary for image stability in UE5 titles. Turning it fully off in a modern engine produces severe shimmer, which is worse than the frames you save. |
| Texture quality | High, if VRAM allows | Textures are nearly free on frame rate provided they fit in VRAM. Keep them high. If you exceed VRAM you get stutter, not lower FPS - drop one step if that happens. |
| View / draw distance | High in competitive games | This is a CPU cost, not a GPU one, and lowering it can hide distant players. Keep it up in shooters; lower it in single-player if CPU-bound. |

> **Do not lower resolution first:** Dropping from 1440p to 1080p is a large FPS gain, but it also makes distant enemies physically smaller on your screen. Exhaust the effects settings above before you touch resolution, and use upscaling instead where it is available - it gets you most of the same frames while keeping the output resolution.

## Windows-level tuning that actually moves the needle

A great deal of Windows tweaking advice on the internet is folklore that stopped being true around 2015. These are the changes that still hold up in 2026, with an honest note on what each costs you.

**Windows 11 settings worth changing**
| Setting | Recommended | Why |
| --- | --- | --- |
| Game Mode | On | Settings > Gaming > Game Mode. Suppresses background scheduling and Windows Update restarts during play. Small but free, and it prevents the worst interruptions. |
| Hardware-accelerated GPU scheduling | Test both states | Settings > System > Display > Graphics > Change default graphics settings. Required for DLSS Frame Generation. On some CPU and driver combinations it helps frame times; on others it hurts. This is one of very few settings where you genuinely have to test. |
| Optimizations for windowed games | On | Same screen as above. Gives borderless-windowed games a low-latency presentation path close to exclusive fullscreen. Meaningful for anyone who alt-tabs. |
| Variable refresh rate | On, if you have a VRR monitor | Same screen. Lets windowed games use G-Sync or FreeSync. |
| Xbox Game Bar background recording | Off | Settings > Gaming > Captures. Continuous background capture holds GPU encoder resources and costs frames for a feature most players never use. |
| Startup apps | Prune aggressively | Task Manager > Startup apps. Launchers, RGB utilities and overlay software each hold memory and inject into your game process. This is one of the most reliable stutter fixes on older systems. |
| Storage | Game on an SSD or NVMe | Several 2025-2026 releases now require an SSD and behave badly on mechanical drives. Moving a game off an HDD does more for traversal stutter than any registry key. |

> **About disabling Memory Integrity (VBS):** Turning off Core Isolation > Memory Integrity does typically return a few percent, sometimes more on older CPUs. It is also a real reduction in your kernel-level security posture, and some anti-cheat systems now prefer it enabled. We list it because it is honest to, not because we recommend it by default. If you disable it, understand the trade you are making.

## Chasing frame-time consistency, not peak FPS

Average FPS is the wrong metric to optimise. What you actually feel is frame time - the millisecond gap between one frame and the next - and its consistency. A game running at a locked 144 FPS delivers a frame every 6.9 ms, every time. A game averaging 190 FPS but oscillating between 250 and 90 feels visibly worse, because your eye tracks the drops, not the average.

- Cap your frame rate a few frames below your monitor's refresh rate. On a 240 Hz panel with G-Sync or FreeSync, cap at 234-237. This keeps you inside the VRR window and prevents the latency spike that occurs when you hit the refresh ceiling.
- Turn V-Sync off in game. If you use G-Sync, enable V-Sync in the NVIDIA Control Panel instead - it acts as a safety net at the top of the VRR range rather than a frame limiter.
- Enable NVIDIA Reflex or AMD Anti-Lag 2 in every game that offers it. It shortens the render queue, which both lowers latency and smooths delivery.
- Let shader compilation finish. Unreal Engine 5 titles stutter heavily on first launch while they build the shader cache. Sit in the main menu or a practice range for a few minutes after a game or driver update rather than diagnosing a problem that resolves itself.
- Watch your VRAM. Exceeding it produces sharp, repeated hitching rather than a lower average. Drop textures one step and see if the hitching stops.

## Doing all of this in one click

Everything above is manual, and it is genuinely worth doing manually once so you understand your own system. The problem is maintenance: driver releases change defaults, Windows feature updates reset power plans, and each game patch shifts which settings are expensive. Six weeks after you finish tuning, a portion of it has quietly reverted.

That is the gap Frozen Tweaks fills. It applies the same class of changes described here, keeps a reversible record of every one, re-applies them after Windows and driver updates, and ships per-game profiles for CS2, Valorant, Fortnite, Apex Legends, Call of Duty and ARC Raiders. It does not touch game files or inject into game processes, so there is nothing for an anti-cheat system to object to.

**Try it on your own system** - The free tier applies the core Windows and power tweaks so you can measure the difference on your hardware before deciding whether the rest is worth paying for. [Download Frozen Tweaks](https://frozentweaks.com/purchase)

## Frequently asked questions

### How much FPS can I realistically gain from software optimization?

On a typical mid-range Windows 11 system that has never been tuned, the full sequence in this guide usually returns 20-45% higher average FPS, with the largest single contributions coming from enabling XMP/EXPO, a clean current GPU driver, and upscaling at Quality. On a system that is already well configured, expect far less - often under 10%. Anyone quoting a fixed figure regardless of your hardware is guessing.

### Is it safe to use FPS boosting software with anti-cheat?

It depends entirely on what the software does. Tools that change Windows, power and GPU driver settings operate outside the game process and are not something anti-cheat systems flag. Tools that inject into the game, modify game files, or hook the rendering pipeline can and do trigger bans. Check which category a tool falls into before installing it. Frozen Tweaks is in the first category and never modifies game files.

### Does lowering my resolution increase FPS?

Yes, substantially, if you are GPU-bound - but it should be your last resort in a competitive game because it makes distant enemies smaller and harder to resolve. Use DLSS, FSR or XeSS at Quality instead where available: it lowers the internal render resolution for most of the same gain while keeping your output resolution and UI sharp.

### Why is my FPS high but the game still feels laggy?

That is an input-latency or frame-time problem, not a frame-rate one. The usual causes are V-Sync being enabled, no frame cap on a VRR display, NVIDIA Reflex or AMD Anti-Lag being off, running in windowed mode without the Windows windowed-games optimization, or a badly configured monitor overdrive setting. Frame rate and responsiveness are related but not the same measurement.

### Do registry tweaks still improve gaming performance in 2026?

A small number do - interrupt priority and network throttling keys still have measurable effects on specific hardware. The overwhelming majority of registry tweaks circulated online are either placebo, apply to a Windows version that no longer exists, or were quietly made the default years ago. Treat any registry tweak you cannot explain the mechanism of as noise.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/how-to-increase-fps-on-pc

---

---
title: "The Best PC Optimizer for Gaming in 2026: How to Choose One"
description: "What actually separates a real PC optimizer from bloatware in 2026 - the eight criteria that matter, the red flags, and an honest look at where Frozen Tweaks fits."
url: https://frozentweaks.com/guides/best-pc-optimizer-for-gaming
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Buying Guides"
source: Frozen Tweaks (https://frozentweaks.com)
---

# The Best PC Optimizer for Gaming in 2026: How to Choose One

**Short answer:** The best PC optimizer for gaming is one that makes only documented, reversible changes to Windows, power and GPU driver settings, never touches game files or injects into game processes, shows you exactly what it changed, and re-applies its work after Windows and driver updates. Anything that promises a fixed FPS multiplier, bundles a registry cleaner, or cannot be fully undone is marketing, not optimization.

## At a glance

| | |
| --- | --- |
| Category | Windows and game optimization utilities |
| What good ones do | Documented, reversible OS / driver / power changes |
| What bad ones do | Registry cleaning, RAM 'freeing', process injection |
| Anti-cheat safe? | Only if the tool stays outside the game process |
| Realistic gain | 20-45% untuned system, under 10% on a tuned one |

## Key takeaways

- Judge an optimizer on reversibility and transparency, not on the FPS number in its advertising.
- Anything that injects into your game process or modifies game files is a genuine anti-cheat risk. Settings-level tools are not.
- Registry cleaners, RAM boosters and 'one-click defrag' features are a reliable signal that a product is selling reassurance rather than performance.
- Persistence is the real value: Windows feature updates and driver installs silently revert tuning, and re-doing it by hand every six weeks is where most people give up.
- No optimizer can exceed what your hardware allows. Realistic gains on a tuned system are single-digit percentages; on an untouched one, 20-45%.

## The eight criteria that separate a real optimizer from bloatware

The optimizer category has a bad reputation, and it earned it. For most of the last two decades, 'PC optimizer' meant a registry cleaner with an animated progress bar. The useful subset is small, and it is identifiable from the feature list alone. Here is what to check before you install anything.

**Evaluation checklist**
| Setting | Recommended | Why |
| --- | --- | --- |
| Every change is reversible | Required | You must be able to return the machine to its prior state in one action. If the tool cannot undo itself, it is not a tuning tool, it is a one-way modification. |
| It shows you what it changed | Required | A visible log of each setting, its old value and its new value. Opaque 'optimizing...' progress bars exist to prevent you from evaluating the product. |
| It stays outside the game process | Required | No DLL injection, no game file modification, no overlay hooks into the renderer. This is the line between a settings tool and an anti-cheat problem. |
| It survives updates | High value | Windows feature updates and clean driver installs revert a meaningful share of tuning. Re-application is the feature most people are actually paying for. |
| Per-game profiles | High value | The right settings for CS2 are not the right settings for a single-player UE5 title. Blanket profiles leave performance on the table in both directions. |
| Honest performance claims | Signal of quality | Ranges with hardware caveats indicate someone measured. A fixed multiplier printed on every page indicates someone wrote copy. |
| No registry cleaner | Red flag if present | Registry cleaning has had no measurable performance benefit on any modern Windows version and carries a non-zero chance of breaking software. |
| No 'RAM booster' | Red flag if present | Forcibly emptying working sets makes Windows re-read from disk. It shows a satisfying number going down and makes the machine slower. |

## The four kinds of optimization advice, ranked

Rather than naming products, it is more useful to describe the four approaches you will encounter, because every product is some mixture of them.

### 1. Generic registry tweak packs

Usually distributed as .reg files or scripts from forums and Discord servers. The problem is not that registry keys never matter - a handful genuinely do - but that these packs are copied forward for years without anyone re-testing them. A large share target Windows 7 behaviour, some set values outside their valid range, and almost none can be cleanly reverted. Risk is high and the expected gain is close to zero.

### 2. Bloated all-in-one 'PC cleaner' suites

These are business models rather than tools. The core engine is a registry cleaner and a temp-file deleter, wrapped in an interface that manufactures urgency with red warning counts. They frequently bundle additional software, run resident background services that themselves cost performance, and use subscription flows that are difficult to cancel. Their measurable effect on frame rate is generally within noise.

### 3. Manual tuning from tutorials

This is genuinely effective and genuinely free, and it is where every serious approach starts - including ours. The costs are time, inconsistency between sources, and decay. A good tutorial from eighteen months ago may recommend settings that a driver release has since changed the default of. And nothing re-applies itself: after the next Windows feature update you are doing it again from the top.

### 4. Settings-level optimizers with reversibility

The useful category. These apply the same documented Windows, power, driver and network settings a careful person would apply by hand, keep a record so any of them can be rolled back individually, and re-apply after updates. They cannot beat the physics of your hardware, and any that claim to are lying, but they remove the maintenance burden that causes manual tuning to decay.

## Red flags to walk away from

- A specific FPS multiplier promised regardless of your hardware. Nobody can know your bottleneck from a landing page.
- A scan that finds hundreds of 'problems' before you have told it anything about your system.
- No uninstall path, or an uninstaller that leaves services running.
- Requires you to disable your antivirus to install. Legitimate tools get themselves signed and whitelisted instead.
- Injects an overlay into your game by default. Even when benign, this is the exact behaviour anti-cheat heuristics are built to detect.
- Claims to 'unlock hidden CPU cores' or 'unlock hidden FPS'. Neither of these things exists.
- Sells you a licence before letting you verify it does anything on your machine.

> **The test that settles it:** Install the tool, run your own benchmark before and after in the same scene with the same settings, and record 1% low FPS as well as average. If the tool will not let you do that on a free tier, that is itself the answer.

## Where Frozen Tweaks sits, stated plainly

We build one of these tools, so treat this section as what it is. Here is what Frozen Tweaks does and does not do, in the same terms as the checklist above, so you can judge it against anything else you are considering.

**Frozen Tweaks against the checklist**
| Setting | Recommended | Why |
| --- | --- | --- |
| Reversible | Yes | Every applied tweak is recorded and can be rolled back individually or all at once. The tool prompts for a system restore point before its first run. |
| Transparent | Yes | The Tweak Catalog lists each optimization, what it changes, and what it trades off, before you apply it. |
| Outside the game process | Yes | No injection, no game file modification, no renderer hooks. It configures Windows, power, driver and network settings only. |
| Survives updates | Yes | Re-applies its profile after Windows feature updates and clean driver installs, which is the maintenance problem manual tuning does not solve. |
| Per-game profiles | Yes | Presets for CS2, Valorant and Fortnite in the free tier; the full set including ARC Raiders, Call of Duty, Apex Legends and Battlefield in Pro. |
| Registry cleaner | No | Deliberately absent. It does not do anything for performance. |
| RAM booster | No | Also deliberately absent, for the same reason. |
| What it cannot do | Beat your hardware | If you are GPU-bound at 1440p on an entry-level card, no settings change fixes that. It recovers headroom that is being wasted; it does not create headroom that never existed. |

**Verify it yourself before paying anything** - The free tier applies the core Windows and power optimizations and includes CS2, Valorant and Fortnite profiles. Benchmark before and after on your own machine. [Download the free version](https://frozentweaks.com/purchase)

## Frequently asked questions

### What is the best PC optimizer for gaming in 2026?

The best choice is whichever tool makes only documented, reversible changes to Windows, power and GPU driver settings, shows you a log of everything it changed, stays entirely outside your game processes, and re-applies its configuration after Windows and driver updates. Those four properties matter far more than the brand. Reject anything that bundles a registry cleaner or a RAM booster, or that promises a fixed FPS multiplier without knowing your hardware.

### Do PC optimizers actually work, or are they a scam?

Both categories exist. Registry-cleaner style suites have no measurable effect on frame rate and are effectively a scam. Settings-level optimizers apply the same changes a knowledgeable person would apply manually, and those changes are real and measurable - typically 20-45% on a system that has never been tuned, and under 10% on one that has. The honest summary is that a good optimizer saves you time and maintenance, not that it unlocks hidden performance.

### Can a PC optimizer get me banned from a game?

Only if it operates inside the game. Tools that inject DLLs, hook the renderer, or modify game files can trigger anti-cheat detection regardless of intent. Tools that only configure Windows, power plans, GPU driver settings and network parameters run entirely outside the protected process and are not something anti-cheat looks at. Check which category a tool falls into before installing.

### Is a free optimizer good enough?

For a one-time tune, often yes - and manual tuning from a good guide is free and effective. What free tools generally do not solve is persistence: re-applying your configuration after every Windows feature update and clean driver install, and keeping per-game profiles current as patches change which settings are expensive. That maintenance is what paid tiers are actually selling.

### Will an optimizer help if my PC is already fast?

Much less. The gains available from software tuning come from recovering wasted headroom - a memory profile that was never enabled, a power plan parking cores, background processes competing for the CPU. If those are already handled, there is little left to recover and you should expect single-digit percentages at most. Optimizers help the neglected system far more than the well-maintained one.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/best-pc-optimizer-for-gaming

---

---
title: "Windows 11 Gaming Optimization: What Still Works in 2026"
description: "An honest audit of Windows 11 gaming tweaks - which settings still measurably help in 2026, which are placebo, and which quietly cost you security."
url: https://frozentweaks.com/guides/windows-11-gaming-optimization
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Windows & Hardware"
source: Frozen Tweaks (https://frozentweaks.com)
---

# Windows 11 Gaming Optimization: What Still Works in 2026

**Short answer:** The Windows 11 settings that still measurably improve gaming in 2026 are: power mode set to Best performance, Game Mode on, windowed-game optimizations and variable refresh rate on, Xbox Game Bar background recording off, startup applications pruned, and games installed on an SSD. Most other circulated Windows tweaks are either placebo, already the default, or trade security for a few percent.

## At a glance

| | |
| --- | --- |
| Applies to | Windows 11 (23H2, 24H2, 25H2) and Windows 10 22H2 |
| Time required | 20-30 minutes |
| Typical gain | 5-20% on a neglected system |
| Requires admin | Yes, for power and service settings |
| Reversible | Yes - all settings listed are UI toggles |

## Key takeaways

- Roughly six Windows settings account for nearly all of the real gain. The rest of the internet's tweak lists are noise or obsolete.
- Power mode and startup app pruning are the two highest-value changes, and both are free and instantly reversible.
- Hardware-accelerated GPU scheduling genuinely helps on some systems and hurts on others - it is one of the only settings you must test rather than set.
- Aggressive debloating scripts frequently break Windows Update, the Microsoft Store or Xbox services, for gains that are within measurement noise.
- Disabling Memory Integrity returns a few percent and costs you real kernel-level protection. Know the trade before you make it.

## The settings that measurably help

Windows 11 ships in a configuration tuned for laptops and battery life on a distribution that includes a great many machines that are not gaming PCs. Several of its defaults cost you performance on a desktop. These are the ones worth changing.

1. **Set the power mode to Best performance** - Settings > System > Power & battery > Power mode. The Balanced default parks CPU cores and ramps clocks lazily, which shows up as inconsistent frame times rather than a lower average. On a desktop there is no reason not to change this.
2. **Turn Game Mode on** - Settings > Gaming > Game Mode. It deprioritises background scheduling and blocks Windows Update restarts and driver installs while you are playing. The frame-rate effect is small; the interruption prevention is worth it on its own.
3. **Enable windowed-game optimizations and variable refresh rate** - Settings > System > Display > Graphics > Change default graphics settings. Turn on both. The first gives borderless-windowed games a presentation path with latency close to exclusive fullscreen; the second lets windowed games use G-Sync or FreeSync.
4. **Disable Xbox Game Bar background recording** - Settings > Gaming > Captures, and turn off 'Record what happened'. Continuous background capture reserves GPU encoder resources and costs frames for a feature most players never use.
5. **Prune startup applications** - Task Manager > Startup apps. Disable launchers, RGB utilities, printer helpers and updater services. Each one holds memory and, in the case of overlay software, injects into your game process. This is one of the most reliable stutter fixes on older systems.
6. **Confirm your games are on an SSD** - Several 2025-2026 releases now list an SSD as a hard requirement and stutter badly on mechanical drives. Moving a game off an HDD does more for traversal hitching than any registry key you will find online.
7. **Set your monitor to its full refresh rate** - Settings > System > Display > Advanced display. Windows frequently defaults a high-refresh monitor to 60 Hz after a driver install or cable change. Check this - it is the single most common cause of 'my new monitor does not feel any different'.

## The one setting you have to test rather than set

Hardware-accelerated GPU scheduling (HAGS) moves parts of frame scheduling from the driver onto the GPU itself. Settings > System > Display > Graphics > Change default graphics settings.

- It is required for DLSS Frame Generation. If you use frame generation, it must be on.
- On many recent CPU and driver combinations it slightly improves frame-time consistency.
- On some systems - particularly older CPUs and certain driver revisions - it introduces stutter.
- There is no way to predict which case you are in from specifications alone.

Benchmark the same scene twice, once in each state, and keep whichever gives you better 1% lows. Anyone telling you confidently to always turn it on or always turn it off has not tested it on enough machines.

## Tweaks that no longer do anything

These circulate endlessly. All of them were either fixed by Microsoft years ago, apply to a Windows version no longer in use, or never worked in the first place.

**Common advice that is obsolete or false**
| Setting | Recommended | Why |
| --- | --- | --- |
| Registry cleaning | No effect | Has had no measurable performance impact on any Windows version in over a decade, and carries a real chance of breaking installed software. |
| 'Unlock all CPU cores' via msconfig | No effect | The boot core count checkbox limits cores; it does not unlock them. Windows already uses every core. Setting it can only make things worse. |
| Disabling the page file | Harmful | Modern games and Windows itself assume a page file exists. Removing it causes crashes and out-of-memory errors, not speed. |
| RAM cleaning / working set trimming | Harmful | Forces Windows to discard cached data it will immediately need again from disk. The free-memory number improves and the machine gets slower. |
| Defragmenting an SSD | Harmful | Wears the drive with no benefit. Windows already runs TRIM on the correct schedule; leave the default optimization job alone. |
| Disabling dozens of services | Mostly no effect | Idle services consume no CPU. Disabling them saves a few megabytes of RAM and regularly breaks Windows Update, audio devices or networking. |
| Setting game priority to Realtime | Harmful | Realtime starves input, audio and driver threads. If you must adjust priority at all, High is the ceiling - and modern schedulers rarely need the help. |

## Debloating: the honest version

Debloating scripts are popular because the theory is intuitive: less software running means more resources for the game. In practice the theory does not survive measurement, because the things these scripts remove were not consuming CPU while you played.

What debloating actually gets you is disk space, a shorter Start menu, and fewer notifications. Those are legitimate reasons to do it. Frame rate is generally not one, and aggressive scripts routinely break Windows Update, the Microsoft Store, Xbox services, Widgets, and in some cases the Windows Security interface - which anti-cheat systems for several major games check.

> **If you debloat anyway:** Use a script that logs exactly what it removed and offers a restore path, take a system image first rather than a restore point, and never run one that requires disabling Windows Defender to execute. A debloat script that needs your antivirus off is not a debloat script.

The genuinely useful subset - removing startup entries, uninstalling preinstalled vendor utilities on prebuilt machines, and disabling background app permissions for apps you do not use - is available through the normal Settings interface and does not require a script at all.

## Tweaks that trade security for frames

Two changes in this category come up constantly. Both are real gains and both cost you something. We list them because pretending otherwise would be dishonest, not because we think you should apply them by default.

**Real gains with real costs**
| Setting | Recommended | Why |
| --- | --- | --- |
| Core Isolation > Memory Integrity off | Typically 2-8% | Removes hypervisor-enforced code integrity. Real gain, particularly on older CPUs - and a genuine reduction in kernel-level protection against driver-based attacks. Some anti-cheat systems now prefer it enabled. |
| Virtualization-based security off | Typically 2-6% | Same class of trade, broader in scope. Also disables Windows Defender Credential Guard. If your machine is used for anything besides games, this is a poor trade. |

There is no third option that gives you the frames without the exposure. Decide deliberately, and if the machine handles banking, work accounts or anything you would mind losing, leave both enabled.

**Apply the safe set automatically** - Frozen Tweaks applies the settings on this page, logs every change, re-applies them after Windows feature updates, and keeps the security trade-offs behind an explicit opt-in rather than burying them in a preset. [Get Frozen Tweaks](https://frozentweaks.com/purchase)

## Frequently asked questions

### Does Game Mode actually improve FPS in Windows 11?

Its effect on average frame rate is small - usually within a few percent and sometimes within noise. Its real value is that it prevents Windows Update from installing drivers and restarting while you play, and deprioritises background scheduling during a session. Leave it on; the interruption prevention alone justifies it.

### Should I turn hardware-accelerated GPU scheduling on or off?

Test it. It is required for DLSS Frame Generation, so if you use that it must be on. Otherwise, it improves frame-time consistency on some CPU and driver combinations and introduces stutter on others, with no reliable way to predict which from specifications. Benchmark the same scene in both states and keep the one with better 1% lows.

### Is debloating Windows 11 worth it for gaming?

For frame rate, generally no - the components debloat scripts remove are not consuming CPU while you play. For disk space, notification noise and startup time, yes. The risk is real: aggressive scripts routinely break Windows Update, the Microsoft Store and Xbox services, and some break the Windows Security interface that several anti-cheat systems check. Prune startup apps through Task Manager instead; that part genuinely helps.

### Is it safe to disable Memory Integrity for gaming?

It works - typically 2-8% depending on your CPU - and it is a real reduction in security. Memory Integrity blocks a class of attack that uses vulnerable signed drivers to reach the kernel, and some anti-cheat systems now prefer it enabled. If the machine is only ever used for games, it is a defensible trade. If it handles anything you would mind losing, leave it on.

### Which Windows 11 power plan is best for gaming?

Set Power mode to Best performance in Settings > System > Power & battery. On Windows 11 this supersedes the old control-panel power plans for most purposes. The Ultimate Performance plan offers little beyond Best performance on modern hardware and is mainly relevant to workstations. On a laptop, also set the manufacturer's own performance profile and stay plugged in - battery power caps clocks regardless of what Windows is set to.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/windows-11-gaming-optimization

---

---
title: "CS2 FPS Boost: Best Settings and Launch Options for 2026"
description: "The Counter-Strike 2 settings that raise FPS and 1% lows without hurting visibility, plus the launch options that still matter and the ones that never did."
url: https://frozentweaks.com/guides/cs2-fps-boost
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Game Guides"
game: "Counter-Strike 2"
source: Frozen Tweaks (https://frozentweaks.com)
---

# CS2 FPS Boost: Best Settings and Launch Options for 2026

**Short answer:** For maximum CS2 FPS, set Shader Detail, Model/Texture Detail and Particle Detail to Low, Ambient Occlusion to Disabled, Global Shadow Quality to High, High Dynamic Range to Performance and NVIDIA Reflex to Enabled + Boost, then use the launch options -novid -nojoy -fullscreen. Keep Boost Player Contrast on and shadows above Low - both cost a little performance and materially improve your ability to see enemies.

## At a glance

| | |
| --- | --- |
| Engine | Source 2 |
| Primary bottleneck | CPU (single-thread heavy) |
| Target frame rate | At or above your refresh rate, capped for VRR |
| Biggest single win | Shader Detail and Particle Detail to Low |
| Do not lower | Shadows, Boost Player Contrast |

## Quick setup

1. **Set the launch options** - Right-click Counter-Strike 2 in Steam, choose Properties, and paste -novid -nojoy -fullscreen into Launch Options. Ignore the longer strings shared in CS:GO-era guides; the rest are Source 1 leftovers that do nothing here.
2. **Drop Shader Detail and Particle Detail to Low** - Advanced Video settings. These two are the largest wins in the menu and neither costs you competitive information - particle detail in particular pays out during smokes and molotovs, where frame rate normally collapses.
3. **Leave the shadows alone** - Keep Global Shadow Quality at High and Dynamic Shadows on All. CS2 renders enemy shadows that reveal players around corners, so lowering these trades information for a small number of frames.
4. **Enable Reflex and cap your frame rate** - Set NVIDIA Reflex Low Latency to Enabled + Boost, and set fps_max about three below your refresh rate if you use G-Sync or FreeSync.
5. **Free up CPU time** - Enable XMP or EXPO in BIOS, set the Windows power mode to Best performance, and close hardware-accelerated browser tabs. CS2 is CPU-bound, so this is where most of the remaining gain lives.

## Key takeaways

- CS2 is heavily CPU-bound at competitive frame rates. If your GPU sits at 60% usage, that is normal and lowering graphics settings will not help much.
- Shader Detail and Particle Detail are the two settings with the worst cost-to-benefit ratio - drop both to Low first.
- Do not lower Global Shadow Quality below High. Shadows in CS2 render enemy silhouettes around corners and are a genuine information source.
- Boost Player Contrast costs a small amount of performance and is worth every frame it takes.
- Most CS:GO-era launch options no longer exist in Source 2. -threads, -high and -tickrate do nothing or actively hurt.

## Why CS2 does not respond to graphics settings the way you expect

CS2 runs on Source 2 and, at the frame rates competitive players target, it is almost always limited by your CPU rather than your GPU. This surprises people who open Task Manager, see the GPU at 55% and assume something is broken. It is not - the CPU is finishing its work on each frame before the GPU has anything left to do.

The practical consequence is that dropping from 1440p to 1080p, or turning texture quality down, often changes almost nothing. What does help is reducing the per-frame CPU work: particle detail, shader complexity, and the number of background processes competing for cores. That is why the system-level section further down matters more in CS2 than in most other games.

> **Check before you tune:** Open the console with the tilde key and run cl_showfps 1. If your FPS barely moves between Low and High presets, you are CPU-bound and should focus on the launch options and Windows sections rather than the graphics menu.

## The CS2 video settings, one by one

**Advanced Video settings for maximum FPS with full visibility**
| Setting | Recommended | Why |
| --- | --- | --- |
| Boost Player Contrast | Enabled | Brightens player models relative to the environment. Costs a small amount of GPU time and is the most valuable visibility setting in the game. Never turn this off for frames. |
| Wait for Vertical Sync | Disabled | V-Sync adds a full frame of latency. Use a frame cap plus G-Sync or FreeSync instead. |
| Multisampling Anti-Aliasing Mode | 2x MSAA (or CMAA2 on weaker GPUs) | 8x MSAA is very expensive for a marginal edge-quality gain. Going to None makes distant player models shimmer and harder to track. |
| Global Shadow Quality | High | Deliberately not Low. CS2 renders enemy shadows that reveal players around corners and above you. Lowering this removes information, and the frame cost is modest. |
| Dynamic Shadows | All | Same reasoning - shadows cast by other players are competitively useful. |
| Model / Texture Detail | Low | Meaningful CPU and memory saving with essentially no impact on your ability to identify a player at range. |
| Texture Filtering Mode | Bilinear or Anisotropic 2x | Anisotropic 16x costs frames for surface detail on floors you are not looking at. |
| Shader Detail | Low | One of the two largest wins in the menu. Reduces per-pixel shader complexity across the whole scene. |
| Particle Detail | Low | The other large win, and it pays out exactly when you need it - smokes, molotovs and flashbangs are where frame rate collapses. |
| Ambient Occlusion | Disabled | Subtle contact shadowing that costs real GPU time and adds no competitive information. |
| High Dynamic Range | Performance | The Quality setting costs frames for tone-mapping fidelity that does not help you win rounds. |
| FidelityFX Super Resolution | Disabled, or Ultra Quality if GPU-bound | Because CS2 is usually CPU-bound, upscaling often returns nothing. If your GPU is genuinely at 99%, Ultra Quality is the only preset that does not soften player models unacceptably. |
| NVIDIA Reflex Low Latency | Enabled + Boost | Shortens the render queue. Costs a small number of frames and returns a larger reduction in click-to-photon latency, which is the thing you actually feel. |

> **The rule for competitive shooters:** Lower everything that draws pixels. Keep everything that draws information. Shadows, player contrast and draw distance are information. Particles, shaders and ambient occlusion are pixels.

## Launch options: what still works in Source 2

Right-click Counter-Strike 2 in Steam, choose Properties, and paste into the Launch Options box. Most of the long strings shared in CS:GO-era guides are inherited from a different engine and either do nothing or hurt.

```text
-novid -nojoy -fullscreen
```

**What each one does, and what to avoid**
| Setting | Recommended | Why |
| --- | --- | --- |
| -novid | Keep | Skips the intro video. Saves a few seconds per launch, no downside. |
| -nojoy | Keep | Skips controller subsystem initialisation. Small memory saving, faster startup. |
| -fullscreen | Keep | Forces exclusive fullscreen, which is the lowest-latency presentation path. Windowed and borderless both add a compositor step. |
| -high | Avoid | Raises process priority above other system threads. On modern schedulers this causes audio and input stutter more often than it helps. |
| -threads N | Avoid | A Source 1 option. In Source 2 it either does nothing or interferes with the engine's own thread allocation. |
| -tickrate 128 | Does nothing | CS2 uses sub-tick timing. Tickrate launch options are meaningless in this engine. |
| -d3d9ex / -softparticlesdefaultoff | Does nothing | Source 1 leftovers. CS2 does not use DirectX 9 and does not recognise these. |

## Console commands worth setting

Enable the console in Settings > Game > Enable Developer Console, then open it with the tilde key.

```text
// Uncapped, or set to 3 below your refresh rate if you use G-Sync/FreeSync
fps_max 0

// Maximum bandwidth - use this unless you are on a very constrained connection
rate 786432

// Lightweight on-screen performance readout
cl_showfps 1

// Full network graph while diagnosing stutter (0 to turn off)
cq_netgraph 1
```

On a variable-refresh display, uncapped frame rate is not what you want. Set **fps_max** to roughly three below your refresh rate - 237 on a 240 Hz panel, 141 on 144 Hz - so you stay inside the VRR window and avoid the latency spike that occurs when frames queue at the refresh ceiling.

## System changes that matter more in CS2 than elsewhere

Because CS2 is CPU-bound, anything competing for CPU time shows up directly in your 1% lows. This is where most of the remaining gain lives.

- Close browser windows and Discord streams before playing. Hardware-accelerated browser tabs are the most common cause of unexplained CS2 frame drops.
- Disable the Steam overlay for CS2 specifically if you do not use it - Properties > General > Enable the Steam Overlay.
- Enable XMP or EXPO in BIOS. Memory bandwidth and latency matter more in CS2 than in almost any other competitive title, and a machine running JEDEC fallback speeds gives up a large amount of headroom.
- Set the Windows power mode to Best performance so cores are not parked between rounds.
- Prune startup applications. RGB software, capture utilities and vendor updaters all take CPU slices during a round.
- Keep the game on an SSD. Map load and round transitions are the only disk-heavy moments, but they are where hitching appears.

**The CS2 profile does this automatically** - Frozen Tweaks ships a CS2 profile in the free tier that applies the Windows, power and network side of this list and rolls it back on demand. [Get the free CS2 profile](https://frozentweaks.com/purchase)

## Frequently asked questions

### Why is my GPU usage low in CS2?

Because CS2 is CPU-bound at high frame rates. The CPU finishes preparing each frame before the GPU is saturated, so GPU utilisation sits well below 100% while your frame rate is limited by single-thread CPU performance. This is normal and expected. It also means lowering resolution or texture quality will do very little - focus on particle and shader detail, background CPU load, and memory speed instead.

### Should I lower shadows in CS2 for more FPS?

No. Keep Global Shadow Quality at High and Dynamic Shadows on All. CS2 renders shadows cast by other players, which reveals enemies around corners and on levels above you. The frames you gain by lowering shadows are worth less than the information you lose. Lower Shader Detail and Particle Detail instead - they cost more and tell you nothing.

### What are the best CS2 launch options in 2026?

-novid -nojoy -fullscreen. That is the complete useful set. Most longer strings circulating online are inherited from CS:GO and Source 1: -threads, -d3d9ex and -softparticlesdefaultoff do nothing in Source 2, -tickrate is meaningless because CS2 uses sub-tick timing, and -high causes audio and input stutter more often than it helps.

### Does FSR help FPS in CS2?

Usually not, because the bottleneck is your CPU rather than your GPU, and upscaling only reduces GPU work. Check GPU utilisation first: if it is genuinely pinned at 98-99%, FidelityFX Super Resolution at Ultra Quality will help. Below that, it costs you image clarity on player models for no frame-rate return.

### What FPS should I cap CS2 at?

If you have a G-Sync or FreeSync monitor, set fps_max to about three below your refresh rate (237 on 240 Hz, 141 on 144 Hz) so you stay inside the variable-refresh window. On a fixed-refresh monitor without VRR, leaving fps_max at 0 gives the lowest input latency at the cost of tearing. A stable capped frame rate consistently feels better than a higher but fluctuating one.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/cs2-fps-boost

---

---
title: "Valorant FPS Boost: Best Settings on Unreal Engine 5"
description: "Valorant moved to Unreal Engine 5 in 2025. Here are the settings that raise FPS and cut input delay on the current build, plus what Vanguard means for tweaking."
url: https://frozentweaks.com/guides/valorant-fps-boost
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Game Guides"
game: "Valorant"
source: Frozen Tweaks (https://frozentweaks.com)
---

# Valorant FPS Boost: Best Settings on Unreal Engine 5

**Short answer:** For maximum Valorant FPS, set Material, Texture, Detail and UI Quality to Low, turn off Vignette, Bloom, Distortion, Cast Shadows and V-Sync, set Anti-Aliasing to MSAA 2x and Anisotropic Filtering to 1x, keep Multithreaded Rendering on, and enable NVIDIA Reflex Low Latency at On + Boost. Valorant is CPU-bound on most systems, so low GPU utilisation is normal rather than a fault.

## At a glance

| | |
| --- | --- |
| Engine | Unreal Engine 5.3 (since patch 11.02, July 2025) |
| Anti-cheat | Riot Vanguard (kernel-level, loads at boot) |
| Primary bottleneck | CPU |
| Biggest single win | Cast Shadows off |
| Safe to tweak? | Yes - settings-level changes only, never file or process modification |

## Quick setup

1. **Turn Cast Shadows off** - The largest single saving in the graphics menu. Valorant does not project other players' shadows for you to read, so unlike CS2 this costs you nothing.
2. **Set the four quality sliders to Low** - Material Quality, Texture Quality, Detail Quality and UI Quality. Leave Multithreaded Rendering on.
3. **Disable the post-process effects** - Vignette, Bloom, Distortion and V-Sync all off. Set Anti-Aliasing to MSAA 2x and Anisotropic Filtering to 1x.
4. **Enable Reflex and a frame cap** - NVIDIA Reflex Low Latency to On + Boost, then turn on Limit FPS Always and set the cap about three below your refresh rate.
5. **Fix the CPU side** - Enable XMP or EXPO, set the Windows power mode to Best performance, and close hardware-accelerated browser tabs. Valorant is CPU-bound, so low GPU usage is normal and these changes matter more than any slider.

## Key takeaways

- Valorant migrated from Unreal Engine 4.27 to Unreal Engine 5.3 in patch 11.02 (July 2025). Reported gains were small on high-end systems and around 5-10% on mid and low-end machines.
- Riot Vanguard is a kernel-level anti-cheat that loads at boot. Never use tools that inject into the game process or modify game files.
- Valorant is CPU-bound on almost all hardware. Low GPU usage is expected, and lowering resolution rarely helps much.
- Cast Shadows off is the largest single graphics saving and, unusually for a shooter, does not cost you meaningful information in this game.
- Reflex On + Boost plus a frame cap below your refresh rate does more for how the game feels than any further graphics reduction.

## What the Unreal Engine 5 move changed

Valorant shipped on Unreal Engine 4.27 for its first five years. Patch 11.02, released at the end of July 2025, moved it to Unreal Engine 5.3. Riot's stated goals were maintainability and faster map loading rather than raw frame rate, and the measured results match that framing.

- High-end desktops saw modest average gains - in the region of a hundred frames on systems already running many hundreds, which is a small relative change.
- Mid-range and low-end laptops reported roughly 5-10% improvement, concentrated in low-complexity scenes.
- Map initialisation got noticeably faster, shaving seconds off load times.
- Crucially, Riot avoided the performance regression that usually accompanies a UE4 to UE5 migration. Nanite and Lumen are not used, which is why Valorant did not inherit the frame-time problems that characterise most UE5 titles.

> **If your FPS dropped after an update:** Unreal Engine 5 rebuilds its shader cache after game and driver updates. Sit in the practice range for a few minutes after a patch before concluding something is wrong - the first session after an update is not representative.

## The full Valorant video settings list

**General**
| Setting | Recommended | Why |
| --- | --- | --- |
| Display Mode | Fullscreen | Exclusive fullscreen is the lowest-latency presentation path. Windowed Fullscreen adds a compositor step unless Windows windowed-game optimizations are enabled. |
| Resolution | Native, or a stretched resolution if you prefer it | Valorant is CPU-bound, so lowering resolution returns much less than it would in a GPU-bound game. Change it for the aspect ratio, not the frames. |
| Limit FPS Always | On | Pair with a Max FPS about three below your refresh rate on a VRR display. A stable cap gives more consistent frame times than an uncapped fluctuating rate. |
| NVIDIA Reflex Low Latency | On + Boost | The single most valuable latency setting in the game. Shortens the render queue; Boost additionally keeps GPU clocks up during CPU-bound moments, which is most of the time in Valorant. |

**Graphics Quality**
| Setting | Recommended | Why |
| --- | --- | --- |
| Multithreaded Rendering | On | Distributes rendering work across cores. Leave this on unless you have a genuinely single-core-limited machine. |
| Material Quality | Low | Shader complexity across every surface. Large saving, minimal visual difference at the distances that matter. |
| Texture Quality | Low | In most games textures are near-free if they fit in VRAM. In Valorant the assets are small enough that Low costs you nothing visually while reducing streaming work. |
| Detail Quality | Low | Controls world geometry density. Lowering it also removes small clutter objects that can obscure a peek. |
| UI Quality | Low | Renders the HUD at lower fidelity. Costs nothing you will notice and is free frames. |
| Vignette | Off | Darkens screen edges. Costs a little GPU time and darkens exactly the peripheral area where you want to spot movement. |
| V-Sync | Off | Adds a full frame of latency. Use the in-game frame cap with G-Sync or FreeSync instead. |
| Anti-Aliasing | MSAA 2x | MSAA 4x is roughly twice the cost for a small quality gain. None causes distant player edges to shimmer, which makes tracking harder. |
| Anisotropic Filtering | 1x | Sharpens textures viewed at oblique angles - floors and walls. No competitive value, measurable cost. |
| Improve Clarity | Off | A post-process sharpening pass. Costs frames; whether it helps you see is subjective, so test it rather than assuming. |
| Experimental Sharpening | Off | As above, and it is explicitly experimental. |
| Bloom | Off | Light bleed around bright surfaces. Pure cost, and it washes out contrast near light sources. |
| Distortion | Off | Heat-haze and ability distortion effects. Turning it off both saves frames and makes several abilities easier to see through. |
| Cast Shadows | Off | The largest single saving in the menu. Unlike CS2, Valorant does not render enemy shadows to other players, so this costs you no information. |

> **The one setting people get backwards:** Cast Shadows off is correct in Valorant and wrong in CS2. Valorant does not project other players' shadows for you to read; CS2 does. Copying a settings list across games without knowing this is how people end up slower.

## What Vanguard means for optimizing Valorant

Riot Vanguard is a kernel-mode anti-cheat that loads at boot rather than at game launch. It has the broadest system visibility of any anti-cheat in a mainstream competitive game, and that has direct consequences for how you should approach performance tuning.

**Safe and unsafe with Vanguard running**
| Setting | Recommended | Why |
| --- | --- | --- |
| Windows, power and driver settings | Safe | These are configuration changes outside the game process. Vanguard does not object to your power plan. |
| In-game settings and config files Riot exposes | Safe | Anything you can change through the game's own interface is by definition permitted. |
| GPU control panel overrides | Safe | NVIDIA Control Panel and AMD Adrenalin settings are driver-level and outside the protected process. |
| DLL injection or overlay hooks | Unsafe | Vanguard blocks or flags processes that attempt to inject. This includes some legitimate overlay and capture software. |
| Modifying game files or configs Riot does not expose | Unsafe | File integrity is checked. Editing Unreal .ini files to unlock hidden settings is exactly the pattern anti-cheat looks for. |
| Unsigned or test-signed drivers | Unsafe | Vanguard refuses to run alongside several classes of unsigned driver, including some older overclocking and fan-control utilities. |

The practical rule is simple: change your operating system and your driver, never the game. Everything recommended in this guide falls on the safe side of that line, and so does everything Frozen Tweaks applies.

## System-level changes for Valorant specifically

- Enable XMP or EXPO. Valorant's CPU-bound profile makes it unusually sensitive to memory latency, and the difference between JEDEC fallback speeds and a rated profile is often larger here than in GPU-heavy games.
- Set the Windows power mode to Best performance. Core parking between rounds produces exactly the kind of first-shot hitch that costs duels.
- Turn off Xbox Game Bar background recording. It reserves GPU encoder resources for a feature almost nobody uses.
- Close hardware-accelerated browser tabs. This is the most common cause of unexplained Valorant frame drops on otherwise capable machines.
- Cap your frame rate below your refresh rate rather than running uncapped. Valorant can produce very high frame rates that push the GPU into a power-limited oscillation, which reads as micro-stutter.
- If you use a 1000 Hz or higher polling rate mouse, verify it is not saturating a shared USB controller. Move it to a dedicated rear port off the chipset.

**Valorant profile included free** - The free Frozen Tweaks tier includes a Valorant profile covering the Windows, power and network side of this list, plus the FrostRes tool if you want a stretched resolution. [Download for Valorant](https://frozentweaks.com/purchase)

## Frequently asked questions

### Why is my FPS low in Valorant even with a good GPU?

Valorant is CPU-bound on nearly all hardware, so a powerful GPU sitting at 40-60% utilisation is normal rather than a fault. Frame rate is limited by single-thread CPU performance, memory latency and background CPU load. Enable XMP or EXPO in BIOS, set the Windows power mode to Best performance, close hardware-accelerated browser tabs, and prune startup applications - those will do more than any graphics setting.

### Did Unreal Engine 5 make Valorant run better or worse?

Slightly better, and notably it did not make it worse. Patch 11.02 in July 2025 moved Valorant from Unreal Engine 4.27 to Unreal Engine 5.3. High-end systems saw small relative gains; mid and low-end machines reported roughly 5-10%. Map load times improved. Riot did not adopt Nanite or Lumen, which is why Valorant avoided the frame-time regressions common to UE5 titles.

### Should Cast Shadows be on or off in Valorant?

Off. It is the largest single performance saving in the graphics menu, and unlike Counter-Strike 2, Valorant does not render other players' shadows for you to read around corners. You lose no competitive information by disabling it. This is the main reason a CS2 settings list should not be copied directly into Valorant.

### Is it safe to use optimization software with Riot Vanguard?

Settings-level tools are safe; anything that touches the game is not. Vanguard is a kernel-level anti-cheat that loads at boot and has broad system visibility, but it is concerned with process injection, game file integrity and unsigned drivers. Changing Windows settings, power plans and GPU driver options happens entirely outside the protected process. Avoid anything that injects overlays, edits Unreal .ini files, or requires an unsigned driver.

### What FPS cap should I use in Valorant?

Turn on Limit FPS Always and set the cap about three frames below your monitor's refresh rate if you use G-Sync or FreeSync - 237 on a 240 Hz panel, 141 on 144 Hz. This keeps you inside the variable-refresh window and avoids the latency penalty of hitting the refresh ceiling. On a fixed-refresh monitor, a cap still helps by preventing the GPU power oscillation that produces micro-stutter at very high frame rates.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/valorant-fps-boost

---

---
title: "Fortnite FPS Boost: Performance Mode and Best Settings"
description: "How to get the highest stable FPS in Fortnite - when Performance Mode is the right call, which DirectX 12 settings to keep, and what to leave alone for visibility."
url: https://frozentweaks.com/guides/fortnite-fps-boost
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Game Guides"
game: "Fortnite"
source: Frozen Tweaks (https://frozentweaks.com)
---

# Fortnite FPS Boost: Performance Mode and Best Settings

**Short answer:** The fastest way to boost Fortnite FPS is to switch Rendering Mode to Performance (Alpha), which replaces the high-fidelity renderer with a lightweight DirectX 11 path and commonly doubles frame rate on mid and low-end systems. If you stay on DirectX 12, set Shadows off, Effects and Post Processing low, Textures low, keep View Distance at Epic for visibility, and enable NVIDIA Reflex at On + Boost.

## At a glance

| | |
| --- | --- |
| Engine | Unreal Engine 5 |
| Renderers | Performance (Alpha), DirectX 11, DirectX 12 |
| Biggest single win | Performance Mode on low/mid hardware |
| Never lower | View Distance |
| Anti-cheat | Easy Anti-Cheat - settings-level tuning only |

## Quick setup

1. **Pick your renderer first** - Performance (Alpha) if your frame rate is below your refresh rate - it is a separate lightweight DirectX 11 path and commonly doubles frame rate. DirectX 12 if you comfortably exceed your refresh rate already.
2. **Keep View Distance at Epic** - It determines whether distant players and structures render at all, and it is a CPU cost rather than a GPU one. This is the setting never to lower.
3. **Turn off the expensive lighting** - On the DirectX 12 path: Shadows off, Lumen Global Illumination and Reflections off, Nanite off, Hardware Ray Tracing off, Motion Blur off.
4. **Set upscaling to Quality** - Anti-Aliasing & Super Resolution: DLSS on NVIDIA RTX, FSR on AMD, XeSS on Intel Arc, or TSR as the vendor-neutral fallback. Leave 3D Resolution at 100%.
5. **Enable Reflex and a frame limit** - NVIDIA Reflex Low Latency to On + Boost, Frame Rate Limit about three below your refresh rate, and Fullscreen window mode.
6. **Wait out shader compilation** - After a game patch or driver update, play a few minutes in Creative before judging performance. Unreal Engine 5 rebuilds its shader cache and the first session always hitches.

## Key takeaways

- Performance Mode is not a preset - it is a different renderer. On low and mid-range hardware it is the single largest FPS change available in the game.
- Keep View Distance at Epic regardless of your other settings. It is a CPU cost and it determines whether distant players render at all.
- Shadows off is the biggest saving on the DirectX 12 path, and Fortnite does not render enemy shadows for you to read.
- Editing and building performance depends on frame-time consistency, not average FPS. A capped, stable rate beats a higher unstable one.
- Unreal Engine 5 shader compilation causes heavy stutter for the first few minutes after a patch or driver update. Wait it out before diagnosing.

## Choose your renderer before you touch anything else

Fortnite offers three rendering modes, and the choice matters far more than any individual quality slider. This is the first decision to make, and most guides bury it three sections down.

**The three rendering modes**
| Setting | Recommended | Why |
| --- | --- | --- |
| Performance (Alpha) | Low and mid-range systems, and anyone chasing maximum frame rate | A separate lightweight DirectX 11 renderer that strips high-fidelity lighting and materials. Commonly doubles frame rate on modest hardware and dramatically reduces CPU load. Visually flat, but every player model remains clearly readable. |
| DirectX 11 | Older GPUs that dislike the DX12 path | The middle option. Better looking than Performance Mode, lower overhead than DirectX 12, and more stable on pre-2018 hardware. |
| DirectX 12 | Modern GPUs, and required for Nanite, Lumen and ray tracing | The best-looking path and the only one with the full Unreal Engine 5 feature set. Higher CPU overhead and the source of most shader compilation stutter. |

> **The honest recommendation:** If you are playing competitively and your frame rate is below your refresh rate, use Performance Mode. It looks worse and it wins more fights. If you comfortably exceed your refresh rate on DirectX 12, stay there - the visual difference is large and you are not gaining anything from the switch.

## Video settings on the DirectX 12 path

**Graphics settings for competitive play**
| Setting | Recommended | Why |
| --- | --- | --- |
| Window Mode | Fullscreen | Exclusive fullscreen is the lowest-latency path. Enable Windows windowed-game optimizations if you must play borderless. |
| Frame Rate Limit | About 3 below your refresh rate | Keeps you inside the G-Sync or FreeSync window. Uncapped frame rates in the menus can push the GPU into thermal and power oscillation. |
| 3D Resolution | 100% | Lowering this is a blunt internal-resolution cut that makes distant players harder to identify. Use the upscaling setting instead. |
| View Distance | Epic | The most important setting in the menu. It is a CPU cost, not a GPU one, and it determines whether players and structures at range render at all. Never lower this. |
| Shadows | Off | The largest GPU saving available. Fortnite does not render enemy shadows for you to read, so unlike CS2 this costs you nothing competitively. |
| Anti-Aliasing & Super Resolution | DLSS / FSR / XeSS at Quality, or TSR Medium | Match the technology to your GPU vendor. Quality mode returns a large share of frames with minimal softening. Never enable two upscalers at once. |
| Textures | Low or Medium | Keep it low enough to stay inside VRAM. Exceeding VRAM produces hitching rather than a lower average, which is far worse. |
| Effects | Low | Explosions, smoke and shield effects. This is where frame rate collapses in end-game circles, which is exactly when you need it. |
| Post Processing | Low | Bundles bloom, depth of field and colour grading. Costs frames and reduces target contrast. |
| Nanite Virtualized Geometry | Off | Detailed geometry streaming. Significant GPU cost for detail you will not notice in a fight. |
| Lumen Global Illumination / Reflections | Off | Real-time global illumination is the most expensive feature in any Unreal Engine 5 title. Off is worth 20-40% on its own on most cards. |
| Hardware Ray Tracing | Off | Pure cost in a competitive mode. |
| Motion Blur | Off | Smears the fast camera movement you need to track during builds and edits. |
| NVIDIA Reflex Low Latency | On + Boost | Shortens the render queue. The clearest improvement to how building and editing feel, separate from frame rate. |
| Show FPS | On | Not a performance setting - a diagnostic one. You cannot tune what you are not measuring. |

## Why building and editing feel bad even at high FPS

Fortnite players regularly report that builds feel delayed on a machine hitting 200 FPS. That is an input-latency problem, and frame rate alone does not describe it. The chain from your click to a build appearing has several stages, and any one of them can dominate.

- Reflex off, or set to On without Boost. Boost specifically helps in CPU-bound moments, and building sequences are heavily CPU-bound.
- V-Sync enabled anywhere - in game, in the driver, or through a frame limiter that queues frames. This alone adds a full frame of delay.
- No frame cap on a variable-refresh display. Hitting the refresh ceiling queues frames and adds latency at exactly the wrong time.
- Running in borderless windowed without the Windows windowed-game optimization enabled.
- Server-side network delay, which no client setting fixes. Check your ping and packet loss in the net debug stats before blaming your PC.

> **Test it properly:** Go to Creative, place a build, and record with a high-frame-rate camera or use your GPU vendor's latency overlay. Perceived input delay is notoriously unreliable - people frequently attribute a bad night to their settings when nothing changed.

## Shader stutter after every update

Unreal Engine 5 compiles shaders on demand and caches them. After a Fortnite patch, a GPU driver update, or a Windows feature update, that cache is invalidated and the first session rebuilds it. The symptom is severe hitching for the first several minutes that then disappears entirely.

This is not a problem with your settings and no tweak fixes it. Load into a Creative island or the lobby for a few minutes after any update rather than diagnosing a fault that resolves itself. If the hitching persists beyond a full session, then look at VRAM headroom, storage speed and background processes.

**Fortnite profile in the free tier** - Frozen Tweaks includes a Fortnite profile free, covering the Windows, power and latency configuration around the settings above. [Download for Fortnite](https://frozentweaks.com/purchase)

## Frequently asked questions

### Does Performance Mode really increase FPS in Fortnite?

Yes, substantially, because it is a different renderer rather than a quality preset. Performance (Alpha) uses a lightweight DirectX 11 path that removes high-fidelity lighting and materials entirely, and it commonly doubles frame rate on low and mid-range systems while cutting CPU load. The trade is that the game looks visibly flat. If your frame rate is already comfortably above your refresh rate on DirectX 12, there is no reason to switch.

### Should I lower View Distance in Fortnite for more FPS?

No. View Distance determines whether distant players and structures render at all, and it is a CPU cost rather than a GPU one, so lowering it often returns very little frame rate while directly damaging your ability to spot enemies. Keep it at Epic and lower Shadows, Effects and Post Processing instead.

### Why does Fortnite stutter after an update?

Unreal Engine 5 rebuilds its shader cache after every game patch, GPU driver update or Windows feature update. The first session compiles shaders on demand, which produces heavy hitching that then disappears completely. Load into Creative or sit in the lobby for a few minutes after an update. If the stutter survives past a full session, look at VRAM headroom, drive speed and background processes instead.

### What is the best upscaling setting in Fortnite?

Match it to your GPU: DLSS on NVIDIA RTX, FSR on AMD, XeSS on Intel Arc, and TSR as the vendor-neutral fallback. Use Quality mode - it returns most of the available frames with the least softening of distant player models. Never enable two upscalers simultaneously, and do not lower 3D Resolution as well; upscaling already reduces the internal render resolution.

### Why does building feel delayed when my FPS is high?

That is input latency, which is a separate measurement from frame rate. The usual causes are NVIDIA Reflex being off or set to On without Boost, V-Sync enabled somewhere in the chain, no frame cap on a variable-refresh display, or running borderless windowed without the Windows windowed-game optimization. Building sequences are CPU-bound, which is exactly the case Reflex Boost is designed for.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/fortnite-fps-boost

---

---
title: "ARC Raiders FPS Boost: Fixing Unreal Engine 5 Stutter"
description: "ARC Raiders runs on Unreal Engine 5, which means shader stutter and expensive lighting. Here are the settings that fix both without making raiders harder to spot."
url: https://frozentweaks.com/guides/arc-raiders-fps-boost
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Game Guides"
game: "ARC Raiders"
source: Frozen Tweaks (https://frozentweaks.com)
---

# ARC Raiders FPS Boost: Fixing Unreal Engine 5 Stutter

**Short answer:** For the best ARC Raiders performance, start from the Medium preset, turn Motion Blur, Depth of Field and ray tracing off, set upscaling to Quality or Balanced, and enable NVIDIA Reflex or AMD Anti-Lag. That configuration typically holds 60-90 FPS on mid-range hardware. Most remaining hitching is Unreal Engine 5 shader compilation and clears after a few minutes of play following a patch.

## At a glance

| | |
| --- | --- |
| Engine | Unreal Engine 5 |
| Typical mid-range result | 60-90 FPS on Medium with RT off |
| Biggest single win | Upscaling at Quality |
| Most common complaint | Shader compilation stutter after patches |
| Anti-cheat | Settings-level tuning only - never modify game files |

## Quick setup

1. **Start from the Medium preset** - It is a better baseline than Low for this game, and the individual overrides below do most of the work anyway.
2. **Turn off ray tracing, motion blur and depth of field** - Ray tracing is the most expensive option in the menu; the other two cost frames and actively hide threats.
3. **Set global illumination to its lowest option** - Real-time GI is the defining cost of Unreal Engine 5, and reducing it is worth more than every texture and mesh setting combined.
4. **Enable upscaling at Quality** - DLSS on NVIDIA, FSR on AMD, XeSS on Intel Arc. Step down to Balanced only if you are still short of your target.
5. **Enable Reflex or Anti-Lag and cap your frames** - Turn V-Sync off and set a cap about three below your refresh rate so you stay inside the variable-refresh window.
6. **Play two matches before judging the result** - Unreal Engine 5 compiles shaders on demand after every patch. The first session is never representative, and a lot of settings get blamed for it.

## Key takeaways

- Medium preset with ray tracing, motion blur and depth of field disabled is the right starting point on almost any mid-range system.
- Upscaling at Quality or Balanced is the single largest free frame gain - match the technology to your GPU vendor.
- Most of the hitching people report is Unreal Engine 5 shader compilation, not a settings problem. It clears itself.
- Extraction shooters punish frame-time inconsistency harder than most genres because engagements are unscripted and audio cues matter.
- Keep textures as high as VRAM allows. Exceeding VRAM in a UE5 title produces severe hitching rather than a lower average.

## What running on Unreal Engine 5 means for you

ARC Raiders is built on Unreal Engine 5, and that single fact predicts most of its performance behaviour. UE5 titles share a characteristic profile: expensive real-time lighting, heavy reliance on upscaling to reach playable frame rates, and shader compilation stutter that appears after every patch and driver update.

This matters because the fixes are different from a Source or Frostbite game. Lowering texture quality will not help much. Turning off the lighting features and letting the shader cache build will.

> **Before you change anything:** Play two full matches after any patch or driver update. UE5 compiles shaders on demand and the first session is never representative. A large share of 'ARC Raiders is broken' reports are a shader cache that had not finished building.

## Recommended graphics settings

**Starting point: Medium preset, then override these**
| Setting | Recommended | Why |
| --- | --- | --- |
| Ray tracing | Off | The most expensive option in the menu by a wide margin. In an extraction shooter where you need consistent frame times during unplanned fights, it is pure cost. |
| Motion Blur | Off | Smears fast camera movement and costs GPU time. There is no version of this that helps you spot a raider. |
| Depth of Field | Off | Blurs the background, which is where threats appear. Costs frames and actively harms awareness. |
| Upscaling (DLSS / FSR / XeSS) | Quality, or Balanced if you need more | The largest free gain available. Quality is nearly indistinguishable in motion; Balanced is a reasonable step if you are still short of your target. |
| Global illumination / Lumen | Lowest available setting | Real-time GI is the defining cost of UE5. Reducing it is worth more than every texture and mesh setting combined. |
| Shadow quality | Medium or Low | Large GPU saving. Keep it at Medium rather than Off if you rely on shadows to read light direction indoors. |
| Textures | As high as VRAM allows | Nearly free on frame rate if they fit. If you see repeated sharp hitching, you have exceeded VRAM - drop one step. |
| Effects / post-processing | Low | Explosion and particle effects are where frame rate collapses during the fights that decide a raid. |
| NVIDIA Reflex / AMD Anti-Lag 2 | On (+ Boost on NVIDIA) | Shortens the render queue. Meaningful latency reduction for a negligible frame cost. |
| V-Sync | Off, with a frame cap below refresh | V-Sync adds a full frame of delay. A cap inside the VRR window gives you tear-free output without it. |

## Telling shader stutter apart from a real problem

Not all hitching is the same, and the fixes do not overlap. Match your symptom to the right row before you start changing settings.

**Stutter symptoms and their causes**
| Setting | Recommended | Why |
| --- | --- | --- |
| Hitching in the first few minutes after a patch, then fine | Shader compilation | Normal UE5 behaviour. No fix required - it resolves as the cache builds. Do not change settings based on this session. |
| Repeated sharp hitches in the same locations | Asset streaming from slow storage | Move the game to an NVMe SSD. This is the most common cause of location-specific hitching in UE5 titles. |
| Hitching that worsens the longer you play | VRAM or memory pressure | Drop textures one step and close background applications. Check VRAM usage in your GPU overlay. |
| Regular hitch every few seconds regardless of location | Background process or overlay | Disable overlays, RGB software and capture utilities one at a time. Browser tabs with hardware acceleration are a frequent culprit. |
| Frame rate fine, input feels heavy | Latency, not stutter | Enable Reflex or Anti-Lag, turn V-Sync off, and cap frames below your refresh rate. |

**ARC Raiders profile in Pro** - Frozen Tweaks ships an ARC Raiders profile that handles the Windows, storage and latency side of this list and re-applies it after driver updates. [See the game profiles](https://frozentweaks.com/purchase)

## Frequently asked questions

### Why does ARC Raiders stutter so much?

Most of it is Unreal Engine 5 shader compilation, which happens on demand after every game patch, GPU driver update and Windows feature update. It produces heavy hitching for the first few minutes of play and then disappears entirely. If hitching survives past a full session, the likely causes are asset streaming from a mechanical drive, VRAM exhaustion, or a background overlay - in that order.

### What are the best ARC Raiders settings for FPS?

Start from the Medium preset, then turn off ray tracing, motion blur and depth of field, set global illumination to its lowest option, and enable upscaling at Quality (DLSS on NVIDIA, FSR on AMD, XeSS on Intel Arc). Keep textures as high as your VRAM allows and enable NVIDIA Reflex or AMD Anti-Lag. On mid-range hardware that configuration typically holds 60-90 FPS.

### Should I use DLSS or FSR in ARC Raiders?

Use whichever matches your GPU - DLSS on NVIDIA RTX cards, FSR on AMD Radeon, XeSS on Intel Arc. Set it to Quality first and only step down to Balanced if you are still short of your target frame rate. Never enable two upscalers at the same time; they fight each other and produce worse image quality than either alone.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/arc-raiders-fps-boost

---

---
title: "Black Ops 7 FPS Boost: Settings, VRAM Scale and Worker Threads"
description: "Two Black Ops 7 settings cause most of the stuttering people blame on their hardware: VRAM Scale Target and renderer worker count. Here is how to set both correctly."
url: https://frozentweaks.com/guides/call-of-duty-black-ops-7-fps-boost
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Game Guides"
game: "Call of Duty: Black Ops 7"
source: Frozen Tweaks (https://frozentweaks.com)
---

# Black Ops 7 FPS Boost: Settings, VRAM Scale and Worker Threads

**Short answer:** The two highest-impact Black Ops 7 fixes are lowering VRAM Scale Target from its 90% default to 60-70%, which resolves most stuttering, and turning ray tracing and motion blur off. Beyond that, run the game from an SSD (it is a hard requirement), enable NVIDIA Reflex at On + Boost, and cap frames slightly below your refresh rate for consistent frame times.

## At a glance

| | |
| --- | --- |
| Storage requirement | SSD - officially required |
| Biggest single fix | VRAM Scale Target 60-70% |
| Turn off first | Ray tracing, motion blur |
| Anti-cheat | Kernel-level - settings and driver tuning only |
| Latency setting | NVIDIA Reflex On + Boost |

## Quick setup

1. **Set VRAM Scale Target to 65%** - The 90% default leaves no allocation headroom, so every unexpected allocation becomes a visible hitch. This single change resolves most Black Ops 7 stuttering reports.
2. **Turn ray tracing and both motion blur options off** - World motion blur and weapon motion blur are separate settings. Ray tracing is the largest frame cost in the game and buys you nothing in multiplayer.
3. **Let shader pre-loading finish** - Skipping it moves the compilation cost into your first matches, where it appears as hitching you will blame on something else.
4. **Confirm the game is on an SSD with free space** - An SSD is a hard requirement rather than a recommendation, and a nearly full drive slows down substantially. Keep 15-20% free.
5. **Configure latency and presentation** - Fullscreen Exclusive display mode, V-Sync off, NVIDIA Reflex at On + Boost, and a frame cap about three below your refresh rate.
6. **On Intel 12th to 14th gen, constrain renderer worker threads** - The renderer defaults to using efficiency cores as well as performance cores, which makes frames wait on the slower ones. Match the worker count to your P-core count and compare 1% lows rather than average FPS.

## Key takeaways

- The default VRAM Scale Target of 90% causes stuttering on most cards. Dropping it to 60-70% is the single most effective fix in the game.
- Black Ops 7 requires an SSD. Running it from a mechanical drive produces stutter that no settings change will fix.
- Ray tracing and motion blur cost a large share of your frame budget and provide zero competitive benefit.
- On Intel 12th to 14th generation CPUs, the renderer defaults to using efficiency cores as well as performance cores, which hurts frame-time consistency.
- Shader pre-loading is worth letting finish. Interrupting it guarantees hitching in your first matches.

## VRAM Scale Target: the setting that causes most Black Ops 7 stutter

Black Ops 7 ships with VRAM Scale Target set to around 90%, meaning the game will fill up to nine tenths of your graphics memory with streamed assets. On paper that maximises texture quality. In practice it leaves almost no headroom, and when the game needs to allocate anything unexpected - a new map area, a killcam, a UI transition - it has to evict assets first. You feel that as a hitch.

Lowering it to 60-70% costs you very little visible texture quality and eliminates a large share of the stuttering people otherwise attribute to their CPU or their drive. On cards with 8 GB of VRAM the difference is dramatic; even on 12 and 16 GB cards it flattens the frame-time graph.

> **Change this first:** If you take one thing from this guide, it is VRAM Scale Target. Set it to 65%, play two matches, and compare your 1% lows. This is a bigger improvement than every other setting on this page combined for most players.

## Graphics settings for competitive multiplayer

**What to change and why**
| Setting | Recommended | Why |
| --- | --- | --- |
| VRAM Scale Target | 60-70% | Leaves allocation headroom. The most effective anti-stutter setting in the game. |
| Ray tracing | Off | The largest single frame cost available. In multiplayer it buys you nothing at all. |
| Motion Blur (world and weapon) | Off | Costs frames and smears exactly the fast movement you need to track. Turn both variants off. |
| Display Mode | Fullscreen Exclusive | The lowest-latency presentation path. Borderless costs you a compositor step. |
| V-Sync | Off | Full frame of added latency. Use a frame cap with G-Sync or FreeSync instead. |
| Frame rate limit | About 3 below your refresh rate | Keeps you inside the VRR window and prevents the queue latency of hitting the ceiling. |
| NVIDIA Reflex Low Latency | On + Boost | Shortens the render queue. Boost helps specifically in the CPU-bound moments that dominate large multiplayer maps. |
| Upscaling (DLSS / FSR / XeSS) | Quality | Large gain, minimal softening. Match the technology to your GPU vendor and never run two at once. |
| Shadow quality | Low | Large GPU saving. Low shadows also make players in dark interiors easier to pick out. |
| Volumetric quality | Low | Smoke and atmospheric fog. Expensive, and it obscures targets. |
| Particle quality / resolution | Low | Where frame rate collapses during heavy firefights and killstreaks. |
| Texture resolution | One step below maximum | Combined with a lower VRAM Scale Target, this keeps you comfortably inside your memory budget. |
| Shader pre-loading | Let it complete | Interrupting it moves the compilation cost into your first matches, where it appears as hitching. |

## Renderer worker threads on Intel hybrid CPUs

On Intel 12th through 14th generation processors, the renderer defaults to spreading work across every logical thread the CPU reports - which includes the efficiency cores. Those cores are considerably slower than the performance cores, so any frame that waits on an E-core finishes late. The average frame rate looks acceptable and the frame-time graph is spiky.

Constraining the renderer's worker count so it maps to your performance cores generally produces flatter frame times on these CPUs. This is configured in the game's own options file, which the game itself writes and reads - it is not a modification of game code.

> **Be conservative with config edits:** Editing the settings file the game writes is normal use. Editing anything else in the game directory is not, and modern Call of Duty titles run kernel-level anti-cheat. If you are not confident which file is which, use the in-game menu and skip this section - the VRAM Scale Target change is worth more anyway.

- Identify your performance core count. Task Manager > Performance > CPU shows total cores; your CPU's product page lists the P-core and E-core split.
- Close the game completely before editing, or it will overwrite your change on exit.
- Set the renderer worker count to your P-core count, not your total logical thread count.
- Test across two matches and compare 1% lows, not average FPS - this change targets consistency, not peak.
- If it makes no difference, revert it. On AMD CPUs and on Intel chips without E-cores there is nothing here to fix.

## System requirements people ignore

- An SSD is a hard requirement, not a recommendation. Black Ops 7 streams assets aggressively and a mechanical drive produces stuttering that no graphics setting fixes.
- Keep at least 15-20% of the drive free. Full SSDs slow down substantially, and a Call of Duty install is large enough to push a small drive there.
- Enable XMP or EXPO. Large multiplayer maps with many entities are memory-bandwidth sensitive.
- Set the Windows power mode to Best performance so cores are not parked between rounds.
- Disable Xbox Game Bar background recording - it holds GPU encoder resources.
- Close hardware-accelerated browser tabs and Discord streams before playing.

**Call of Duty profile in Pro** - Frozen Tweaks includes a Call of Duty profile covering the Windows, power, storage and latency configuration around these settings. [See the game profiles](https://frozentweaks.com/purchase)

## Frequently asked questions

### How do I fix stuttering in Black Ops 7?

Lower VRAM Scale Target from its 90% default to 60-70% first - this resolves the majority of stuttering reports on its own by leaving the game allocation headroom in graphics memory. Then confirm the game is installed on an SSD, which Black Ops 7 requires, let shader pre-loading finish, and turn off ray tracing. On Intel 12th to 14th generation CPUs, constraining renderer worker threads to your performance cores also helps frame-time consistency.

### What VRAM Scale Target should I use in Black Ops 7?

Between 60% and 70%. The 90% default fills almost all of your graphics memory with streamed assets, leaving no room for the allocations the game makes during map transitions, killcams and UI changes - and each of those becomes a visible hitch. Lowering it costs very little visible texture quality and produces a substantially flatter frame-time graph, especially on 8 GB cards.

### Does Black Ops 7 need an SSD?

Yes, it is an official requirement rather than a recommendation. The game streams assets continuously and a mechanical hard drive cannot supply them fast enough, which produces stuttering that no graphics setting will fix. Moving the install to an SSD or NVMe drive is more effective than any amount of lowering settings.

### Is it safe to edit the Black Ops 7 config file?

Editing the options file the game itself writes and reads is normal use of the settings the game exposes. Editing anything else inside the game directory is not, and modern Call of Duty titles run kernel-level anti-cheat that checks file integrity. If you are unsure which file is which, stay in the in-game menu - the VRAM Scale Target change available there is worth more than the worker-thread tweak anyway.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/call-of-duty-black-ops-7-fps-boost

---

---
title: "Battlefield 6 FPS Boost: Best PC Settings for Large Maps"
description: "Battlefield 6 punishes weak CPUs and cheap effects settings. Here is the configuration that holds frame rate through 64-player destruction without blinding you."
url: https://frozentweaks.com/guides/battlefield-6-fps-boost
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Game Guides"
game: "Battlefield 6"
source: Frozen Tweaks (https://frozentweaks.com)
---

# Battlefield 6 FPS Boost: Best PC Settings for Large Maps

**Short answer:** For the best Battlefield 6 performance, turn ray tracing off (commonly worth around 25%), set lighting to Medium, Effects and Post-Process quality to Low, Ambient Occlusion to SSAO, textures to High on 8 GB cards or Ultra on 12 GB and above, and enable DLSS, FSR or XeSS at Quality with Reflex or Anti-Lag 2 on and a frame cap just under your refresh rate.

## At a glance

| | |
| --- | --- |
| Engine | Frostbite |
| Primary bottleneck | CPU at high player counts |
| Ray tracing cost | Roughly 25% of frame rate |
| Texture guidance | High on 8 GB VRAM, Ultra on 12 GB+ |
| Anti-cheat | Kernel-level - settings and driver tuning only |

## Quick setup

1. **Turn ray tracing off** - Commonly around 25% of your frame budget, and it contributes nothing in a 64-player match.
2. **Set Effects Quality and Post-Process Quality to Low** - These control the explosion, smoke and destruction load that stacks up in exactly the moments your frame rate collapses. The fastest win after ray tracing.
3. **Set Lighting to Medium and Ambient Occlusion to SSAO** - Medium lighting keeps enough shading definition to read building interiors, and SSAO is the cheap ambient occlusion variant.
4. **Size textures to your VRAM** - High on 8 GB cards, Ultra on 12 GB and above. Keep anisotropic filtering high - it is cheap and it keeps distant ground surfaces readable.
5. **Enable upscaling and Reflex, then cap frames** - DLSS, FSR or XeSS at Quality, Reflex or Anti-Lag 2 on, and a cap about three below your refresh rate. A stable 120 beats an unstable 160.
6. **Enable XMP or EXPO in BIOS** - Battlefield is CPU and memory-bandwidth heavy at high player counts, so this matters more here than in smaller-scale shooters.

## Key takeaways

- Ray tracing off is worth roughly 25% on average and costs nothing you need in a 64-player match.
- Effects Quality and Post-Process Quality are the fastest wins - they control the explosion, smoke and destruction load that stacks on large maps.
- Keep textures and anisotropic filtering high. They are close to free if they fit in VRAM and they help you identify players at range.
- A stable 120 FPS feels better than an unstable 160. Cap below your refresh rate and enable Reflex or Anti-Lag 2.
- Battlefield is CPU-heavy at high player counts. Memory speed and background process load matter more here than in smaller-scale shooters.

## Why Battlefield needs a different approach to a 5v5 shooter

Everything that makes Battlefield distinctive - large player counts, vehicles, destructible buildings, long sightlines - is CPU work. In a 5v5 tactical shooter your frame rate is broadly stable because the scene complexity is broadly stable. In a 64-player Battlefield match, your worst frame of the round happens when a building collapses next to a tank battle, and that is the frame that gets you killed.

So the goal here is not a high average. It is a floor. Every recommendation below is chosen for what it does to your 1% lows during the busiest thirty seconds of a match, not what it does to your number standing in an empty spawn.

## Recommended settings

**Graphics settings for competitive large-scale play**
| Setting | Recommended | Why |
| --- | --- | --- |
| Ray tracing | Off | Commonly around 25% of your frame budget. In a mode where visibility and frame-time floors decide fights, this is the easiest decision on the page. |
| Effects Quality | Low | Governs explosions, smoke and destruction particles - the exact load that stacks up in the moments your frame rate collapses. The fastest single win after ray tracing. |
| Post-Process Quality | Low | Bundles bloom, lens effects and colour grading. Costs frames and reduces contrast against smoke. |
| Lighting Quality | Medium | Medium keeps enough shading definition to read building interiors while dropping the most expensive lighting passes. |
| Ambient Occlusion | SSAO | The cheap variant. The high-quality and ray-traced options cost several times as much for a contact-shadow effect nobody notices in a firefight. |
| Texture Quality | High on 8 GB VRAM, Ultra on 12 GB+ | Nearly free if they fit in memory, and they help you resolve player silhouettes at distance. Exceeding VRAM causes hitching, so size this to your card. |
| Anisotropic Filtering | High (8x-16x) | Very cheap on modern GPUs and it keeps distant ground surfaces readable rather than a smear. |
| Volumetric fog / clouds | Low or Off | Expensive and it hides infantry. Both reasons point the same way. |
| Motion Blur | Off | Costs frames, smears vehicle and turn movement. |
| Upscaling (DLSS / FSR / XeSS) | Quality | Match the technology to your GPU vendor. Quality returns a large share of frames with minimal cost to distant target clarity. |
| NVIDIA Reflex / AMD Anti-Lag 2 | On (+ Boost on NVIDIA) | Shortens the render queue, which matters most in exactly the CPU-bound moments Battlefield generates. |
| Frame rate limit | About 3 below your refresh rate | A stable 120 genuinely feels better than an unstable 160. Cap it and stay inside the VRR window. |
| V-Sync | Off | Adds a full frame of latency. The cap plus G-Sync or FreeSync replaces it. |

## System-side work that matters here more than usual

Because Battlefield leans on the CPU harder than most shooters, the system-level items below shift your frame-time floor more than another notch of graphics reduction would.

- Enable XMP or EXPO in BIOS. High entity counts and destruction physics are memory-bandwidth hungry, and a machine running JEDEC fallback speeds gives up a lot here.
- Set the Windows power mode to Best performance. Core parking during quiet moments produces a stutter the instant the map gets busy again.
- Prune startup applications and close hardware-accelerated browser tabs. Every core slice they take comes directly out of your worst frame.
- Install on an SSD with free space. Streaming a large map from a full or mechanical drive shows up as traversal hitching.
- Check your monitor is running at its full refresh rate in Windows display settings - it silently reverts to 60 Hz after some driver installs.
- If you are on a laptop, keep it plugged in and set the manufacturer performance profile as well. Battery power caps clocks regardless of what Windows says.

**Battlefield profile in Pro** - Frozen Tweaks applies the Windows, power, memory and latency side of this list automatically and re-applies it after driver updates. [See the game profiles](https://frozentweaks.com/purchase)

## Frequently asked questions

### What are the best Battlefield 6 settings for FPS?

Turn ray tracing off, set Effects Quality and Post-Process Quality to Low, Lighting to Medium and Ambient Occlusion to SSAO, keep Texture Quality at High on 8 GB cards or Ultra on 12 GB and above, keep anisotropic filtering high, and enable DLSS, FSR or XeSS at Quality. Then turn on Reflex or Anti-Lag 2 and cap your frame rate about three below your refresh rate.

### Why does my FPS drop in big Battlefield 6 fights?

Because large-scale moments are CPU-bound: player counts, vehicles, destruction physics and particle effects all add CPU work simultaneously. Lowering resolution will not help. Lower Effects Quality and Post-Process Quality, enable XMP or EXPO in BIOS, set the Windows power mode to Best performance, and close background applications competing for cores. Those change your frame-time floor, which is what you actually feel.

### How much FPS does turning off ray tracing give in Battlefield 6?

Around 25% on average, though the figure varies with your GPU, resolution and which ray-traced features the game exposes. It is consistently the largest single setting change available, and in competitive multiplayer it costs you nothing functional - the visual difference is real but it does not help you win engagements.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/battlefield-6-fps-boost

---

---
title: "Marvel Rivals FPS Boost: Taming Lumen on Unreal Engine 5"
description: "One setting in Marvel Rivals costs more than everything else combined. Here is how to configure global illumination, upscaling and the rest for a stable frame rate."
url: https://frozentweaks.com/guides/marvel-rivals-fps-boost
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Game Guides"
game: "Marvel Rivals"
source: Frozen Tweaks (https://frozentweaks.com)
---

# Marvel Rivals FPS Boost: Taming Lumen on Unreal Engine 5

**Short answer:** The single biggest Marvel Rivals performance lever is Global Illumination: switching it from Lumen to SSGI at low quality commonly returns 30-60 FPS on a mid-range card. Follow it with Reflection Quality set to Screen Space, DLSS or FSR at Quality with sharpening around 70-80, model detail and post-processing low, and exclusive fullscreen rather than windowed.

## At a glance

| | |
| --- | --- |
| Engine | Unreal Engine 5 |
| Biggest single win | Global Illumination: Lumen to SSGI Low |
| Typical gain from that one change | 30-60 FPS on mid-range GPUs |
| Second win | Reflection Quality to Screen Space |
| Display mode | Exclusive fullscreen |

## Quick setup

1. **Change Global Illumination to SSGI at low quality** - Lumen is the single most expensive thing your GPU does in this game. This one change commonly returns 30-60 FPS on a mid-range card - do it before anything else, then re-measure.
2. **Set Reflection Quality to Screen Space** - The second-largest saving, for a difference you will not see during a teamfight.
3. **Enable Super Resolution at Quality** - DLSS on NVIDIA, FSR on AMD, XeSS on Intel Arc. Set Super Resolution Sharpening to about 70-80 to offset the softness.
4. **Drop Shadow Detail, Effects and Foliage to Low** - Ability effects stack heavily in teamfights, which is where frame rate matters most.
5. **Use exclusive fullscreen with V-Sync off** - Windowed fullscreen routes through the Windows compositor and adds a step. V-Sync trades a full frame of delay for tear-free output, which a shooter cannot afford.
6. **Only then consider lowering resolution** - It makes enemy heroes physically smaller on screen. If you need more frames, use the upscaler's Performance mode instead so the UI stays sharp.

## Key takeaways

- Global Illumination is the whole game. Lumen costs 30-60 FPS on mid-range hardware; SSGI at low quality gets almost all of it back.
- Reflection Quality set to Screen Space is the second-largest saving, for a difference you will not see during a teamfight.
- Use exclusive fullscreen, not windowed fullscreen. Exclusive mode takes the lowest-latency path to the display.
- Set upscaling sharpening around 70-80 to offset the softness DLSS and FSR introduce at Quality.
- Lower resolution last. In a hero shooter, smaller enemies on screen costs you more than the frames are worth.

## Global Illumination is the setting that matters

Marvel Rivals is built on Unreal Engine 5 and uses Lumen, the engine's real-time global illumination system, by default. Lumen produces genuinely beautiful indirect lighting, and it is the most expensive thing your GPU does in this game by a very wide margin - commonly 30 to 60 frames on a mid-range card.

Switching Global Illumination from Lumen to SSGI at low quality replaces it with a far cheaper screen-space approximation. The scene loses some depth in shadowed areas. Your frame rate does not lose a teamfight.

> **Do this before anything else:** Change Global Illumination first, then re-measure. On many systems it alone takes you from unplayable to comfortably above your refresh rate, and every other setting on this page becomes optional.

## The rest of the settings, in order of impact

**Marvel Rivals graphics settings**
| Setting | Recommended | Why |
| --- | --- | --- |
| Global Illumination | SSGI, Low quality | The single largest performance lever in the game. Typically worth 30-60 FPS on mid-range hardware. |
| Reflection Quality | Screen Space | The second-largest saving. Ray-traced and Lumen reflections are expensive and invisible during a fight. |
| Super Resolution (DLSS / FSR / XeSS) | Quality | The biggest free gain after lighting. Match the technology to your GPU vendor and never enable two at once. |
| Super Resolution Sharpening | 70-80 | Upscaling at Quality softens the image slightly. This offsets it without introducing the ringing artefacts you get near 100. |
| Display Mode | Fullscreen (exclusive) | Windowed fullscreen adds a compositor step. Exclusive takes the lowest-latency path to the monitor. |
| V-Sync | Off | Trades a full frame of latency to stop tearing. That is not a trade a shooter can afford - cap frames and use VRR instead. |
| Model Detail | Low or Medium | Hero models are large and distinctive; the detail reduction is barely visible in motion and the CPU saving is real. |
| Shadow Detail | Low | Large GPU saving with no competitive information loss in this game. |
| Effects / Post-Processing | Low | Ability effects stack heavily in teamfights. This is where frame rate collapses at the moment it matters most. |
| Foliage Quality | Low | Cheap win on the maps that have it, and less visual clutter to hide enemies. |
| Resolution | Native - change this last | Lowering resolution makes enemy heroes physically smaller on screen. Exhaust every setting above before touching it. |

## If you are on a low-end machine

The order still holds, it just becomes stricter. Work top to bottom and stop when you reach a stable frame rate above your refresh rate:

1. Global Illumination to SSGI Low. Non-negotiable, and it may be all you need.
2. Reflection Quality to Screen Space.
3. Super Resolution to Quality, then Balanced if required.
4. Shadow Detail, Effects and Foliage to Low.
5. Model Detail to Low.
6. Only now consider lowering resolution - and if you do, use the upscaler's Performance mode rather than dropping your display resolution, so the UI stays sharp.

**Automate the system side** - Frozen Tweaks handles the Windows, power and latency configuration that sits underneath these in-game settings, and re-applies it after driver updates. [Download Frozen Tweaks](https://frozentweaks.com/purchase)

## Frequently asked questions

### How do I fix low FPS in Marvel Rivals?

Change Global Illumination from Lumen to SSGI at low quality. It is the single most expensive setting in the game and switching it commonly returns 30-60 FPS on mid-range hardware. Then set Reflection Quality to Screen Space, enable DLSS, FSR or XeSS at Quality with sharpening around 70-80, and drop Shadow Detail, Effects and Foliage to Low. Lower your resolution only as a last resort.

### Should I use fullscreen or windowed in Marvel Rivals?

Exclusive fullscreen. It takes the lowest-latency path to your monitor, while windowed fullscreen routes through the Windows compositor and adds a step. If you need to alt-tab frequently and want to stay borderless, at least enable the windowed-game optimizations toggle in Windows display graphics settings, which recovers most of the difference.

### What sharpening value should I use with DLSS in Marvel Rivals?

Around 70-80. Upscaling at Quality reconstructs from a lower internal resolution and softens the image slightly; sharpening in that range restores perceived detail without the halo and ringing artefacts that appear as you approach 100. Adjust to taste - it is a preference setting, not a performance one.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/marvel-rivals-fps-boost

---

---
title: "Apex Legends FPS Boost: Settings and Launch Options"
description: "The Apex Legends settings that raise frame rate and 1% lows, the launch options that still work, and why Adaptive Resolution should be off."
url: https://frozentweaks.com/guides/apex-legends-fps-boost
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Game Guides"
game: "Apex Legends"
source: Frozen Tweaks (https://frozentweaks.com)
---

# Apex Legends FPS Boost: Settings and Launch Options

**Short answer:** For maximum Apex Legends FPS, set Adaptive Resolution FPS Target to 0, Model Detail and Effects Detail to Low, Volumetric Lighting and Dynamic Spot Shadows to Disabled, Ambient Occlusion Quality to Disabled, Impact Marks to Disabled, and Anti-aliasing to TSAA. Add the launch option +fps_max followed by a value about three below your refresh rate, and enable NVIDIA Reflex at On + Boost.

## At a glance

| | |
| --- | --- |
| Engine | Modified Source |
| Must be 0 | Adaptive Resolution FPS Target |
| Turn off first | Volumetric Lighting, Dynamic Spot Shadows |
| Texture budget | Match to your VRAM, never above |
| Anti-cheat | Kernel-level - settings and driver tuning only |

## Quick setup

1. **Set Adaptive Resolution FPS Target to 0** - Left on, it dynamically lowers your render resolution whenever performance dips - which means the image degrades at the exact moment a fight starts.
2. **Set Texture Streaming Budget to match your VRAM** - One step below your card's maximum. Setting it above your VRAM causes repeated hitching rather than a lower average, and this is the most commonly misconfigured setting in the game.
3. **Disable Volumetric Lighting and Dynamic Spot Shadows** - The two largest GPU costs in the menu, and the first also obscures targets in god-ray areas.
4. **Lower the cheap-to-lose settings** - Model Detail and Effects Detail to Low, Impact Marks Disabled, Ragdolls Low, Ambient Occlusion Quality Disabled, Sun Shadow Coverage and Detail Low.
5. **Add the launch options** - +fps_max set to about three below your refresh rate, plus -preload. Apex is noticeably less stable uncapped, and -preload reduces early-match hitching.
6. **Enable NVIDIA Reflex at On + Boost** - Apex is often CPU-bound during fights, which is exactly the case Boost is designed for.

## Key takeaways

- Adaptive Resolution FPS Target must be 0. Left on, it dynamically lowers your render resolution and makes distant enemies inconsistent to spot.
- Volumetric Lighting and Dynamic Spot Shadows are the two largest GPU costs in the menu.
- Texture Streaming Budget should match your VRAM. Setting it above your card causes hitching, not a lower average.
- Cap your frame rate. Apex is unstable at uncapped high frame rates and a cap improves frame-time consistency.
- Apex runs kernel-level anti-cheat. Stay on the settings and driver side of the line - never modify game files.

## Turn Adaptive Resolution off before anything else

Adaptive Resolution FPS Target is on by default on many installs, and it is the setting most responsible for Apex feeling inconsistent. It works by dynamically lowering your internal render resolution whenever frame rate drops below the target you set. The frame counter stays flat, which is the point - and the image quality swings underneath it.

In practice that means the moment a fight starts and your frame rate would otherwise dip, your resolution drops instead, and distant enemies become blurrier at exactly the wrong moment. Set it to 0 to disable it entirely, and take the honest frame rate.

## Video settings

**Apex Legends video settings for competitive play**
| Setting | Recommended | Why |
| --- | --- | --- |
| Adaptive Resolution FPS Target | 0 | Disables dynamic resolution scaling. Keeps your image quality stable during fights rather than degrading it exactly when it matters. |
| Display Mode | Full Screen | Lowest-latency presentation path. |
| V-Sync | Disabled | Adds a full frame of latency. Cap frames and use G-Sync or FreeSync instead. |
| Anti-aliasing | TSAA | None produces heavy shimmer on distant players and foliage, which is worse for tracking than the frames it saves. |
| Texture Streaming Budget | Match your VRAM (one step below the maximum your card supports) | Setting it above your VRAM causes repeated hitching rather than a lower average frame rate. This is the most commonly misconfigured setting in the game. |
| Texture Filtering | Anisotropic 2x-4x | 16x costs frames for floor detail. 2x-4x is the sensible middle. |
| Ambient Occlusion Quality | Disabled | Meaningful GPU cost for a subtle contact-shadow effect with no competitive value. |
| Sun Shadow Coverage / Detail | Low | Large saving. Apex does not project enemy shadows in a way you can reliably read. |
| Volumetric Lighting | Disabled | One of the two largest costs in the menu, and it obscures targets in god-ray areas. |
| Dynamic Spot Shadows | Disabled | The other large cost. Also removes flickering shadow noise in interiors. |
| Model Detail | Low | Reduces CPU and GPU work on characters and props without making players harder to identify. |
| Effects Detail | Low | Ability and explosion effects. This is where frame rate collapses in final circles. |
| Impact Marks | Disabled | Bullet decals accumulate through a fight and cost frames for information you already have from the tracers. |
| Ragdolls | Low | Physics on downed players. Pure cost. |
| NVIDIA Reflex | On + Boost | Shortens the render queue. Apex is often CPU-bound in fights, which is exactly where Boost helps. |

## Launch options

In Steam, right-click Apex Legends, Properties, Launch Options. In the EA app, find the game settings and use the advanced launch options field.

```text
+fps_max 237 -preload
```

- **+fps_max** - set this to about three below your refresh rate (237 on 240 Hz, 141 on 144 Hz). Apex is noticeably less stable uncapped, and the cap improves frame-time consistency more than the lost peak frames cost you.
- **-preload** - preloads assets at launch rather than streaming them in during the first match. Reduces early-game hitching at the cost of a slightly longer startup.
- Avoid **-high**. Raising process priority above system threads causes audio and input stutter more often than it helps on modern schedulers.
- Avoid **-novid** style options inherited from other Source games - Apex does not use them.
- Be cautious with any launch option or config file you find in a tweak pack. Apex runs kernel-level anti-cheat, and the boundary you must not cross is modifying game files.

> **The anti-cheat line:** Launch options the game itself documents are fine. Editing files inside the game directory to unlock settings the menu does not expose is not, and it is the pattern anti-cheat is built to detect. If a guide tells you to replace a game file, close it.

## System-side changes

- Enable XMP or EXPO in BIOS. Apex is CPU and memory sensitive in the late game when many players are compressed into a small area.
- Set the Windows power mode to Best performance.
- Install on an SSD. Drop-in and first-ring asset streaming is where mechanical drives show up as hitching.
- Close hardware-accelerated browser tabs and streaming overlays before playing.
- Verify your monitor is at its full refresh rate in Windows display settings.
- If you use a high-polling-rate mouse, move it to a rear USB port directly off the chipset rather than a front-panel hub.

**Apex profile in Pro** - Frozen Tweaks includes an Apex Legends profile handling the Windows, power, storage and latency configuration around these settings. [See the game profiles](https://frozentweaks.com/purchase)

## Frequently asked questions

### What should Adaptive Resolution FPS Target be in Apex Legends?

Zero, which disables it. Adaptive Resolution keeps your frame counter stable by dynamically lowering internal render resolution when performance dips - meaning the image degrades precisely when a fight starts and distant enemies get blurrier at the worst possible moment. Set it to 0, accept the honest frame rate, and lower other settings if you need more.

### What are the best Apex Legends launch options?

+fps_max set to about three below your refresh rate, plus -preload. The frame cap improves consistency, which matters more than peak frame rate in Apex, and -preload reduces early-match hitching by loading assets at startup. Avoid -high, which causes audio and input stutter on modern schedulers more often than it helps, and avoid anything that modifies files in the game directory.

### Why does Apex Legends stutter in fights?

Most commonly Texture Streaming Budget set above your card's VRAM, which causes repeated hitching rather than a lower average frame rate - drop it one step below your card's maximum. After that, lower Effects Detail and disable Impact Marks, since bullet decals accumulate through a fight, and make sure the game is installed on an SSD. Uncapped frame rates also destabilise frame times; add +fps_max.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/apex-legends-fps-boost

---

---
title: "GTA 6 on PC: Release Status and How to Prepare Your Rig"
description: "Where the GTA 6 PC version actually stands as of August 2026, what Rockstar has and has not confirmed, and what is genuinely worth doing to your PC now."
url: https://frozentweaks.com/guides/gta-6-pc-requirements
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Game Guides"
game: "Grand Theft Auto VI"
source: Frozen Tweaks (https://frozentweaks.com)
---

# GTA 6 on PC: Release Status and How to Prepare Your Rig

**Short answer:** As of August 2026, GTA 6 is confirmed for consoles on 19 November 2026, and Rockstar has announced no PC release date, no PC storefront and no PC system requirements. Based on Rockstar's history - seven to nineteen months between console and PC launches for its last three major titles - a PC version is unlikely before late 2027. Treat every published GTA 6 PC requirements list as speculation.

## At a glance

| | |
| --- | --- |
| Console release | 19 November 2026 (PS5, Xbox Series X|S) |
| PC release date | Not announced |
| PC system requirements | Not published |
| PC storefront | Not announced |
| Historical console-to-PC gap | 7 to 19 months across Rockstar's last three releases |

## Key takeaways

- GTA 6 launches on PS5 and Xbox Series X|S on 19 November 2026. There is no PC release date.
- Rockstar has published no PC system requirements. Every requirements table currently circulating is invented.
- Rockstar's console-to-PC gap on its last three major releases ran from seven to nineteen months, which puts a realistic PC window in late 2027 at the earliest.
- Do not buy hardware for GTA 6 now. Anything you purchase in 2026 for a 2027-plus release is a year of depreciation for a specification nobody has seen.
- The preparation that is genuinely worth doing is the preparation that helps you today anyway - storage, memory configuration and a tuned Windows install.

## What is actually confirmed

This is a topic where a great deal of published content is guesswork presented as fact, so it is worth being precise about the line between the two.

**Confirmed versus speculation, as of August 2026**
| Setting | Recommended | Why |
| --- | --- | --- |
| Console release date | Confirmed: 19 November 2026 | PlayStation 5 and Xbox Series X|S. Not coming to PS4 or Xbox One. |
| PC release date | Not announced | Rockstar has made no statement about a PC version's timing. |
| PC system requirements | Not published | No minimum or recommended specification exists. Every table you have seen was assembled by someone estimating from console hardware. |
| PC storefront | Not announced | No confirmation of Steam, Epic, or a Rockstar-launcher exclusivity window. |
| Likely PC timing | Speculation: late 2027 at the earliest | Inferred from Rockstar's pattern, not from any statement. The gap between console and PC on its last three major titles ranged from about seven months to about nineteen. |

> **About the requirements tables you have seen:** If a site is showing you a GTA 6 minimum and recommended specification with named GPUs, it is fabricated. Rockstar has published nothing. This is worth knowing because those tables are being used to sell hardware.

## Why buying hardware now is a bad idea

The temptation to build for GTA 6 is understandable and the timing makes it a poor decision. Consider what happens to a component bought in August 2026 for a game that, on Rockstar's own historical pattern, arrives no earlier than late 2027.

- You lose a year or more of warranty coverage before the game exists.
- You pay 2026 prices for a card that will have a successor generation available by launch.
- You are buying against a specification nobody has published, so you cannot even confirm you bought the right thing.
- Rockstar PC ports historically arrive with substantially expanded graphics options relative to the console version, which means the console hardware is a poor proxy for what a PC build will want.

The rational move is to wait for Rockstar to publish requirements, then buy against them, in a market that will have moved a full generation by that point.

## What is worth doing to your PC now

There is a version of preparation that is not speculative, and it is the version where everything you do also improves the games you are playing today. None of this is GTA 6 specific - it is just good practice that happens to also be the right foundation.

1. **Sort out storage capacity and type** - Rockstar open-world titles are large and stream aggressively. An NVMe SSD with meaningful free space is the one component decision that is safe to make early, because it benefits every game you own right now and storage is the least likely component to be obsoleted by a specification announcement.
2. **Enable XMP or EXPO** - Free, instant, and worth 5-15% in CPU-bound games today. Open-world titles with heavy simulation are exactly the workload that benefits most from a properly configured memory profile.
3. **Get your Windows install in order** - Power mode, startup applications, driver hygiene and monitor refresh rate. This is the work that decays over time and that most people never do, and it applies to every title regardless of what launches when.
4. **Learn your own bottleneck** - Spend twenty minutes with an overlay watching CPU and GPU utilisation across the games you actually play. When requirements are finally published, you will know which component is your real constraint instead of guessing.

**Tune what you have today** - Frozen Tweaks handles the Windows, power and driver configuration described above, and re-applies it after updates - useful now, and the right foundation whenever GTA 6 does arrive. [Download Frozen Tweaks](https://frozentweaks.com/purchase)

## Frequently asked questions

### Is GTA 6 coming to PC?

Almost certainly, but Rockstar has not announced it. As of August 2026 there is no PC release date, no PC storefront and no published PC system requirements. Every previous mainline Grand Theft Auto has eventually reached PC, so the question is timing rather than whether - and Rockstar's pattern on its last three major releases suggests a gap of roughly seven to nineteen months after the console launch.

### When is the GTA 6 PC release date?

Unannounced. The console version launches on 19 November 2026 for PS5 and Xbox Series X|S. Based on Rockstar's historical console-to-PC gap, a PC release is unlikely before late 2027, but that is inference from past behaviour rather than a statement from Rockstar. Anyone quoting a specific PC date is speculating.

### What are the GTA 6 PC system requirements?

There are none published. Rockstar has released no minimum or recommended specification for a PC version, because it has not announced a PC version. Every requirements table currently circulating was assembled by estimating from console hardware, and several of them are being used to sell graphics cards. Wait for official figures before buying anything.

### Should I upgrade my PC now for GTA 6?

No. You would be spending 2026 prices, against an unpublished specification, for a game that on Rockstar's own historical pattern arrives no earlier than late 2027 - by which point a new GPU generation will be available and your warranty will be a year shorter. The exception is storage: an NVMe SSD with free space benefits every game you play today and is the least likely purchase to be invalidated by an announcement.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/gta-6-pc-requirements

---

---
title: "How to Reduce Input Lag on PC: The Whole Latency Chain"
description: "Input lag is nine separate delays stacked together. Here is each one, how much it costs you in milliseconds, and which are actually worth fixing."
url: https://frozentweaks.com/guides/reduce-input-lag
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Latency & Networking"
source: Frozen Tweaks (https://frozentweaks.com)
---

# How to Reduce Input Lag on PC: The Whole Latency Chain

**Short answer:** To reduce input lag, work through the whole chain: turn V-Sync off, cap your frame rate about three below your refresh rate with G-Sync or FreeSync on, enable NVIDIA Reflex or AMD Anti-Lag 2, play in exclusive fullscreen, disable Enhance Pointer Precision in Windows, use raw input in game, and set your monitor overdrive to its middle setting. Those changes typically remove 20-40 ms of end-to-end delay.

## At a glance

| | |
| --- | --- |
| What you are measuring | Click-to-photon: input to visible response |
| Typical untuned system | 50-80 ms |
| Typical tuned system | 20-40 ms |
| Biggest single cost | V-Sync - up to a full frame |
| Cheapest fix | Frame cap below refresh with VRR on |

## Key takeaways

- Frame rate and input lag are related but different. You can have 300 FPS and terrible latency, and the usual cause is V-Sync.
- The three largest, cheapest wins are: V-Sync off, a frame cap inside the VRR window, and Reflex or Anti-Lag enabled.
- Going from 60 Hz to 144 Hz removes far more latency than going from 144 Hz to 240 Hz. The returns diminish sharply.
- Mouse polling above 1000 Hz has very small returns and measurably increases CPU load - it is not a free upgrade.
- Enhance Pointer Precision is mouse acceleration. It does not add latency but it makes your aim inconsistent, which people misreport as lag.

## The nine stages between your click and the screen

What people call input lag is properly called click-to-photon latency: the total time between your finger moving and a photon changing on your monitor. It is not one delay. It is nine, in series, and fixing the wrong one gets you nothing.

**Where the milliseconds go**
| Setting | Recommended | Why |
| --- | --- | --- |
| 1. Mouse sensor and switch | 1-3 ms | Determined by polling rate and switch debounce. Already small on any modern gaming mouse; not where your problem is. |
| 2. USB transport | under 1 ms | Effectively free unless you are on a saturated hub. Move high-polling mice to a rear port off the chipset. |
| 3. Windows input processing | 1-2 ms | Small, but this is where mouse acceleration lives. Raw input in game bypasses part of this stack. |
| 4. Game simulation tick | 1-8 ms | How often the engine samples input. Largely fixed by the game; higher frame rates sample more often in most engines. |
| 5. Render queue | 0-30 ms | The big one. Frames queued ahead of the GPU wait their turn. This is exactly what NVIDIA Reflex and AMD Anti-Lag shorten. |
| 6. GPU render time | 3-20 ms | Inversely proportional to frame rate. Higher FPS genuinely helps here, with diminishing returns. |
| 7. Present and composition | 0-16 ms | Exclusive fullscreen is near zero. Borderless windowed goes through the compositor unless Windows windowed-game optimizations are on. |
| 8. Scanout | 4-16 ms | Set by refresh rate. A 240 Hz panel scans a frame in about 4 ms, a 60 Hz panel in about 16 ms. |
| 9. Panel response | 1-10 ms | Pixel transition time, controlled by your overdrive setting. Too high produces inverse ghosting, which looks worse than it measures. |

> **Where to spend your effort:** Stages 5, 7 and 8 hold almost all of the recoverable latency on a typical system. Stages 1 through 3 are where people spend money, and they are already close to free.

## The changes that actually remove milliseconds

1. **Turn V-Sync off everywhere** - In game, in the NVIDIA Control Panel or AMD Adrenalin, and in any third-party limiter. V-Sync holds a completed frame until the next refresh, which costs up to a full refresh interval - 16 ms at 60 Hz. It is the single most expensive latency setting on most systems.
2. **Cap your frame rate below your refresh rate** - With G-Sync or FreeSync enabled, cap about three frames below your panel's refresh - 237 on 240 Hz, 141 on 144 Hz. Running uncapped pushes you against the refresh ceiling where frames queue, which reintroduces exactly the delay you removed by disabling V-Sync.
3. **Enable NVIDIA Reflex or AMD Anti-Lag 2** - Turn it on in every game that offers it, and use On + Boost on NVIDIA. It shortens the render queue directly, which is stage 5 - the largest recoverable chunk. The frame cost is small and the latency reduction is not.
4. **Play in exclusive fullscreen** - Borderless windowed routes your frames through the Windows compositor. If you need borderless for alt-tabbing, at least enable 'Optimizations for windowed games' in Settings > System > Display > Graphics, which recovers most of the difference.
5. **Confirm your monitor is at full refresh rate** - Settings > System > Display > Advanced display. Windows regularly reverts a high-refresh monitor to 60 Hz after a driver install or cable change, and this is the most common cause of a new monitor not feeling different.
6. **Set monitor overdrive to its middle option** - Usually labelled Normal, Medium or Fast. The most aggressive setting produces inverse ghosting - bright trails behind moving objects - which is visually worse than the response time it saves. The panel's rated response time is measured at a setting most people should not use.
7. **Disable Enhance Pointer Precision** - Settings > Bluetooth & devices > Mouse > Additional mouse settings > Pointer Options. This is mouse acceleration. It does not add latency, but it makes the same physical movement produce different cursor distances, which players consistently describe as the game feeling laggy or inconsistent.
8. **Turn on raw input in game** - Where the option exists, it bypasses part of the Windows pointer pipeline and ignores desktop sensitivity and acceleration settings entirely.

## Where the returns stop being worth it

Latency chasing has a point past which you are spending money for immeasurable gains. It is useful to know roughly where that point is.

**Honest cost-benefit on the popular upgrades**
| Setting | Recommended | Why |
| --- | --- | --- |
| 60 Hz to 144 Hz | Large, obvious | Scanout drops from about 16 ms to about 7 ms and frame delivery roughly doubles. This is the single most noticeable hardware upgrade available. |
| 144 Hz to 240 Hz | Modest, noticeable to some | Scanout drops from about 7 ms to about 4 ms. Real, but a fraction of the previous step. Worth it if you are already at the top of your game; not a fix for anything. |
| 240 Hz to 360 Hz+ | Very small | Roughly a further 1 ms. At this point your monitor is no longer the constraint and you would gain more from anything else on this page. |
| 1000 Hz to 4000/8000 Hz mouse polling | Very small, with a cost | Saves a fraction of a millisecond and measurably increases CPU interrupt load, which can hurt 1% lows in CPU-bound games. This is not a free upgrade and it is sometimes a net loss. |
| Wired versus 2.4 GHz wireless | Negligible on modern gear | Current dedicated gaming wireless is within about a millisecond of wired. Bluetooth is a different matter and should not be used for gaming. |
| Frame rate above 3x your refresh rate | Very small | GPU render time is already tiny at that point. The remaining latency is in scanout and panel response, which frame rate cannot touch. |

## Measuring instead of guessing

Perceived input lag is extremely unreliable. People report a game feeling worse after a patch that changed nothing, and better after a placebo tweak. If you are going to tune this, measure it.

- NVIDIA's overlay reports a PC latency figure on supported games and GPUs, which covers stages 3 through 7. It is the easiest starting point.
- A high-frame-rate phone camera pointed at your mouse and monitor together works surprisingly well - count frames between the click and the muzzle flash.
- Change one thing at a time and re-measure. Applying six tweaks and declaring the result better tells you nothing about which one worked.
- Test in the same scene. Latency varies with GPU load, so a benchmark in an empty range does not describe a teamfight.

**Apply the system side automatically** - Frozen Tweaks configures the Windows, power, driver and presentation settings on this page, and keeps them applied after updates revert them. [Download Frozen Tweaks](https://frozentweaks.com/purchase)

## Frequently asked questions

### Why does my game feel laggy at high FPS?

Because frame rate and input latency are different measurements. The usual causes are V-Sync enabled somewhere in the chain, which costs up to a full refresh interval, no frame cap on a variable-refresh display so frames queue at the refresh ceiling, NVIDIA Reflex or AMD Anti-Lag being off, or running borderless windowed without the Windows windowed-game optimization enabled. Any one of those can add more delay than a large frame-rate increase removes.

### Does a higher mouse polling rate reduce input lag?

Barely, and it is not free. Going from 1000 Hz to 4000 or 8000 Hz saves a fraction of a millisecond while measurably increasing CPU interrupt load, which can hurt 1% lows in CPU-bound games like CS2 and Valorant. On most systems it is a net neutral change and on some it is a net loss. 1000 Hz is the sensible default.

### Should I turn V-Sync on or off to reduce input lag?

Off, in the game and in your GPU control panel. V-Sync holds a finished frame until the monitor's next refresh, adding up to a full refresh interval of delay - about 16 ms at 60 Hz. The exception is a G-Sync setup where enabling V-Sync in the NVIDIA Control Panel while capping frames below the refresh rate acts as a safety net at the top of the VRR range rather than as a frame limiter.

### Is 240 Hz worth it over 144 Hz for input lag?

It is a real but modest improvement - scanout drops from roughly 7 ms to roughly 4 ms. That is a fraction of the gain you get moving from 60 Hz to 144 Hz. Worth having if your setup is otherwise fully tuned; not a solution to a game that feels bad, which is almost always a V-Sync, frame cap or Reflex problem rather than a refresh rate one.

### Does Enhance Pointer Precision cause input lag?

No, it causes inconsistency, which people describe as lag. Enhance Pointer Precision is mouse acceleration: the same physical movement produces a different cursor distance depending on how fast you move. That breaks muscle memory for aiming. Turn it off in Pointer Options and enable raw input in game, which ignores Windows pointer settings entirely.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/reduce-input-lag

---

---
title: "How to Fix Stuttering and Frame Drops: Diagnose Before You Tweak"
description: "Stutter has six distinct causes and each has a different fix. Match your symptom to the right one instead of applying tweaks at random."
url: https://frozentweaks.com/guides/fix-stuttering-frame-drops
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Windows & Hardware"
source: Frozen Tweaks (https://frozentweaks.com)
---

# How to Fix Stuttering and Frame Drops: Diagnose Before You Tweak

**Short answer:** Stuttering has six common causes, and the symptom tells you which: hitching only after a patch is shader compilation and resolves itself; hitching in fixed locations is asset streaming from a slow drive; hitching that worsens over a session is VRAM or memory pressure; a regular pulse is a background process or overlay; hitching under load is thermal or power throttling; and audio crackling alongside it points to a DPC latency problem from a driver.

## At a glance

| | |
| --- | --- |
| What to measure | Frame time (ms) and 1% lows, not average FPS |
| Number of distinct causes | Six, with different fixes |
| Most common on new games | Shader compilation (self-resolving) |
| Most common on old systems | Background processes and overlays |
| Most misdiagnosed | VRAM exhaustion, blamed on the CPU |

## Key takeaways

- Stutter is a frame-time problem, not a frame-rate problem. Your average FPS can look perfect while the game is unplayable.
- Identify the pattern before changing anything. The six causes have almost no overlap in their fixes.
- Shader compilation stutter after a patch is normal Unreal Engine 5 behaviour and needs no fix at all.
- Exceeding VRAM produces sharp repeated hitching rather than a lower average - drop textures one step, not resolution.
- Audio crackling alongside stutter almost always means a driver DPC latency problem, most often network, audio or chipset.

## Measure frame time, not frame rate

Average FPS is a mean, and a mean hides exactly the information you need. A game running at an average of 150 FPS might be delivering a steady frame every 6.7 ms, or it might be alternating between 4 ms and 40 ms. The first is smooth. The second is a slideshow that reports 150 FPS.

Turn on a frame-time graph in your GPU vendor's overlay or a capture tool before you change anything. What you are looking for is the shape of the spikes: how tall, how often, and whether they correlate with anything you are doing.

> **Record 1% lows:** The 1% low figure is the average of your worst one percent of frames. It correlates with how a game feels far better than the average does, and it is the number to compare before and after any change you make.

## The six causes and how to tell them apart

**Match your symptom to the cause**
| Setting | Recommended | Why |
| --- | --- | --- |
| Heavy hitching only in the first minutes after a game patch, driver update or Windows update, then completely fine | Shader compilation | Normal Unreal Engine 5 behaviour. The engine compiles shaders on demand and caches them. No fix required - play through it and do not change settings based on that session. |
| Reproducible hitches in the same physical locations, or when entering new areas | Asset streaming from slow storage | Move the game to an NVMe SSD and keep 15-20% of the drive free. This is the dominant cause of traversal stutter in open-world and UE5 titles. |
| Smooth at first, progressively worse over a session, sharp repeated hitches | VRAM or system memory exhaustion | Drop texture quality one step and check VRAM usage in your overlay. Exceeding VRAM causes hitching rather than a lower average, which is why people misdiagnose it as a CPU problem. Close background applications. |
| A regular pulse every few seconds regardless of what is happening in game | A background process or overlay | Disable overlays, RGB software, capture utilities and vendor updaters one at a time. Hardware-accelerated browser tabs are the single most common culprit. |
| Fine for the first few minutes of a session, then frame rate steps down and stays down | Thermal or power throttling | Check GPU and CPU temperatures and clock speeds in your overlay. On laptops, confirm you are plugged in and on the manufacturer's performance profile. Clean dust filters; repaste if the machine is several years old. |
| Stutter accompanied by audio crackling or popping | DPC latency from a driver | A driver is holding the CPU too long at high interrupt priority. The usual suspects are network adapters, audio drivers, and chipset drivers. Update them, and disable network adapter power saving in Device Manager. |

## The fixes, in order

1. **Rule out shader compilation** - If anything updated recently - the game, your GPU driver, or Windows - play two full sessions before investigating further. A large share of stutter reports are a shader cache that had not finished building, and every tweak applied during that window gets false credit when the hitching stops on its own.
2. **Check your storage** - Confirm the game is on an SSD, and that the drive has at least 15-20% free space. Full SSDs slow substantially. Several 2025-2026 releases treat an SSD as a hard requirement and behave badly without one.
3. **Check VRAM headroom** - Watch VRAM usage in your overlay during play. If you are at or near your card's capacity, drop texture quality one step. Do not lower resolution first - that hurts your ability to see enemies and often does not fix the hitching.
4. **Strip background software** - Task Manager > Startup apps, and disable everything that is not essential. Then close browsers, Discord streams and capture software before playing. Re-test after each removal rather than all at once.
5. **Check temperatures and clocks** - If frame rate steps down after several minutes and stays down, you are throttling. Look at GPU hotspot temperature and CPU package temperature under load, and at whether clocks are dropping below their expected boost range.
6. **Investigate DPC latency if audio is affected** - Crackling audio alongside stutter is a strong signal. Update network, audio and chipset drivers from the vendor rather than Windows Update, and turn off the 'Allow the computer to turn off this device to save power' option on your network adapter in Device Manager.
7. **Set the Windows power mode to Best performance** - Core parking and lazy clock ramping produce exactly the intermittent frame-time spikes that read as micro-stutter, and they are more visible on frame-time graphs than in average FPS.

## Things that look like stutter but are not

- **Network lag in multiplayer.** Rubber-banding and delayed hit registration are server-side or connection problems. No client-side graphics setting fixes them. Check ping, jitter and packet loss in the game's network overlay first.
- **Screen tearing.** A visible horizontal split during fast movement is a synchronisation artefact, not a frame-time problem. Enable G-Sync or FreeSync and cap frames below your refresh rate.
- **Inverse ghosting.** Bright trails behind moving objects come from monitor overdrive set too aggressively. Reduce it to the middle setting.
- **Frame generation artefacts.** DLSS and FSR frame generation can produce a smooth but odd-feeling result because latency does not improve with the interpolated frames. If the game looks smooth and feels heavy, try it off.
- **Perceived stutter after a settings change you expected to help.** Extremely common and unreliable. Compare recorded 1% lows, not impressions.

**Rule out the system side in one pass** - Frozen Tweaks handles the power, startup, storage and driver-side configuration in this guide, so you can eliminate the whole system-level category in one step and focus on the game. [Download Frozen Tweaks](https://frozentweaks.com/purchase)

## Frequently asked questions

### Why does my game stutter even though my FPS is high?

Because average FPS hides frame-time spikes. A game averaging 150 FPS can be alternating between 4 ms and 40 ms frames, which feels terrible while reporting an excellent number. Turn on a frame-time graph and look at your 1% lows instead. Then match the pattern of the spikes to a cause: shader compilation, storage streaming, VRAM exhaustion, a background process, thermal throttling, or driver DPC latency.

### How do I fix shader compilation stutter?

You do not need to - it fixes itself. Unreal Engine 5 compiles shaders on demand and caches them, so the first session after a game patch, GPU driver update or Windows update hitches heavily and then runs cleanly. Play two full sessions before changing anything. Some games offer a shader pre-compilation step at launch; let it finish rather than skipping it.

### Does running out of VRAM cause stuttering?

Yes, and it is one of the most misdiagnosed causes. Exceeding VRAM does not produce a smoothly lower frame rate; it produces sharp, repeated hitching as the driver evicts and re-uploads assets, and it typically gets worse the longer you play. Watch VRAM usage in an overlay, and if you are near capacity, drop texture quality one step rather than lowering resolution.

### What causes micro stutter every few seconds?

A regular pulse independent of what is happening in the game almost always points to a background process. Disable overlays, RGB utilities, capture software and vendor updaters one at a time, and close hardware-accelerated browser tabs - those are the most frequent cause. If the stutter is accompanied by audio crackling, it is instead a driver DPC latency problem, usually from a network, audio or chipset driver.

### Can stuttering be caused by my hard drive?

Yes. Hitching that reproduces in the same physical locations, or when entering a new area, is asset streaming that the drive cannot keep up with. Move the game to an NVMe SSD and keep at least 15-20% of the drive free, because full SSDs slow down significantly. Several 2025-2026 releases list an SSD as a hard requirement precisely because of this.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/fix-stuttering-frame-drops

---

---
title: "Best NVIDIA Control Panel Settings for Gaming in 2026"
description: "Every NVIDIA 3D setting that still matters, what to set it to, and why - plus the ones that have done nothing for years."
url: https://frozentweaks.com/guides/nvidia-control-panel-best-settings
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Windows & Hardware"
source: Frozen Tweaks (https://frozentweaks.com)
---

# Best NVIDIA Control Panel Settings for Gaming in 2026

**Short answer:** The NVIDIA settings that matter are: Power management mode set to Prefer maximum performance, Low Latency Mode Ultra only in games without Reflex, Max Frame Rate capped about three below your refresh, Texture filtering quality set to High performance, Shader Cache Size at 10 GB or Unlimited, Monitor Technology set to G-SYNC Compatible, Preferred refresh rate at Highest available, and Vertical sync off unless you run G-Sync.

## At a glance

| | |
| --- | --- |
| Where | NVIDIA Control Panel > Manage 3D settings, or the NVIDIA app |
| Apply | Globally, then override per game where needed |
| Most useful setting | Power management mode: Prefer maximum performance |
| Most misconfigured | V-Sync and G-Sync combination |
| Reversible | Yes - Restore Defaults button in the panel |

## Quick setup

1. **Open Manage 3D settings and work in Global Settings first** - Set your baseline globally so new games inherit it, then add Program Settings overrides only where a specific title needs different behaviour.
2. **Set Power management mode to Prefer maximum performance** - The most reliably useful setting in the panel. It stops the GPU dropping clocks between frames, a common source of inconsistent frame times in CPU-bound games.
3. **Set Low Latency Mode to Ultra globally** - Then override it to Off per game for any title with in-game NVIDIA Reflex - they do the same job and Reflex does it with better information.
4. **Take the texture filtering trade** - Texture filtering Quality to High performance, with Anisotropic sample optimization and Trilinear optimization on. Set Shader Cache Size to 10 GB or Unlimited while you are here.
5. **Configure G-Sync correctly** - Enable G-Sync for full screen and windowed mode, set Monitor Technology to G-SYNC Compatible, set Vertical sync to On in the driver, turn V-Sync off in game, and cap frames about three below your refresh rate.
6. **Set Max Frame Rate as a fallback limiter** - About three below your refresh rate, for games with no reliable in-game limiter. Set Preferred refresh rate to Highest available at the same time.

## Key takeaways

- Power management mode set to Prefer maximum performance is the most reliably useful setting in the panel.
- Low Latency Mode Ultra and in-game NVIDIA Reflex do the same job. Use Reflex where it exists and leave the driver setting off for that game.
- The correct G-Sync configuration is: G-Sync on, V-Sync on in the driver, V-Sync off in game, frame cap about three below refresh.
- Texture filtering quality set to High performance is one of the few remaining image-quality trades worth taking in competitive games.
- Several settings people still recommend - triple buffering, FXAA, DSR - do nothing useful for a modern competitive setup.

## Where these settings live now

NVIDIA has been consolidating its software: the NVIDIA app now hosts driver updates, per-game profiles and an increasing share of what used to live only in the classic NVIDIA Control Panel. The 3D settings themselves are the same regardless of which interface you use them from.

Set these globally first under **Manage 3D settings > Global Settings**, then add per-game overrides under Program Settings only where a specific title needs different behaviour. Global first is the right order because it means new games inherit a sensible baseline.

## The settings that matter

**Manage 3D settings**
| Setting | Recommended | Why |
| --- | --- | --- |
| Power management mode | Prefer maximum performance | The most reliably useful setting here. Stops the GPU dropping clocks between frames, which is a common source of inconsistent frame times in CPU-bound games where GPU load is low. |
| Low Latency Mode | Ultra - but only for games without Reflex | Does the same job as NVIDIA Reflex at the driver level. If a game has in-game Reflex, use that and set this to Off for that title; running both is redundant and occasionally worse. |
| Max Frame Rate | About 3 below your refresh rate | A driver-level frame cap that stays inside the VRR window. Use this when a game has no reliable in-game limiter. |
| Monitor Technology | G-SYNC Compatible | Enables variable refresh on a FreeSync or G-Sync Compatible panel. Also confirm G-Sync is enabled under Set up G-SYNC. |
| Preferred refresh rate | Highest available | Prevents games that request a lower refresh from getting it. Cheap insurance against the 60 Hz problem. |
| Vertical sync | Off - or On if you use G-Sync | With G-Sync plus a frame cap below refresh, V-Sync On in the driver acts as a safety net at the top of the VRR range and adds no latency because you never reach it. Without G-Sync, leave it off. |
| Texture filtering - Quality | High performance | Reduces filtering work across the whole scene. One of the few remaining image-quality trades worth taking in a competitive title. |
| Texture filtering - Anisotropic sample optimization | On | Part of the same trade. Small gain, negligible visual cost at gameplay distances. |
| Texture filtering - Trilinear optimization | On | As above. |
| Shader Cache Size | 10 GB or Unlimited | A larger cache means fewer shader recompilations, which means less stutter after driver updates. Costs disk space and nothing else. |
| Threaded optimization | Auto | Let the driver decide. Forcing it on or off helps in a small number of older titles and hurts in others. |
| Background Application Max Frame Rate | On, around 30 FPS | Caps frame rate when a game is not focused. Useful if you alt-tab during matchmaking - it stops an unfocused game consuming the whole GPU. |
| Ambient Occlusion | Off | Driver-level AO is expensive and games handle this better themselves. |
| Antialiasing - FXAA | Off | A driver-level post-process blur. Modern in-game anti-aliasing is strictly better. |
| DSR Factors | Off | Renders above your native resolution and downsamples. The opposite of what you want in a competitive game. |
| Triple buffering | Off | Only applies to OpenGL titles and adds latency where it does apply. |

## The correct G-Sync configuration

This is the most commonly misconfigured combination in PC gaming, and getting it wrong costs you either tearing or a frame of latency. There is one correct arrangement.

1. **Set up G-SYNC** in the control panel: enable it, and select 'Enable for full screen and windowed mode'.
2. **Monitor Technology** under Manage 3D settings: G-SYNC Compatible.
3. **Vertical sync** in the NVIDIA Control Panel: On. This is the safety net, not a limiter.
4. **V-Sync in the game**: Off. Always.
5. **Frame cap**: about three below your refresh rate, set in game if possible, otherwise via Max Frame Rate in the driver.
6. **NVIDIA Reflex** in game: On + Boost.

> **Why V-Sync On in the driver is not a mistake:** Because the frame cap keeps you below the refresh ceiling, driver V-Sync never actually engages. It only exists to catch the rare frame that would otherwise exceed the VRR range and tear. You get the tear-free result without paying the latency cost, which is the entire point of the arrangement.

**Set and keep these automatically** - Driver installs reset 3D settings to defaults. Frozen Tweaks re-applies your GPU configuration after clean driver installations so your tuning does not quietly disappear. [Download Frozen Tweaks](https://frozentweaks.com/purchase)

## Frequently asked questions

### Should Low Latency Mode be Ultra or Off?

Ultra for games that do not have NVIDIA Reflex, Off for games that do. They perform the same function - shortening the render queue - and in-game Reflex does it with better information about the engine's workload. Running both is redundant and occasionally produces slightly worse results than Reflex alone. Set the global default to Ultra and override to Off for your Reflex-supporting titles.

### What is the correct V-Sync setting with G-Sync?

V-Sync On in the NVIDIA Control Panel, V-Sync Off in the game, and a frame cap about three below your refresh rate. The cap keeps you inside the variable-refresh window so driver V-Sync never actually engages - it exists only as a safety net against the occasional frame that would exceed the range and tear. You get tear-free output with no added latency.

### Does Prefer maximum performance actually help?

Yes, and it is the most reliably useful setting in the panel. It stops the GPU from dropping clock speeds between frames, which matters most in CPU-bound games where GPU utilisation is low and the driver would otherwise decide the card can idle. The visible effect is more consistent frame times rather than a higher average. The cost is higher idle power draw and slightly more heat.

### What should I set Shader Cache Size to?

10 GB, or Unlimited if you have the disk space. A larger shader cache means fewer recompilations, which means less stutter after driver updates and when returning to a game you have not played recently. The only cost is disk space. This is one of the genuinely free settings in the panel.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/nvidia-control-panel-best-settings

---

---
title: "Best AMD Adrenalin Settings for Gaming in 2026"
description: "How to configure Radeon Anti-Lag 2, FreeSync, texture filtering and HYPR-RX for competitive gaming - and which Adrenalin features to leave switched off."
url: https://frozentweaks.com/guides/amd-adrenalin-best-settings
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Windows & Hardware"
source: Frozen Tweaks (https://frozentweaks.com)
---

# Best AMD Adrenalin Settings for Gaming in 2026

**Short answer:** For competitive gaming on a Radeon GPU, enable Radeon Anti-Lag 2, turn Radeon Chill and Radeon Boost off, set Texture Filtering Quality to Performance, enable Surface Format Optimization, leave Wait for Vertical Refresh off unless the application specifies, enable FreeSync, and set Frame Rate Target Control about three below your refresh rate. Enable Smart Access Memory in BIOS if your platform supports it.

## At a glance

| | |
| --- | --- |
| Where | AMD Software: Adrenalin Edition > Gaming > Graphics |
| Latency setting | Radeon Anti-Lag 2 |
| Turn off | Radeon Chill, Radeon Boost, Enhanced Sync |
| BIOS side | Smart Access Memory / Resizable BAR |
| Reversible | Yes - Reset to factory defaults in Adrenalin |

## Quick setup

1. **Enable Radeon Anti-Lag 2** - The Radeon equivalent of NVIDIA Reflex. Turn it on in every competitive title that supports it - the frame cost is small and the latency reduction is one of the largest available from a single setting.
2. **Disable Radeon Chill and Radeon Boost** - Both dynamically reduce work to save power - Chill by lowering frame rate when the action is calm, Boost by lowering resolution during fast movement. Both do it at exactly the wrong moment for a shooter.
3. **Take the texture and format trades** - Texture Filtering Quality to Performance, Surface Format Optimization enabled, Tessellation Mode to AMD optimized. Leave anti-aliasing and anisotropic filtering set to use application settings.
4. **Configure FreeSync end to end** - Enable FreeSync in the monitor's own on-screen menu first, then in Adrenalin, then set Frame Rate Target Control about three below your refresh rate and turn V-Sync off in game.
5. **Enable Smart Access Memory and EXPO in BIOS** - Both are platform settings rather than Adrenalin ones, both are free, and Smart Access Memory requires UEFI boot with CSM disabled.
6. **Install chipset drivers from AMD, not Windows Update** - The AMD package includes the power plan and scheduler behaviour Ryzen CPUs expect. Windows Update ships a generic, older version.

## Key takeaways

- Radeon Anti-Lag 2 is the AMD equivalent of NVIDIA Reflex and should be on in every competitive title that supports it.
- Radeon Chill and Radeon Boost both dynamically reduce work to save power. Both are wrong for competitive play.
- Smart Access Memory (Resizable BAR) is a BIOS setting, not an Adrenalin one, and it is worth real performance on supported platforms.
- HYPR-RX is a one-click bundle. Convenient, but understand what it turns on before you use it.
- Enhanced Sync is not a substitute for FreeSync plus a frame cap, and it introduces instability on some configurations.

## Graphics settings in Adrenalin

**Gaming > Graphics**
| Setting | Recommended | Why |
| --- | --- | --- |
| Radeon Anti-Lag / Anti-Lag 2 | Enabled | AMD's equivalent of NVIDIA Reflex. Shortens the render queue and reduces click-to-photon latency for a small frame cost. On in every competitive title that supports it. |
| Radeon Chill | Disabled | Dynamically lowers frame rate when you are not moving to save power. That is the opposite of what a competitive player wants - it means your frame rate changes the instant a fight starts. |
| Radeon Boost | Disabled | Dynamically lowers resolution during fast movement. Saves frames precisely when you are trying to track a target, at the cost of image clarity in that moment. |
| Wait for Vertical Refresh | Off, unless application specifies | The Adrenalin V-Sync control. Leave it deferring to the game, and turn V-Sync off in the game. |
| Enhanced Sync | Disabled | An alternative synchronisation mode that predates widespread FreeSync. It causes flickering and instability on some configurations, and FreeSync plus a frame cap is a strictly better solution. |
| Frame Rate Target Control | About 3 below your refresh rate | Keeps you inside the FreeSync range and avoids the queue latency of hitting the refresh ceiling. |
| Texture Filtering Quality | Performance | Reduces filtering work scene-wide. A worthwhile trade in competitive titles where surface detail at oblique angles is irrelevant. |
| Surface Format Optimization | Enabled | Lets the driver choose cheaper render target formats where the quality difference is negligible. Free frames. |
| Tessellation Mode | AMD optimized | Caps excessive tessellation levels that some engines request far beyond the point of visible benefit. |
| Anti-Aliasing / Anisotropic Filtering | Use application settings | Games handle these better than a driver override. Overriding them frequently produces artefacts in modern engines. |
| Radeon Image Sharpening | Optional, around 70-80% if used | A cheap post-process sharpen. Useful to offset upscaling softness. Purely a preference setting. |
| Radeon Super Resolution | Only for games without built-in upscaling | A driver-level upscaler. Where a game has its own FSR, XeSS or DLSS implementation, use that instead - it has access to motion vectors that the driver does not. |
| Reset Shader Cache | Only when troubleshooting | Clearing it forces a full recompile, which means a session of stutter. Do not do this routinely. |

## The correct FreeSync configuration

1. Enable FreeSync on the monitor itself, in its on-screen menu. It is frequently off by default.
2. Enable AMD FreeSync in Adrenalin under Gaming > Display.
3. Set Frame Rate Target Control about three below your refresh rate, or use an in-game cap at the same value.
4. Turn V-Sync off in the game.
5. Leave Wait for Vertical Refresh in Adrenalin set to 'Off, unless application specifies'.
6. Enable Radeon Anti-Lag 2 in game or in the per-game Adrenalin profile.

> **Check the monitor's own menu:** A surprising share of 'FreeSync is not working' reports come down to the feature being disabled in the monitor's OSD, or the monitor being connected over a cable or port that does not carry it. Check the physical display before debugging the driver.

## Platform settings outside Adrenalin

**BIOS and Windows**
| Setting | Recommended | Why |
| --- | --- | --- |
| Smart Access Memory / Resizable BAR | Enable in BIOS | Lets the CPU address the full GPU memory pool rather than a small window. Worth real performance on supported platforms, and it is free. Requires UEFI boot and CSM disabled. |
| EXPO memory profile | Enable in BIOS | Runs your memory at its rated speed and timings rather than the JEDEC fallback. One of the largest single gains available on a Ryzen system. |
| Windows power mode | Best performance | Prevents core parking and lazy clock ramping, which show up as frame-time inconsistency rather than lower average FPS. |
| Chipset drivers | Install from AMD, not Windows Update | The AMD chipset package includes the power plan and scheduler behaviour that Ryzen CPUs expect. Windows Update ships a generic older version. |

## What HYPR-RX actually turns on

HYPR-RX is a one-click profile that enables several Adrenalin features together. It is genuinely convenient, and it is worth knowing what you are agreeing to before you press it, because two of the components are things a competitive player would otherwise deliberately disable.

- **Radeon Anti-Lag** - you want this. It is the main reason to use the profile.
- **Radeon Boost** - dynamic resolution reduction during fast movement. In a competitive shooter this degrades image quality exactly when you are tracking a target.
- **Radeon Super Resolution** - driver-level upscaling. Reasonable in games without their own upscaler, redundant and lower quality in games that have one.

For single-player and casual play, HYPR-RX is a sensible default. For competitive shooters, configure the individual settings instead: Anti-Lag on, Boost off, and use the game's own upscaler.

**Keep your configuration after driver updates** - Clean Adrenalin installs reset these settings. Frozen Tweaks re-applies your GPU and platform configuration so it does not silently revert. [Download Frozen Tweaks](https://frozentweaks.com/purchase)

## Frequently asked questions

### Should I use Radeon Chill for gaming?

Not for competitive play. Radeon Chill lowers your frame rate when the on-screen action is calm and raises it when you move, to save power and reduce heat. That means your frame rate and therefore your input latency change at the exact moment a fight begins. It is a reasonable feature for a laptop playing a single-player game, and the wrong choice for a shooter.

### Is Radeon Anti-Lag 2 the same as NVIDIA Reflex?

They solve the same problem in the same way - shortening the render queue so frames are not sitting waiting for the GPU - and the practical effect is comparable. Both need game support for their best results. Enable Anti-Lag 2 in every competitive title on your Radeon card; the frame cost is small and the latency reduction is one of the largest available from a single setting.

### Does Smart Access Memory improve FPS?

Yes, on supported platforms, and it is free. Smart Access Memory (AMD's implementation of Resizable BAR) lets the CPU address the whole GPU memory pool at once instead of through a small window, which reduces transfer overhead. Gains vary by title from negligible to substantial. It is a BIOS setting rather than an Adrenalin one, and it requires UEFI boot with CSM disabled.

### Should I enable HYPR-RX?

For single-player and casual gaming, yes - it is a convenient bundle. For competitive shooters, configure the parts individually instead. HYPR-RX enables Radeon Boost, which dynamically lowers resolution during fast movement and degrades image quality precisely while you are tracking a target, and Radeon Super Resolution, which is redundant in any game with its own upscaler. Keep Anti-Lag, skip the other two.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/amd-adrenalin-best-settings

---

---
title: "Is PC Optimization Software Safe? What to Check Before Installing"
description: "The honest answer depends on one question: does the tool touch your games, or only your operating system? Here is how to tell, and what to verify first."
url: https://frozentweaks.com/guides/is-pc-optimization-software-safe
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Trust & Safety"
source: Frozen Tweaks (https://frozentweaks.com)
---

# Is PC Optimization Software Safe? What to Check Before Installing

**Short answer:** PC optimization software is safe when it only changes Windows, power, driver and network settings, keeps a reversible record of every change, and never enters the game process. It is genuinely risky when it injects DLLs, modifies game files, hooks the renderer, or requires you to disable antivirus - those behaviours can trigger anti-cheat bans regardless of intent. Check which category a tool falls into before installing it.

## At a glance

| | |
| --- | --- |
| Safe category | OS, power, driver and network settings |
| Risky category | Injection, game file edits, renderer hooks |
| Non-negotiable | Full reversibility and a change log |
| Immediate red flag | Requires antivirus to be disabled |
| Biggest real-world risk | Pirated tweak tools carrying malware |

## Key takeaways

- The dividing line is the game process. Tools that stay outside it are not something anti-cheat looks at; tools that enter it are.
- Reversibility is the second test. If a tool cannot undo itself, you are making permanent changes you cannot audit.
- Any tool that asks you to disable your antivirus to install has told you what it is.
- Registry cleaners are not dangerous in a ban sense but are a reliable sign a product is selling reassurance rather than performance.
- Cracked or pirated tweak tools are the most common malware vector in this category by a wide margin.

## The one question that answers this

Ask a single question about any optimization tool: does it change your operating system, or does it change your game? Everything else follows from the answer.

**Two categories, very different risk profiles**
| Setting | Recommended | Why |
| --- | --- | --- |
| Changes Windows settings, power plans, GPU driver options, network parameters | Safe with respect to anti-cheat | These run entirely outside the protected game process. Anti-cheat systems have no interest in your power plan, and there is no mechanism by which such a change resembles cheating. |
| Injects DLLs into the game, hooks the renderer, modifies game files or memory | Genuine ban risk | This is behaviourally identical to how cheats work, and anti-cheat systems detect the behaviour rather than the intent. Well-meaning overlay and capture software has been caught by this repeatedly. |
| Requires an unsigned or test-signed kernel driver | Blocked or flagged | Several kernel-level anti-cheat systems refuse to run alongside these, and some vulnerable signed drivers are explicitly blocklisted by Windows itself. |
| Edits configuration files the game does not expose in its own menus | Risky | File integrity checks are standard. Unlocking hidden settings by editing engine .ini files is exactly the pattern anti-cheat is built to find. |

> **The practical rule:** Change your computer, not your game. Every safe optimization in existence lives on the operating system side of that line, and every genuinely risky one crosses it.

## What to verify before you install anything

1. **Check whether it is code signed** - Right-click the installer, Properties, Digital Signatures tab. A valid signature from a named publisher does not guarantee good behaviour, but its absence on a commercial tool is a meaningful warning.
2. **Confirm it does not require disabling antivirus** - This is not a false positive problem that legitimate vendors live with - they get their binaries signed and submitted to vendors for whitelisting. Any instruction to turn off Defender before installing should end the evaluation.
3. **Look for a documented list of what it changes** - You should be able to read what each optimization does before applying it. If the interface is an opaque progress bar, you are being deliberately prevented from evaluating the product.
4. **Confirm there is an undo** - Not just an uninstaller - an undo. Uninstalling a tool that changed forty registry values does not change them back unless the tool was designed to.
5. **Create a restore point yourself** - Do not rely on the tool to do it. Start, 'Create a restore point', System Restore Configure, turn protection on, Create. One minute of work.
6. **Never download it from anywhere but the vendor** - Cracked and repacked tweak tools are the most common malware delivery route in this category. A licence you did not pay for is not free; it is priced in credentials.
7. **Benchmark before and after** - Record average and 1% low FPS in the same scene with the same settings. If the tool cannot demonstrate a difference on your hardware, uninstall it. This also catches tools that do nothing at all.

## Risks people worry about that are not real, and one that is

**Sorting the real concerns from the folklore**
| Setting | Recommended | Why |
| --- | --- | --- |
| Changing my power plan could get me banned | Not a real risk | Power plans are an operating system setting with no relationship to game integrity. No anti-cheat system examines them. |
| GPU control panel overrides could get me banned | Not a real risk | Driver settings are outside the game process. Every professional player configures these. |
| Registry tweaks will break Windows | Mostly overstated | Individually, most gaming registry tweaks are harmless. The real problem is that unlogged bulk changes are impossible to audit or undo later when something does go wrong. |
| Registry cleaners will damage my system | Occasionally true, but mostly pointless | They can break installed software by removing entries they misjudge as orphaned. More importantly they do nothing for performance, so the risk buys you nothing. |
| Optimizers can permanently damage hardware | Not from settings tools | Software that only changes OS settings cannot damage hardware. Overclocking and voltage tools are a different category and do carry that risk. |
| Downloading a cracked tweak tool | This is the real risk | By a wide margin the most common way people in this hobby end up with credential stealers and remote access trojans. The tool works, and so does the payload. |

## Where Frozen Tweaks stands on each of these

We build one of these tools, so it is only fair to hold ourselves to the checklist rather than describing it in the abstract.

- **No injection.** Frozen Tweaks never enters a game process, hooks a renderer, or loads into a protected application.
- **No game file modification.** It does not touch game directories, engine configuration files, or anything an integrity check would examine.
- **Everything logged.** The Tweak Catalog documents what each optimization changes and what it trades off, before you apply it.
- **Everything reversible.** Each applied tweak can be rolled back individually or all at once, and the tool prompts for a system restore point before its first run.
- **No registry cleaner, no RAM booster.** Deliberately absent, because they do not work.
- **Free tier before payment.** You can measure the difference on your own hardware before deciding whether the rest is worth buying.

**Verify it on your own machine** - Download the free tier, benchmark before and after, and check the change log. That is the only evidence that should convince you. [Download the free version](https://frozentweaks.com/purchase)

## Frequently asked questions

### Can FPS boosting software get you banned?

Only if it operates inside the game. Software that injects DLLs, hooks the rendering pipeline, or modifies game files behaves identically to cheat software from an anti-cheat system's perspective, and detection is based on behaviour rather than intent - legitimate overlay and capture tools have been caught this way. Software that only configures Windows, power plans, GPU driver settings and network parameters runs entirely outside the protected process and carries no ban risk.

### Are PC optimizers safe to use with kernel-level anti-cheat?

Settings-level tools are, including alongside Riot Vanguard and the kernel anti-cheat used by modern Call of Duty and Battlefield titles. What those systems object to is process injection, game file tampering, and unsigned or blocklisted kernel drivers. Changing your power mode, GPU driver settings or network configuration is not in any of those categories. Avoid any optimizer that installs its own unsigned driver.

### Will optimization software damage my PC?

Software that only changes operating system settings cannot damage hardware - there is no mechanism for it. The real risks in this category are different: bulk unlogged registry changes you cannot audit or undo later, debloat scripts that break Windows Update or Windows Security, and above all pirated or cracked tweak tools, which are one of the most common malware delivery routes in PC gaming. Overclocking and voltage tools are a separate category that does carry genuine hardware risk.

### Should I disable my antivirus to install an optimizer?

No, and being asked to is the clearest single warning sign available. Legitimate vendors get their binaries code signed and submitted to antivirus vendors for whitelisting, because they know their customers will not and should not turn off protection to install a utility. If the installation instructions begin with disabling Windows Defender, stop there.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/is-pc-optimization-software-safe

---

---
title: "Low-End PC Gaming Optimization: Getting Playable Frame Rates"
description: "What actually works on a weak PC, in order - including the one upgrade that beats every software tweak combined, and honest limits on what tuning can do."
url: https://frozentweaks.com/guides/low-end-pc-gaming-optimization
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Windows & Hardware"
source: Frozen Tweaks (https://frozentweaks.com)
---

# Low-End PC Gaming Optimization: Getting Playable Frame Rates

**Short answer:** On a low-end PC, the order that works is: move the game to an SSD, enable XMP or EXPO, set the Windows power mode to Best performance, prune startup applications, use upscaling at Performance mode, and switch to a game's dedicated low-fidelity renderer where one exists (such as Fortnite's Performance Mode). If you can spend money, an SSD and a second matched memory stick beat any software change.

## At a glance

| | |
| --- | --- |
| Best free change | Upscaling at Performance + lowest effects settings |
| Best cheap upgrade | SATA or NVMe SSD |
| Second best upgrade | Matched second RAM stick for dual channel |
| Common mistake | Disabling the page file |
| Honest limit | Tuning recovers waste; it does not create hardware |

## Key takeaways

- The highest-value change on most low-end machines is not a setting. It is moving from a mechanical drive to an SSD.
- Single-channel memory is extremely common in budget prebuilts and laptops and costs a great deal on integrated graphics. Adding a matched second stick is cheap and dramatic.
- Upscaling at Performance mode is the difference between unplayable and playable on entry-level GPUs, and it is free.
- Some games ship a dedicated low-fidelity renderer rather than just a low preset. Use it - it is a different code path, not a slider.
- Never disable the page file on a system with limited RAM. It causes crashes, not speed.

## What tuning can and cannot do

Software optimization recovers performance that is being wasted. It does not create performance that your hardware never had. On a neglected low-end machine there is often a lot of waste - single-channel memory, a mechanical drive, a power plan parking cores, a dozen startup applications - and recovering it can genuinely double a frame rate. On a low-end machine that is already configured properly, there is very little left.

That distinction matters because it tells you when to stop. If you have done everything on this page and a game is still unplayable, the answer is a different game or different hardware, not another tweak. Anyone selling you a further 50% on top of a tuned system is selling you nothing.

## The order that works

1. **Get the game onto an SSD** - This is the single largest change available on most older machines, and it is not a frame-rate change - it is a stutter change. Mechanical drives cannot stream modern game assets fast enough, which produces hitching that no graphics setting fixes. Even a cheap SATA SSD transforms this. Several 2025-2026 releases now require one outright.
2. **Check whether your memory is running in dual channel** - Task Manager > Performance > Memory shows the channel configuration. Budget prebuilts and laptops very often ship with one stick, and on integrated graphics that halves your memory bandwidth - which is the GPU's bandwidth too. Adding a matched second stick is the cheapest large upgrade in PC gaming.
3. **Enable XMP or EXPO in BIOS** - Free, takes two minutes, and typically worth 5-15% in CPU-bound games. Most systems run memory at the JEDEC fallback speed until you enable the rated profile.
4. **Set the Windows power mode to Best performance** - Settings > System > Power & battery. On a laptop, also set the manufacturer's performance profile and stay plugged in - battery power caps clocks regardless of what Windows says.
5. **Prune startup applications hard** - Task Manager > Startup apps. On a machine with 8 GB of RAM, every resident application is competing for memory you need. This matters far more on low-end systems than on high-end ones.
6. **Turn on upscaling at Performance mode** - DLSS, FSR or XeSS at Performance renders internally at roughly half resolution and reconstructs. On entry-level GPUs this is frequently the difference between unplayable and playable, and it preserves your UI and output resolution in a way that simply lowering resolution does not.
7. **Use a dedicated low-fidelity renderer where one exists** - Fortnite's Performance Mode is the clearest example - it is a separate DirectX 11 render path, not a quality preset, and it commonly doubles frame rate on weak hardware. Check whether the games you play offer something equivalent before grinding through individual sliders.
8. **Lower effects before resolution** - Shadows, volumetrics, post-processing and ambient occlusion first. Resolution last, because a smaller image makes distant enemies physically smaller and you lose more than you gain in a competitive game.

## If you are on integrated graphics

Integrated GPUs share system memory with the CPU, which changes the priorities substantially.

- **Dual channel memory is not optional.** It is the single biggest determinant of integrated GPU performance, because system memory bandwidth is the GPU's bandwidth. A single-stick configuration can cost you 40% or more.
- **Faster memory helps more than it does on a discrete card.** If you are choosing sticks, speed matters here in a way it does not for a desktop with a dedicated GPU.
- **Check the VRAM allocation in BIOS.** Some systems allow you to reserve more system memory for the integrated GPU. More is not always better - you are taking it from the system - but a very low allocation can cause problems in modern titles.
- **Close everything.** With shared memory, background applications compete with your GPU directly rather than just with your CPU.
- **Set expectations by generation.** Recent AMD and Intel integrated graphics handle competitive shooters at 1080p low settings. Integrated graphics from before roughly 2020 generally do not, regardless of tuning.

## Common low-end mistakes

**Advice that makes a weak PC worse**
| Setting | Recommended | Why |
| --- | --- | --- |
| Disabling the page file to save RAM | Causes crashes | This is the most damaging piece of low-end advice in circulation. Modern games and Windows both assume a page file exists. On a system with limited RAM, removing it guarantees out-of-memory crashes rather than speed. |
| RAM cleaner utilities | Makes things slower | They force Windows to discard cached data it is about to need again, so it re-reads from disk. On a machine with a mechanical drive this is particularly punishing. |
| Aggressive debloat scripts | High risk, low reward | The components removed were not consuming CPU while you played. The broken Windows Update or Microsoft Store afterwards is real. |
| Setting game priority to Realtime | Causes stutter | Starves audio, input and driver threads. High is the ceiling if you adjust priority at all. |
| Overclocking a thermally limited laptop | No gain | If the machine is already throttling, raising the clock ceiling changes nothing. Clean the fans and improve airflow instead; on an older machine, repasting often recovers more than any tweak. |
| Filling the drive to 98% | Slows everything | SSDs slow substantially when nearly full, and a full mechanical drive fragments badly. Keep 15-20% free. |

**Free tier is aimed at exactly this** - The free Frozen Tweaks tier applies the power, startup and Windows-side configuration in this guide - the changes that matter most on modest hardware - and rolls back on demand. [Download the free version](https://frozentweaks.com/purchase)

## Frequently asked questions

### How can I boost FPS on a low-end PC for free?

In order: confirm the game is on an SSD rather than a mechanical drive, enable XMP or EXPO in BIOS, set the Windows power mode to Best performance, prune startup applications, turn on DLSS, FSR or XeSS at Performance mode, and use a game's dedicated low-fidelity renderer if it has one - Fortnite's Performance Mode is the clearest example. Lower effects settings before you lower resolution.

### Does adding more RAM increase FPS?

Going from single-channel to dual-channel almost always does, sometimes dramatically - and budget prebuilts and laptops very frequently ship with one stick. On integrated graphics the effect is largest, because system memory bandwidth is also the GPU's bandwidth. Going from 16 GB to 32 GB on a machine that was not running out of memory generally does very little. Check your channel configuration in Task Manager before buying anything.

### Should I disable the page file to speed up my PC?

No. This is the most harmful piece of low-end optimization advice in circulation. Windows and modern games both assume a page file exists, and on a system with limited RAM, removing it produces out-of-memory crashes and application failures rather than additional speed. Leave it on the system-managed default.

### Can I play modern games on integrated graphics?

Recent AMD and Intel integrated graphics handle competitive shooters like Valorant, CS2 and Fortnite in Performance Mode at 1080p on low settings. Anything from before roughly 2020 generally will not, regardless of tuning. The single most important factor is dual-channel memory - a one-stick configuration can cost 40% or more on integrated graphics, because the GPU is using system memory bandwidth.

### What is the best upgrade for an old gaming PC?

An SSD, if the machine still has a mechanical drive - it transforms stutter and load times, and several current releases require one. After that, a matched second memory stick to get into dual channel, which is cheap and often overlooked. A GPU upgrade is usually third, because it is the most expensive and is frequently held back by the other two on an older system.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/low-end-pc-gaming-optimization

---

---
title: "Stretched Resolution: How It Works and Whether It Helps"
description: "How to set up stretched resolution on any GPU, what it actually does to your field of view, and an honest look at whether it makes you aim better."
url: https://frozentweaks.com/guides/stretched-resolution-guide
author: Frost Live, Founder of Frozen Tweaks
published: 2026-08-29
updated: 2026-08-29
category: "Game Guides"
source: Frozen Tweaks (https://frozentweaks.com)
---

# Stretched Resolution: How It Works and Whether It Helps

**Short answer:** Stretched resolution means rendering at a narrower aspect ratio such as 4:3 and stretching it to fill a 16:9 display, which makes player models appear wider and can raise FPS by lowering the render resolution. The trade is real: you lose horizontal field of view, so you see less of the map. Setting it up requires a custom resolution plus GPU scaling set to full-panel in your driver.

## At a glance

| | |
| --- | --- |
| What it does | Renders 4:3 or similar, stretches to fill 16:9 |
| Upside | Wider player models, higher FPS from lower render resolution |
| Downside | Reduced horizontal field of view |
| Requires | Custom resolution + GPU scaling set to full panel |
| Free tool | FrostRes - automates both steps on any GPU |

## Quick setup

1. **Create the custom resolution** - NVIDIA Control Panel > Change resolution > Customize, AMD Adrenalin > Display > Custom Resolutions, or Intel Graphics Command Center > Display > Custom Resolutions. 1280x960 is the most common 4:3 choice.
2. **Turn on GPU scaling** - NVIDIA: Adjust desktop size and position, Scaling mode Full-screen, Perform scaling on GPU. AMD: enable GPU Scaling with Scaling Mode set to Full Panel. Intel: set Scale to stretch to full screen.
3. **Tick the override option** - On NVIDIA, 'Override the scaling mode set by games and programs'. Without this step you get black bars instead of a stretched image, which is the most common failure people hit.
4. **Select the resolution in game and use exclusive fullscreen** - Borderless windowed bypasses GPU scaling entirely, so the stretch will not apply.
5. **Check the monitor's own aspect ratio setting** - If bars persist, the display is applying its own scaling over the top. That setting lives in the monitor's on-screen menu, not in Windows.
6. **Or let FrostRes do all of it** - It creates the resolution, applies the correct scaling override for your GPU vendor, manages the Valorant config, and restores your native resolution when you exit. Free, no account required.

## Key takeaways

- Stretched resolution widens player models horizontally and removes horizontal field of view. Both effects are real and they pull in opposite directions.
- The FPS gain comes from the lower render resolution, not from the stretching itself.
- It requires two things: a custom resolution the display accepts, and GPU scaling set to full-panel with the override enabled.
- Whether it helps you aim is genuinely subjective. Professional players are split, and there is no consensus.
- Some games and configurations do not permit it, and forcing it through unsupported methods is not worth the risk.

## What stretched resolution actually does

Your monitor is almost certainly 16:9. Stretched resolution means telling the game to render a narrower aspect ratio - most commonly 4:3, at something like 1280x960 - and then telling your GPU to stretch that narrower image horizontally until it fills the whole panel.

Two things happen as a result, and they are frequently discussed as if only the first exists.

- **Player models get wider.** Everything is stretched horizontally, so a target that was 30 pixels wide becomes 40. A wider target is easier to hit, particularly with flick aim.
- **Your horizontal field of view shrinks.** You are rendering a 4:3 slice of the world. The parts of the scene that would have been at the left and right edges of a 16:9 frame are simply not drawn. You see less.

> **The honest framing:** Stretched resolution trades map awareness for target size. Whether that is a good trade depends on how you play, and there is no objectively correct answer. Professional players in both Valorant and CS2 are split on it.

## Does it increase FPS?

Usually yes, but not because of the stretching. The gain comes from the lower render resolution: 1280x960 is about 1.2 million pixels against 1920x1080's 2.1 million, so if you are GPU-bound you are doing roughly 40% less pixel work.

The important caveat is that the games where stretched resolution is most popular - CS2 and Valorant - are typically CPU-bound rather than GPU-bound. In those titles the frame-rate gain is often small or nonexistent, and the actual reason to use stretched res is the aspect ratio, not the frames. Check your GPU utilisation before assuming this is a performance change.

## Setting it up manually

Two steps in every case: create the resolution, then force the GPU to scale it to the full panel. If you skip the second step you get black bars instead of a stretched image, which is the most common failure people hit.

### NVIDIA

1. NVIDIA Control Panel > Change resolution > Customize > Create Custom Resolution. Add your target resolution (for example 1280x960) at your monitor's refresh rate, and test it.
2. NVIDIA Control Panel > Adjust desktop size and position. Set Scaling mode to Full-screen, and Perform scaling on to GPU.
3. Tick 'Override the scaling mode set by games and programs'. This step is what actually produces the stretch.
4. Select the custom resolution in the game's video settings, and set the game to exclusive fullscreen.

### AMD

1. AMD Adrenalin > Settings > Display > Custom Resolutions. Create your target resolution and apply it.
2. On the same Display page, enable GPU Scaling.
3. Set Scaling Mode to Full Panel.
4. Select the resolution in game and use exclusive fullscreen.

### Intel

1. Intel Graphics Command Center > Display > Custom Resolutions. Add the resolution you want.
2. On the Display > General page, set Scale to 'Stretch to full screen' or 'Maintain display scaling', depending on your driver version.
3. Select the resolution in game and use exclusive fullscreen.

> **Two things that break this:** Running the game in borderless windowed mode bypasses GPU scaling entirely and you will get an unstretched image. And some monitors apply their own scaling that overrides the GPU's - check the aspect ratio setting in your monitor's on-screen menu if the image is not filling the panel.

## Doing it automatically with FrostRes

The manual process is tedious, differs by GPU vendor, breaks after driver updates, and has to be undone every time you want your desktop back at native resolution. That is why we built FrostRes and made it free.

- Creates the custom resolution for you on NVIDIA, AMD or Intel without you needing to know which control panel you are in.
- Applies the correct GPU scaling override for your vendor automatically.
- Manages Valorant configuration so the resolution is actually picked up by the game.
- Restores your native resolution automatically when you exit the game, so your desktop is not left stretched.
- Free, with no account required.

**FrostRes is free** - Custom and stretched resolutions on any GPU, with automatic restore on exit. No account, no payment. [Get FrostRes free](https://frozentweaks.com/frost-res)

## Should you actually use it?

An honest answer rather than a recommendation, because this is a preference and anyone telling you otherwise is overstating the evidence.

**Who it tends to suit**
| Setting | Recommended | Why |
| --- | --- | --- |
| You play a lot of Valorant or CS2 and rely on flick aim | Worth trying | Wider models help most when your aim style is fast and corrective rather than tracking. |
| You are GPU-bound at native resolution | Worth trying | You get a genuine frame-rate gain on top of the aspect ratio change. |
| You play games with a lot of wide-angle information | Probably not | Battle royales and large-map shooters punish reduced peripheral vision more than they reward wider models. |
| You are already comfortable at native | Probably not | The adjustment period is real, and changing aspect ratio disrupts muscle memory for a while. If nothing is wrong, do not fix it. |
| You are switching because a professional player uses it | Be careful | Professionals are split roughly down the middle on this, which is a strong signal that it is preference rather than an advantage. |

## Frequently asked questions

### Does stretched resolution give more FPS?

Usually, but the gain comes from the lower render resolution rather than the stretching. Rendering 1280x960 instead of 1920x1080 is about 40% less pixel work, so a GPU-bound system gains meaningfully. However, the games where stretched res is most popular - CS2 and Valorant - are typically CPU-bound, and in those titles the frame-rate gain is often small. Check your GPU utilisation before assuming it is a performance change.

### Does stretched resolution make it easier to hit shots?

It makes player models wider, which some players find easier to hit, especially with flick aim. It also removes horizontal field of view, so you see less of the map and get less warning about wide angles. Professional players in both Valorant and CS2 are split roughly down the middle on it, which is the strongest available evidence that it is a preference rather than a straightforward advantage.

### Why is my stretched resolution showing black bars?

Because GPU scaling is not applied. Creating the custom resolution is only half the setup - you also need scaling set to full-screen or full-panel with the override enabled in your GPU control panel. Two other common causes: running the game in borderless windowed mode, which bypasses GPU scaling entirely, and the monitor applying its own aspect ratio setting through its on-screen menu.

### Is stretched resolution allowed by anti-cheat?

Yes. Custom resolutions and GPU scaling are display driver settings that operate entirely outside the game process, and they are used openly by professional players in officially sanctioned competition. What is not safe is editing game files to force a resolution the game does not offer - that crosses into file modification, which is a different category entirely.

### What is the best stretched resolution for Valorant?

1280x960 stretched to your panel is the most common choice, as it gives a true 4:3 ratio at a render resolution most systems handle easily. 1440x1080 is the next most popular and is a reasonable middle ground if you want less pixel-quality loss. There is no objectively best option - it depends on your monitor, your GPU headroom and how much horizontal field of view you are willing to give up.

---
Written by Frost Live, founder of Frozen Tweaks. Canonical version: https://frozentweaks.com/guides/stretched-resolution-guide