A choppy shift ruins the joke, so this Scam With Your Friends low fps fix targets the real culprits: heavy shadows, uncapped background apps, and the voice model chewing your CPU. Apply these tweaks and your calls run smooth again.
Why Your Frame Rate Tanks During Calls
The biggest surprise for new players is that the frame drops rarely come from the 3D office itself. The office scene is lightweight — a handful of props, a few callers, and simple lighting. What actually drags your frame rate down is the text-to-speech voice engine running on the same CPU threads as the game loop, plus whatever else you left open in the background. When a caller starts talking, the engine synthesizes audio in real time, and on weaker machines that spike eats into your render budget.
Three pressure points stand out: the TTS voice engine spiking a single CPU core every time a caller begins a line, dynamic shadow and reflection passes that scale poorly on mid-range GPUs like the GTX 1650 or RX 6400, and background bloat from browsers, launchers, and recording software all fighting for the same threads. On a quad-core chip, the voice synthesis pass alone can consume 25–40% of one core mid-call, which is why the stutter hits hardest right as dialogue starts rather than during idle office exploration.
-
Voice synthesis spikes — every new caller triggers a generation pass that briefly hammers the CPU
-
Shadow and reflection quality — the office uses dynamic shadows that scale badly on mid-range GPUs
-
Background bloat — browsers, launchers, and recording software competing for the same cores
Understanding this matters because most generic "turn everything to low" advice only fixes one of the three. If your voice engine is the bottleneck, dropping texture quality does almost nothing. If your GPU is the bottleneck, disabling voices won't help either. You need to identify which resource is actually maxed out before you touch a single slider.
A quick way to check: open Task Manager (Ctrl+Shift+Esc), play for five minutes, and watch whether CPU or GPU sits pinned near 100%. That single observation tells you which half of this guide to prioritize. Players on older quad-core chips almost always land on the CPU side, while anyone with a modern six-core CPU but an entry-level GPU lands on the graphics side.
There's also a memory angle worth checking before you blame the GPU. If your system is running low on RAM, Windows starts paging to disk mid-call, which produces the exact stutter pattern people describe as "lag." The high memory usage fix guide walks through trimming that footprint if Task Manager shows your RAM near the ceiling.
The Fastest Graphics Settings for Higher FPS
If your GPU is the bottleneck, this is where you win the most frames for the least visual pain. The office art style is deliberately flat and cartoonish, so several "high" settings add almost nothing to the look while costing a surprising amount of performance. Start here and work down until your frame counter stabilizes.
| Setting | Recommended Value | Why It Matters |
|---|---|---|
| Shadow Quality | Low | Biggest single GPU saving; flat art hides the loss |
| Reflections | Off | Screen-space reflections are expensive and barely visible |
| Anti-Aliasing | FXAA | Cheap edge smoothing; MSAA costs far more |
| Texture Quality | Medium | High textures rarely change the cartoon look |
| View Distance | Medium | Office is small; far draw distance is wasted |
| V-Sync | Off | Adds input lag; cap frames in driver instead |
| Resolution Scale | 100% | Drop to 90% only if you still stutter |
The Shadow Quality slider is the one to change first. In practice, moving it from High to Low recovers the largest chunk of frames with the smallest visual cost, because the office lighting is already soft and stylized. Reflections are the second-biggest offender — turning them off entirely is barely noticeable during a call.
If you're still short after these changes, drop Resolution Scale to 90%. That renders the scene slightly under your monitor's native resolution and upscales it, which is far cheaper than lowering the output resolution itself. Most players can't tell the difference at 1080p, and it buys a meaningful buffer on integrated graphics.
One caution: don't stack every setting at the absolute minimum at once. Change one slider, play a full call, then change the next. That way you learn which setting your specific hardware actually hates, and you avoid turning the game into a blurry mess for no reason. The Steam Deck optimization guide covers a similar one-at-a-time approach for handheld players, and the logic transfers directly to desktops.
Fixing Stutter and Micro-Freezes Mid-Call
Stutter is different from a low average frame rate. Your counter might read a healthy 60 fps, yet the game hitches for a quarter-second every time a caller speaks. That pattern almost always points to frame-time spikes, not raw throughput, and the fixes are different from the graphics tweaks above.
| Stutter Symptom | Likely Cause | Fix |
|---|---|---|
| Hitch when caller starts talking | Voice synthesis on main thread | Lower voice quality / preload voices |
| Regular rhythm hitches | Background app polling | Close browsers and launchers |
| Hitch on scene transitions | Shader compilation | Let the game warm up, then replay |
| Random long freezes | Disk paging from low RAM | Free up memory, close tabs |
| Stutter only in windowed mode | Compositor overhead | Switch to exclusive fullscreen |
The voice synthesis hitch is the signature stutter of this game. Because the engine generates caller audio on demand, the first line from a new caller can momentarily starve the render thread. Lowering voice quality in the audio settings reduces how much work each generation pass costs, and preloading voices (if the option is available in your build) removes the on-demand spike entirely.
Background apps are the second silent killer. A single browser with a dozen tabs can hold several CPU cores busy with JavaScript timers, and those cores are exactly the ones the game wants. Closing your browser, Discord overlay, and any recording software before a session is one of the highest-value habits you can build.
If your stutter has a regular rhythm — a hitch every few seconds like clockwork — suspect a background process polling on a timer rather than the game itself. Cloud sync clients, RGB software, and antivirus scans all do this. Pausing them for the duration of a session often clears the rhythm entirely, and it costs you nothing but a few clicks.
Stopping Crashes on Startup and Speech Errors
Crashes are a separate beast from performance, and they usually happen before you even reach the office. The two most common reports are a crash on startup and a speech startup crash where the game dies the moment it tries to initialize the voice engine. Both tend to trace back to the same handful of causes.
| Crash Type | Common Trigger | First Fix to Try |
|---|---|---|
| Crash on startup | Corrupted config file | Delete local config, verify files |
| Speech startup crash | Missing voice model files | Re-download voice assets |
| Crash after a few minutes | Overheating / driver timeout | Update GPU driver, check temps |
| Crash on launch only | Outdated DirectX / VC++ | Install latest redistributables |
| Random crash mid-call | Unstable overclock | Reset to stock clocks |
For a crash on startup, the fastest fix is to verify your game files through Steam, which replaces any corrupted or missing assets. If that doesn't work, delete the local configuration file so the game regenerates a clean one on next launch — a corrupted config is a surprisingly common culprit after a patch.
The speech startup crash is more specific: the game loads its voice model at launch, and if those files are incomplete or the download was interrupted, initialization fails hard. Re-downloading the voice assets usually resolves it. If you've been experimenting with voice settings, reverting to defaults before relaunching can also get you past a bad configuration.
Driver timeouts deserve a mention because they masquerade as crashes. If your screen goes black and the game closes with no error, your GPU driver may have reset itself under load. Updating to the latest driver and, if you overclock, returning to stock clocks resolves the majority of these cases. In practice, the game is sensitive to unstable memory overclocks in particular.
Squeezing Out Extra Frames With System Tweaks
Once the in-game settings are dialed in, the remaining gains come from your system. These tweaks are free, reversible, and often worth another 10–20% on weaker hardware, since Scam With Your Friends leans hard on CPU-side physics for its co-op prop chaos — the ragdolls, grab physics, and voice-driven interactions all compete for the same threads your OS is juggling. On a mid-range rig, background processes like browser tabs, launchers, and RGB software can eat 15–25% of a single core, which shows up as micro-stutter exactly when four players pile into one room. None of this touches your save data or install, and every change stacks cleanly with the graphics changes above.
-
Set the game to High Priority — open Task Manager, right-click the game process, and raise its priority so Windows schedules it first
-
Enable Game Mode — Windows Game Mode reduces background interruptions during play
-
Cap your frame rate — a stable 60 beats a fluctuating 90 for perceived smoothness
-
Update your GPU driver — new drivers frequently include fixes for specific titles
-
Disable the Discord overlay — it hooks into the render pipeline and costs frames
-
Move the install to an SSD — faster asset loading reduces transition hitches
The frame rate cap is underrated. Uncapped frames make your GPU work harder than it needs to, which raises temperatures and can trigger thermal throttling that produces worse stutter than a modest cap would. Setting a cap slightly below your average — say 60 if you hover around 70 — smooths out the dips.
If you play with others, some of what feels like low fps is actually network lag, which no graphics setting will fix. The multiplayer lag fix guide separates connection problems from rendering problems so you don't waste time tuning the wrong thing.
Matching Fixes to Your Hardware Tier
Not every machine needs every fix, and applying a high-end tweak to a low-end rig can actually make things worse — dropping Shadows to Low on a strong GPU gains nothing while costing you visual clarity. Use the table below to jump straight to the changes that match your actual bottleneck, then verify with a five-minute play session before moving on. If the stutter returns mid-round, revert that single change rather than stacking more edits on top of it.
| Your Hardware | Primary Bottleneck | Do This First |
|---|---|---|
| Integrated graphics | GPU | Shadows Low, Reflections Off, Scale 90% |
| Older quad-core CPU | CPU / voice engine | Lower voice quality, close background apps |
| 8 GB RAM | Memory paging | Close tabs, raise page file, cap frames |
| Modern GPU, mid CPU | Voice synthesis | Preload voices, set High Priority |
| Laptop on battery | Power throttling | Plug in, set High Performance power plan |
Laptop players should always plug in before tuning anything. On battery, most laptops throttle the CPU and GPU aggressively, and no in-game slider can overcome a power limit. Switching to a High Performance power plan while plugged in often recovers more frames than any graphics change.
If you're on a low-end PC and still struggling after all of this, the honest answer may be that the voice engine is simply too heavy for your hardware, and reducing voice quality or count is the only lever left. That's not a failure of your tuning — it's the nature of running real-time speech synthesis on a machine that wasn't built for it.
Frequently Asked Questions
What is the single best setting to change for a Scam With Your Friends low fps fix?
Lower Shadow Quality to Low first. It delivers the largest frame gain with the smallest visual cost because the office art is flat and stylized. If you still stutter, turn Reflections off and drop Resolution Scale to 90% before touching anything else.
Why does my game stutter only when callers start talking?
That's the voice engine synthesizing audio on demand, which briefly competes with the render thread. Lowering voice quality or preloading voices reduces the spike. If the hitch has a regular rhythm instead, a background app is polling on a timer — close browsers and launchers.
How do I fix a crash on startup or a speech startup crash?
Verify your game files through Steam to replace corrupted assets, then delete the local config so it regenerates cleanly. For a speech startup crash specifically, re-download the voice model files, since an interrupted download leaves initialization broken. Updating your GPU driver covers the remaining cases.
Will these tweaks work on a low-end PC or laptop?
Yes, and they matter most there. Plug in your laptop, set a High Performance power plan, and apply the integrated-graphics row from the hardware table. On very weak machines, reducing voice quality is the final lever, since real-time speech synthesis is the heaviest load.
Does capping my frame rate actually improve smoothness?
Often, yes. An uncapped frame rate pushes your GPU harder, raising temperatures and risking thermal throttling that causes worse stutter than a modest cap. Setting a cap slightly below your average frame rate smooths out the dips and keeps frame times consistent.
Getting smooth calls comes down to three moves: identify whether your CPU or GPU is the bottleneck, apply the matching fixes from the tables above, and change one setting at a time so you know what actually worked. The graphics sliders handle GPU pressure, closing background apps and lowering voice quality handle CPU pressure, and the startup crash fixes get you into the office in the first place. Work through them in order, verify each change with a real call, and your shift will run as smoothly as the scam itself.