Elden Ring Gameplay Speedrun Pc Ultra Graphics

Speedrunning Elden Ring on PC With Ultra Graphics Isn't Worth What You Think

I've been running Elden Ring tools for a few years now, mostly for personal challenge splits and occasional leaderboard submissions. Someone recently asked me about pairing ultra graphics with a speedrun, and honestly, it comes up more often than I'd like. People see the performance mode discussion and assume they can just crank everything up and run faster. That's not how this works. The short answer is that you technically can run Elden Ring at ultra graphics while attempting a speedrun on PC, but you should almost certainly not do it. The game has a dedicated Performance Mode that exists specifically because ray tracing and high-resolution textures create input latency that actively hurts your times. I went through a phase where I thought I could optimize my machine enough to have both, and I wasted three weeks learning exactly why that's a bad idea. Ultra settings push the GPU hard, which introduces frame time variance even when your average FPS looks fine. A 144Hz display with consistent 140fps still means variable frame delivery during heavy scenes. Input lag stacks up. For a speedrun where frame-perfect movement matters across 200+ encounters, that variance is punishing. My best no-glitch run dropped by over four minutes the moment I switched from Performance Mode to Ultra and enabled ray tracing. Not a rounding error.

How Speedrunning Actually Works in This Game

Elden Ring speedruns fall into two broad categories: Any% with glitches and Any% without. The current world records are all glitch-assisted because the game's collision system and memory layout have enough exploitable behavior that skipping massive portions of the map becomes viable. The top route uses sequence breaks that involve hitting invisible walls at precise angles, manipulating enemy pathing with item drops, and using hitbox tricks to bypass bosses entirely. The game uses a frame-accurate physics and AI system, meaning input timing matters down to the individual frame. A 16ms input delay from GPU post-processing is measurable at the split time level. That's roughly a third of a second per 16.6ms, accumulated across hundreds of inputs. It compounds. I learned this the hard way when my input tester showed a consistent 8-12ms delay in menu navigation with ultra settings active versus performance mode, which runs at 2-4ms under the same conditions on the same hardware.

What Ultra Graphics Actually Changes in Practice

Enabling ultra on Elden Ring PC primarily affects three things that matter for speedrunning: texture resolution, ray-traced reflections, and post-processing bloom. The base rendering is still the same game code. Pathfinding, collision detection, and input handling don't change. But the display pipeline adds latency through several layers of anti-aliasing and upscaling. If you're running DLSS or FSR, you're introducing an additional processing step between your frame render and the display. Even at the quality preset, there's a measurable delay. On my setup—a 4090 with a 360Hz monitor—Performance Mode gave me input-to-display latency around 6-8ms. Ultra with DLAA pushed that to 14-18ms. That's the difference between landing a dodgeroll perfectly and arriving half a frame late into a boss attack window. There's also a subtler issue. Ultra textures increase VRAM usage significantly. When the game streams textures mid-fight and VRAM fills up, it starts swapping to system memory. This causes micro-stutters that are invisible to most players but devastating for frame-perfect inputs. I encountered this during a practice session where I hit a stutter exactly at the Radahn festival entrance—a section I had run dozens of times without issue. The stutter cost me a reset and about twenty minutes of practice time before I figured out what was happening.

The Workaround I Used When I Couldn't Let Go

For a while, I tried running ultra textures with ray tracing disabled, DLSS in performance mode, and a specific config file modification that reduced post-processing overhead. The config change involved editing the INI files in the game directory to cap the motion blur intensity and disable certain depth-of-field calculations. This cut the input latency from 18ms back down to about 10ms, which was closer to acceptable but still worse than native Performance Mode. The real fix was simpler than I wanted it to be. I ran the game at 1080p with Performance Mode and a high refresh rate. The visual difference on a 27-inch screen at that resolution is minimal during fast movement, and the input response was immediate. My times improved by three minutes in the first week of switching back. I felt stupid for not doing this sooner, but that's how these things go.

When Ultra Might Actually Make Sense

There are a few scenarios where higher graphics settings don't hurt as much. If you're doing a non-competitive run where the goal is just to finish the route fast without tracking frame-perfect splits, ultra settings won't materially affect your time. The game's engine handles high-end hardware well enough for casual play. If you're streaming or recording with ultra aesthetics as part of the presentation, you might accept a 5-10% time penalty for the visual quality. Some runners also use ultra settings during practice to reduce eye strain. This is a personal preference thing, not a performance optimization. If your eyes hurt less at high resolution, that can indirectly help your times because you're more comfortable during long practice sessions. Just don't confuse comfort with speed.

Hardware Requirements If You Still Want To Try It

If you're determined to run ultra alongside your speedrun attempts, here's what you actually need. A GPU with at least 12GB of VRAM—the 4070 Ti Super or better. 32GB of system RAM minimum, because texture streaming with ultra settings eats that alive. A monitor with a proven low input lag mode, preferably 240Hz or higher. You'll also want to disable Windows game bar, background recording software, and any overlay applications. These add their own latency on top of the GPU pipeline. The CPU matters less than usual here because Elden Ring is primarily GPU-bound at ultra settings. An Intel i7-12700K or Ryzen 7 5800X3D is plenty. The 5800X3D is particularly relevant because its L3 cache helps with the game's AI processing, which runs on the CPU thread and doesn't benefit from GPU upgrades.

What Most Runners Actually Do

The speedrun community standard is Performance Mode at native resolution or with minimal upscaling. This gives the lowest possible input latency and the most stable frame times. Leaderboard submissions require this configuration anyway because the rules specify that no graphics modifications are allowed that could alter game behavior. Ultra settings don't technically modify game behavior, but they do alter input timing, and some runners avoid it purely to stay on the safe side. I've seen runners argue about this online, usually people who haven't timed their own runs at both settings. The data is pretty clear if you actually measure it. Performance Mode is faster. Ultra is prettier. Pick one and stop trying to optimize the other.

Final Notes on Elden Ring Gameplay Speedrun Pc Ultra Graphics

I don't want to come across as gatekeeping here. Running the game however you want is fine for personal play. But if you're serious about times, stop chasing graphics settings and start chasing input consistency. The hardware you already have will work. The game is the same either way. Your mouse and keyboard inputs don't care about texture resolution. My advice, after wasting weeks on this exact problem, is to run Performance Mode, lock your resolution to something your monitor natively supports, and invest that energy into learning the routes instead. The records aren't being set by people with better GPUs. They're being set by people who've practiced the same frames ten thousand times. Graphics won't help you there.