If Marvel’s Spider-Man: Miles Morales stutters, drops below 60 FPS, or crashes on PC, start by disabling ray tracing, updating your GPU driver with a clean install, verifying the Steam files, and using DLSS or FSR 2 at a sensible resolution. Then cap the frame rate to a number your system can hold consistently. Those steps fix the most common problems without turning New York into a blurry mess.
The PC port from Nixxes is far more flexible than the PlayStation version, but that flexibility exposes every weak point in a system. Fast traversal streams buildings and traffic constantly, ray-traced reflections hammer GPU memory, and shader compilation can produce nasty one-off hitches. Here’s how to separate normal first-run behavior from a genuine configuration problem.
Check Your Hardware Before Chasing Settings
Miles Morales has a relatively modest minimum target, but the recommended specification is the more realistic starting point for a stable 1080p experience. The game uses a lot of VRAM when texture quality, resolution, and ray tracing are pushed together. A graphics card that technically launches the game can still stutter when it runs out of memory during high-speed traversal.
| Target | Hardware Baseline | Practical Expectation | Storage Note |
|---|---|---|---|
| Minimum | GTX 950 or Radeon RX 470, 8GB RAM | 720p to 1080p Low, around 30 FPS | SSD strongly preferred |
| Recommended | GTX 1060 6GB or RX 580, 16GB RAM | 1080p Medium, around 60 FPS with upscaling | Use an SSD for traversal streaming |
| High-quality target | RTX 3060 or RX 6600 XT, 16GB RAM | 1080p High near 60 FPS without RT | Keep at least 20GB free |
| Ray-tracing target | RTX 3070-class GPU or better | 1440p with upscaling and selective RT | 16GB VRAM is comfortable for max settings |
These are not guarantees. CPU-heavy areas, especially during fast movement through dense neighborhoods, can cause dips even when your GPU is below 100 percent. Put the game on an SSD, close browsers and recording tools, and make sure Windows is using the dedicated GPU rather than integrated graphics. If your PC struggles with several games, our PC crash and FPS troubleshooting guide covers the same system-level checks.
Use This Stable Graphics Preset First
Don’t change fifteen options at once. Load a save in a busy part of Manhattan, swing for two minutes, and change one setting at a time. The preset below favors consistent frame times over flashy screenshot quality. Consistency matters more than a peak FPS number because traversal stutter is felt as a sudden hitch, not a slow average.
| Setting | Recommended Value | FPS Impact | Visual Trade-off |
|---|---|---|---|
| Display mode | Exclusive Fullscreen | Low | Usually gives the cleanest presentation and input response |
| Resolution | Native, or 90% render scale | Medium | 90% is a useful compromise on weaker GPUs |
| Upscaling | DLSS Quality, FSR 2 Quality, or XeSS Quality | Large gain | Quality modes retain much more detail than Performance |
| Texture quality | High if VRAM allows; Medium under 6GB | Medium | Mostly affects surface detail and memory use |
| Shadow quality | Medium | Medium | Reduces expensive dynamic shadow work |
| Traffic and crowd density | Medium | CPU-dependent | Fewer distant cars and pedestrians during traversal |
| Hair quality | Medium | Low to medium | Important in close-ups, less visible while swinging |
| Ray-traced reflections | Off initially | Very large | Reflections become screen-space or rasterized |
| Ray-traced shadows and geometry | Off initially | Large | Keep them off until the baseline is stable |
| Motion blur | 0 to 3 | Negligible | Personal preference; lower values improve clarity |
DLSS is the best first choice on RTX cards. FSR 2 Quality is a solid alternative on Radeon and GeForce GTX hardware, while XeSS can help on compatible Intel GPUs. Avoid Performance mode at 1080p unless you absolutely need it; its lower internal resolution can make buildings and web lines shimmer. For a 60Hz display, cap the game at 60 FPS. For 120Hz or 144Hz screens, try 90 or 120 only if your frame-time graph stays flat.
Stop Stuttering During Web-Swinging
The most recognizable Miles Morales PC stutter happens when the game streams new city geometry while you swing rapidly across Harlem or the Upper East Side. A brief hitch during the first traversal of a district can be shader or asset caching. Repeated stutters on every pass usually mean the storage drive, VRAM budget, background software, or CPU is being overwhelmed.
Build a clean baseline
- Install the latest Game Ready or Adrenalin driver for your GPU. If the problem began immediately after a driver update, test the previous stable release instead.
- Restart the PC after the driver installation. Don’t rely on sleep mode, especially after several game launches.
- Disable Steam Overlay, Discord Overlay, GeForce Experience recording, Xbox Game Bar, and MSI Afterburner’s overlay one by one. Overlays hook into the rendering pipeline and can create hitching or crashes.
- Set Windows power mode to Best performance while testing, and close browsers playing video in the background.
- Use a frame limiter. A locked 50 or 60 FPS feels substantially better than a volatile 45-75 FPS range.
Watch GPU usage, VRAM, system RAM, CPU thread load, and frame time with an overlay. If VRAM is full and the graph spikes during traversal, lower textures, reflections, and resolution before lowering effects that barely affect memory. If one or two CPU threads are pinned while the GPU is underused, reduce crowd density and traffic first. Those settings affect simulation work, not just visuals.
Shader compilation can also look like broken performance. Let the game sit at the main menu after a driver change, then play through the same area twice. If the second run is dramatically smoother, the first pass was likely cache-related. Don’t repeatedly clear shader caches unless you’re troubleshooting a corruption problem; doing so forces the game to rebuild them.
Fix Low FPS Without Making Miles Look Muddy
Start by identifying whether the GPU or CPU is the limit. Lower resolution and see what happens. If FPS rises sharply, the GPU is the bottleneck. If it barely moves, CPU simulation, streaming, or a frame cap is responsible. This simple test prevents the classic mistake of dropping every visual setting when the real issue is crowd simulation.
For GPU-limited systems, switch ray-traced reflections off first. They are gorgeous across wet streets and glass towers, but they can cost more than several ordinary quality settings combined. Next, use DLSS or FSR 2 Quality, then reduce shadow quality from High to Medium. Keep textures as high as your VRAM permits because texture detail usually costs less performance than resolution or ray tracing.
For CPU-limited systems, lower traffic and crowd density, close background applications, and check that the processor isn’t thermal throttling. High temperatures can reduce clock speed after several minutes, making the opening benchmark look fine while a long patrol becomes stuttery. A steady 45 FPS cap may be the right answer on an older six-core CPU; it will feel better than unstable 60 FPS targets.
| Problem Pattern | Likely Bottleneck | First Change | What to Keep High |
|---|---|---|---|
| GPU at 95-99%, VRAM near full | Graphics card or VRAM | Disable RT, use Quality upscaling | Textures, if memory remains available |
| GPU below 80%, one CPU thread maxed | CPU simulation or streaming | Lower crowd and traffic density | Texture quality and anisotropic detail |
| Sudden spikes when entering new blocks | Asset streaming or shader cache | Move the game to SSD and replay the route | Effects after confirming stability |
| Stable FPS but unpleasant motion | Frame pacing or sync | Use a fixed cap and test V-Sync | Resolution and image quality |
Stop Crashes, Freezes, and Black Screens
Crashes after changing graphics settings often come from an unstable GPU overclock, corrupted shader data, or a driver conflict rather than the game itself. Return the GPU and CPU to stock clocks before testing. Undervolts that work in other games can still fail during Miles Morales’ rapid streaming and heavy RT workloads.
Run the repair checklist in this order
- Open Steam, right-click the game, choose Properties, Installed Files, and Verify integrity of game files. Let the process finish completely.
- Update Windows and install the current GPU driver using the clean-install option. If normal installation fails, use Display Driver Uninstaller in Safe Mode, then install the driver fresh.
- Delete or rename the game’s shader cache only after verifying files and drivers. The next launch may stutter while the cache rebuilds.
- Disable every overlay and monitoring hook, including Steam Input experiments, third-party reshade injectors, and aggressive antivirus game modes.
- Remove custom launch options. Test the unmodified executable before adding commands found in forum posts.
- Check Event Viewer after a crash. “Display driver stopped responding” points toward the driver, heat, power, or an unstable clock; an application fault points more toward files or software conflicts.
If the game crashes only when ray tracing is enabled, leave RT disabled and test the rest of the profile. If it crashes after ten or twenty minutes, monitor GPU temperature, hotspot temperature, CPU package temperature, and power delivery. A black screen followed by a driver reset is not fixed by lowering motion blur; it needs a stability check. Nixxes’ official support portal is the right place to report repeatable failures, while the Steam page for Miles Morales lists the current platform information.
Fine-Tune Frame Pacing After the Fix
Once the game stops crashing, tune for frame time rather than a screenshot benchmark. A locked 60 FPS means each frame has about 16.67 milliseconds to render. At 30 FPS, the budget is 33.33ms; at 90 FPS, it is only 11.11ms. A single 40ms spike feels like a hitch even if your average counter says 90.
Use your monitor’s refresh rate as the ceiling. With G-Sync or FreeSync, cap a few frames below the maximum refresh rate using the driver or an in-game limiter. For a 144Hz display, 141 FPS is a common starting point, but only use it if your hardware can sustain it while swinging through dense areas. Otherwise, 90 or 72 FPS can produce a cleaner, quieter experience.
V-Sync deserves testing rather than blind loyalty. Adaptive sync with an external cap often delivers the smoothest result. If you see tearing, enable V-Sync in the driver or game and compare input latency. The best setting depends on your display, but the goal is simple: no constant oscillation between an unreachable target and a lower fallback.
Finally, test the same route after every major change: launch from a save near a busy street, swing across several blocks, enter a building, and fight a group of enemies. That route stresses streaming, combat effects, crowds, and reflections far more effectively than standing on a quiet rooftop.
Keep the Port Healthy After Updates
New GPU drivers and game patches can change shader behavior, upscaling quality, or ray-tracing performance. Save a screenshot of your working settings before updating, and don’t clear caches on every patch unless the game begins hitching repeatedly. If a patch introduces a fresh issue, document your GPU model, driver version, resolution, upscaler, RT state, and whether the game is installed on an SSD before reporting it.
For broader PC troubleshooting, Steamoz’s guides on crashes and low FPS and high-FPS graphics settings are useful companions. You can also check PlayStation’s official Miles Morales page for game information.
The winning setup is rarely “everything on Ultra.” It’s a stable frame cap, Quality-level upscaling, sensible textures, ray tracing only when the GPU has room, and a clean software environment. Get those fundamentals right and Miles’ most demanding activity—launching from a rooftop and tearing across Manhattan—becomes the smooth showcase it was meant to be.