Indiana Jones And The Great Circle nails atmosphere, scale, and cinematic pacing, but the moment DLSS is toggled on, a lot of PC players notice something feels off. Instead of smoother frame pacing, FPS dips appear during traversal, combat spikes stutter, and camera pans hitch like the GPU just lost aggro. That disconnect between expectation and reality is exactly why this issue is so frustrating, especially on GPUs that should be cruising.
Why DLSS Can Hurt Performance Instead of Helping
DLSS isn’t a magic FPS switch; it’s a reconstruction pipeline that depends heavily on clean motion vectors and stable frame delivery. In Indiana Jones And The Great Circle, several environments push heavy per-pixel lighting, volumetric shadows, and dense geometry, which strains the engine’s temporal data. When DLSS struggles to reconstruct frames accurately, it increases GPU workload instead of reducing it, leading to frame drops rather than gains.
This is most noticeable when rotating the camera quickly, entering large interior spaces, or transitioning between cutscenes and gameplay. The engine rapidly changes scene complexity, and DLSS doesn’t always adapt cleanly, causing micro-stutter or sudden FPS collapses.
CPU Bottlenecks and Frame Pacing Conflicts
One of the biggest misconceptions is assuming DLSS is purely GPU-bound. In reality, Indiana Jones And The Great Circle leans hard on the CPU for world streaming, NPC logic, and physics-driven set pieces. When DLSS boosts raw FPS, it can expose CPU limits that weren’t visible at native resolution.
This results in uneven frame pacing where the GPU finishes frames faster than the CPU can feed them. The end result feels like lag even when the FPS counter looks healthy, especially on mid-range CPUs paired with high-end GPUs.
VRAM Pressure and Texture Streaming Issues
DLSS Performance and Balanced modes reduce internal resolution, but they don’t always reduce VRAM usage proportionally. High-resolution textures, ray-traced effects, and aggressive streaming can still push VRAM limits, particularly on 8GB and 10GB cards.
When VRAM fills up, the game starts swapping data mid-frame. That’s when players see sudden FPS drops, delayed texture loads, or hitching during exploration, even though DLSS is technically enabled and functioning.
Driver-Level Optimization Gaps
At launch and early update cycles, GPU drivers often lag behind engine-specific optimizations. DLSS profiles rely on driver-side tuning to handle motion vectors, sharpening, and frame timing correctly. Without a properly optimized driver, DLSS can behave inconsistently, amplifying stutter instead of smoothing it out.
This is why some players see massive FPS gains on one driver version and performance regressions on another, even with identical in-game settings.
Why DLSS Alternatives Sometimes Feel Better
In certain scenarios, native resolution with dynamic resolution scaling or even FSR can deliver more stable performance. That’s not because DLSS is inferior, but because Indiana Jones And The Great Circle’s rendering pipeline sometimes favors simpler scaling methods over advanced temporal reconstruction.
When frame consistency matters more than raw FPS, especially during combat or traversal-heavy sequences, stability wins. Understanding that trade-off is the key to fixing the problem instead of blindly chasing higher numbers.
Why DLSS Can Perform Worse Than Native Rendering in This Game
On paper, DLSS should be a free FPS win. In Indiana Jones And The Great Circle, though, it can backfire depending on your hardware balance, settings, and even where you are in the game world. The issue isn’t that DLSS is broken, but that its strengths don’t always align with how this engine handles streaming, CPU workloads, and frame timing.
CPU Bottlenecks Become More Aggressive With DLSS Enabled
DLSS lowers the internal render resolution, which means your GPU finishes its work faster. That sounds great until the CPU becomes the limiting factor. In this game, AI routines, physics interactions, and world streaming are extremely CPU-heavy, especially in dense hub areas and scripted sequences.
When the GPU is waiting on the CPU to deliver the next frame, you get inconsistent frame delivery instead of a smooth curve. This is why players see 90 to 120 FPS with DLSS enabled, yet the game feels worse than a locked 60 at native resolution. The fix here is counterintuitive: cap your FPS slightly below your CPU’s comfort zone using an in-game limiter or RTSS to stabilize frame pacing.
DLSS Increases Frame Pacing Sensitivity
Indiana Jones And The Great Circle is very sensitive to frame time variance. DLSS can introduce micro-oscillations in frame delivery because reconstructed frames rely heavily on motion vectors and temporal data. When those vectors don’t align cleanly with camera pans or fast traversal, frame times spike even if average FPS stays high.
Switching DLSS from Performance to Quality often improves this, even if the FPS number drops. Quality mode reduces reconstruction artifacts and stabilizes motion, which leads to smoother camera movement during exploration and combat. This is one of those cases where better frame consistency beats raw throughput.
VRAM Saturation Can Be Worse With DLSS Than Native
DLSS does not automatically mean lower VRAM usage. High texture quality, ray-traced lighting, and detailed geometry still allocate full-resolution assets. On GPUs with 8GB or 10GB of VRAM, DLSS can actually push the game into memory pressure faster because the engine assumes headroom that isn’t really there.
The practical fix is to drop texture quality by one tier and disable ray-traced reflections if you’re near your VRAM limit. This often results in higher real-world FPS with DLSS than simply leaving visuals maxed and hoping the upscaler saves you.
Sharpening and Post-Processing Overhead
DLSS sharpening isn’t free. In Indiana Jones And The Great Circle, aggressive sharpening combined with film grain, motion blur, and depth of field adds extra post-processing passes. These effects stack up, especially at higher output resolutions like 1440p and 4K.
Reducing DLSS sharpening to zero and disabling film grain and motion blur can recover lost performance instantly. The image often looks cleaner too, which makes this one of the easiest wins for both FPS and clarity.
Driver and DLSS Version Mismatch
Not all DLSS implementations are equal. This game is particularly sensitive to driver-level DLSS handling, and outdated drivers can cause stutter, frame drops, or uneven GPU utilization. Players who updated drivers mid-playthrough often report performance swings without touching in-game settings.
Updating to the latest Nvidia driver and manually swapping to a newer DLSS DLL can dramatically improve stability. This aligns DLSS’s temporal reconstruction with the engine’s current motion vector output, reducing hitching during camera-heavy moments and cinematic transitions.
When Native or FSR Is the Smarter Choice
In some setups, especially GPU-heavy but CPU-limited rigs, native resolution with a slight resolution scale reduction delivers smoother gameplay than DLSS. FSR, while less advanced, applies simpler scaling that can better match this engine’s frame timing behavior.
If DLSS feels unstable after tuning, try native rendering with a 90 to 95 percent resolution scale and enable a frame cap. The result is often lower peak FPS, but far fewer dips during traversal, combat encounters, and puzzle-heavy sections where consistency matters most.
Quick In-Game Fixes: DLSS Mode, Resolution Scaling, and Hidden Settings to Change
If DLSS is actively hurting your FPS instead of helping, the fastest gains usually come from rethinking how the game is scaling its image. Indiana Jones And The Great Circle leans heavily on temporal data and post-processing, which means the wrong DLSS mode or resolution target can create extra GPU work instead of reducing it. Before touching external tools or config files, these in-game changes should be your first stop.
DLSS Mode: Why Quality Is Often the Worst Choice
DLSS Quality sounds like the safe pick, but in this game it’s often the least efficient. At 1440p and above, DLSS Quality renders at a high internal resolution, leaving minimal headroom for the GPU while still adding DLSS’s reconstruction overhead. That’s a recipe for uneven frame pacing, especially in dense interior scenes and cinematic transitions.
Switching to DLSS Balanced usually delivers the smoothest experience. Performance mode can boost raw FPS, but it tends to amplify temporal artifacts on fast camera pans, which then increases reconstruction cost frame-to-frame. Balanced hits the sweet spot where the GPU actually gets breathing room without stressing the engine’s motion vectors.
Resolution Scaling Beats DLSS When You’re GPU-Bound
If your GPU usage is pegged near 95 to 99 percent with DLSS enabled, resolution scaling can outperform it outright. Native resolution with a 90 to 95 percent render scale reduces pixel cost without adding DLSS’s temporal processing layer. That means fewer compute passes and more consistent frame times.
This works especially well on mid-to-high-end GPUs that aren’t VRAM-starved but struggle with sustained boost clocks. The visual difference is minor, but traversal and combat feel dramatically smoother because the engine isn’t fighting reconstruction during camera-heavy moments.
The Hidden Cost of Dynamic Resolution and V-Sync
Dynamic resolution scaling sounds helpful, but in Indiana Jones And The Great Circle it frequently conflicts with DLSS. Both systems attempt to manage performance, which leads to resolution oscillation and sudden FPS drops when the engine rapidly changes targets mid-scene.
Disable dynamic resolution entirely when using DLSS or manual resolution scaling. At the same time, turn off in-game V-Sync and use either Nvidia Control Panel V-Sync or a frame limiter instead. The in-game implementation adds latency and can trigger GPU stalls that look like random DLSS drops.
Ray Tracing Presets That Quietly Break DLSS Efficiency
Even when ray tracing is “partially” enabled, DLSS has to reconstruct ray-traced data, not just rasterized frames. Ray-traced shadows and reflections are particularly expensive here, and they scale poorly with DLSS Quality and Balanced modes.
If you want DLSS to actually work as intended, disable ray-traced reflections first and leave shadows on their highest non-RT setting. This reduces reconstruction complexity and stabilizes GPU workload, which translates directly into fewer dips during exploration and puzzle sequences.
Frame Caps and Why DLSS Hates Uncapped Boost Clocks
DLSS performs best when frame pacing is predictable. Leaving the game uncapped lets the GPU spike and downclock constantly, which increases variance in DLSS reconstruction timing. That’s when microstutter creeps in, even if the average FPS looks high.
Set a frame cap 3 to 5 FPS below your monitor’s refresh rate. This keeps GPU clocks stable, reduces DLSS overhead, and results in smoother motion during whip swings, combat encounters, and cutscene-heavy story beats where consistency matters more than raw numbers.
DLSS Frame Generation, Ray Tracing, and CPU Bottlenecks Explained
Once you’ve stabilized DLSS with sane caps and cleaner rendering inputs, the next performance wall players hit is frame generation and how it interacts with the CPU. Indiana Jones And The Great Circle leans heavily on simulation, streaming, and animation logic, which means DLSS can only do so much if the CPU can’t feed frames consistently.
This is where FPS drops feel confusing. Your GPU usage looks low, DLSS is enabled, yet the game still stutters during traversal or dense interiors. That’s not a DLSS failure—it’s a pipeline mismatch.
Why DLSS Frame Generation Can Lower FPS Instead of Raising It
DLSS Frame Generation doesn’t reduce GPU load; it adds work on top of it. The game still has to render base frames, calculate motion vectors, and synchronize AI and physics before DLSS can generate interpolated frames.
In Indiana Jones And The Great Circle, this becomes a problem when the CPU can’t deliver consistent base frames. Frame Generation then waits on uneven frame times, causing hitching, input latency spikes, or outright FPS drops during camera pans and combat.
If you’re on a 40-series GPU, only enable Frame Generation after confirming your native DLSS FPS is already stable. If your baseline frame rate fluctuates below 60, Frame Generation amplifies instability instead of hiding it.
Ray Tracing vs Frame Generation: A Tug of War
Ray tracing and Frame Generation compete for the same frame timing budget. RT increases render latency per frame, while Frame Generation demands tight synchronization between real and generated frames.
When both are enabled, Indiana Jones And The Great Circle often hits a scheduling bottleneck. The result is uneven pacing where FPS counters look fine, but motion feels choppy and inconsistent.
If you want Frame Generation, disable all ray-traced effects entirely. If you want ray tracing, turn Frame Generation off and rely on DLSS Quality or Balanced instead. Mixing both is one of the fastest ways to destabilize performance in this engine.
CPU Bottlenecks: The Silent DLSS Killer
This game is CPU-heavy in ways most GPU-bound titles aren’t. World streaming, enemy logic, puzzle scripting, and animation blending all run on the CPU, especially during exploration-heavy sequences.
When the CPU becomes the limiter, DLSS can’t help because there are fewer frames to upscale in the first place. That’s why GPU usage drops into the 70 percent range while FPS tanks in busy scenes.
To mitigate this, lower CPU-bound settings like crowd density, simulation detail, and view distance. Also close background apps and disable overlays, as even minor CPU interruptions can break frame pacing here.
Drivers, DLSS Versions, and When to Use Alternatives
Outdated GPU drivers can dramatically worsen DLSS behavior in Indiana Jones And The Great Circle. Newer drivers improve frame pacing, shader compilation, and DLSS stability, especially with Frame Generation.
If DLSS continues to misbehave, test DLSS Quality without Frame Generation, or switch to XeSS or FSR as a fallback. These alternatives lack Frame Generation but often provide more consistent frame times on CPU-limited systems.
The goal isn’t chasing the highest FPS number—it’s maintaining steady delivery. In this game, smooth motion during whip traversal and puzzle solving matters far more than inflated averages that collapse under load.
Driver-Level Fixes: NVIDIA Driver Versions, Clean Installs, and Control Panel Tweaks
If DLSS is still tanking your FPS after in-game tuning, the problem often lives one layer lower: the driver. Indiana Jones And The Great Circle is extremely sensitive to frame pacing, shader caching, and driver-level latency handling.
DLSS Frame Generation, in particular, relies on tight driver scheduling. A single bad driver profile or corrupted install can turn what should be smooth interpolation into stutter, hitching, or sudden drops that feel worse than native rendering.
Use the Right NVIDIA Driver (And Don’t Assume Newest Is Best)
Not every Game Ready driver plays nicely with every engine, and this game is proof. Some players see worse DLSS frame pacing on brand-new releases due to changes in Frame Generation scheduling or shader compilation behavior.
If you updated drivers shortly before the FPS drops started, roll back one or two versions and retest. Look for drivers released around major DLSS or Frame Generation updates, as those tend to be more stable for games leaning heavily on NVIDIA’s upscaling stack.
Avoid hotfix drivers unless you’re troubleshooting a specific crash. Stability matters more than raw performance here.
Do a True Clean Install (DDU Is Not Optional)
Standard driver installs often leave behind old shader caches, profiles, and registry hooks. When DLSS behavior changes between driver versions, those leftovers can directly cause stuttering and inconsistent frame times.
Use Display Driver Uninstaller in Safe Mode, wipe the NVIDIA driver completely, then install your chosen version fresh. During installation, select Custom and uncheck everything except the core driver and PhysX.
This resets DLSS, Frame Generation, and shader caching behavior back to a known-good baseline, which is critical for diagnosing real performance issues versus software cruft.
NVIDIA Control Panel Tweaks That Actually Matter
Open the NVIDIA Control Panel and set changes per-game, not globally. Indiana Jones And The Great Circle responds poorly to one-size-fits-all profiles.
Set Power Management Mode to Prefer Maximum Performance to prevent clock downshifts during exploration-heavy scenes. DLSS hates fluctuating GPU clocks, especially when Frame Generation is active.
Low Latency Mode should be set to Off when using Frame Generation. NVIDIA Reflex already handles latency in-engine, and stacking both can create scheduling conflicts that hurt frame pacing.
Shader Cache, V-Sync, and G-Sync Alignment
Set Shader Cache Size to Unlimited or at least 10 GB. This game recompiles shaders aggressively when streaming new areas, and a small cache leads to recurring stutter that looks like DLSS instability.
Disable V-Sync in the NVIDIA Control Panel and manage sync in-game or via G-Sync instead. Double-buffering at the driver level adds latency and can cause DLSS-generated frames to miss their delivery window.
If you’re using G-Sync, cap FPS slightly below your monitor’s refresh rate using an external limiter like RTSS. This keeps frame delivery consistent and prevents DLSS Frame Generation from oscillating between CPU and GPU limits.
Threaded Optimization and Background Interference
Leave Threaded Optimization set to Auto. Forcing it On can backfire in CPU-heavy engines like this one, increasing contention instead of reducing it.
Also disable overlays at the driver level, including GeForce Experience’s in-game overlay. These hooks run on the CPU and can interrupt DLSS frame scheduling during traversal, combat, and puzzle transitions.
At this stage, DLSS FPS drops aren’t about raw horsepower. They’re about eliminating timing conflicts, and the driver is where most of those battles are won or lost.
Advanced Fixes: DLSS DLL Swaps, Reflex Settings, and Windows Optimization
If you’ve cleaned up the driver layer and DLSS is still tanking FPS in Indiana Jones And The Great Circle, you’re officially in advanced territory. This is where engine behavior, Windows scheduling, and NVIDIA’s own feature stack start stepping on each other.
The good news is that these fixes target the actual reasons DLSS drops frames in this game: bad frame pacing, CPU-to-GPU desync, and Windows interrupting render queues at the worst possible time.
DLSS DLL Swaps: Why the Default Version Can Betray You
Indiana Jones And The Great Circle ships with a conservative DLSS DLL that prioritizes stability across a wide range of hardware. On mid-to-high-end GPUs, that older version can cause sporadic FPS drops during camera pans, traversal, and scene transitions.
Swapping the DLSS DLL to a newer version like 3.7 or later often stabilizes frame pacing immediately. Newer DLLs handle motion vectors and frame generation prediction more efficiently, reducing the micro-hitches that feel like random DLSS collapses.
Use a tool like DLSS Swapper, or manually replace the nvngx_dlss.dll in the game directory. Always back up the original file, and avoid mixing experimental DLSS builds if you’re already using Frame Generation.
Frame Generation and Reflex: Stop Them From Fighting Each Other
DLSS Frame Generation shifts a lot of scheduling responsibility to the CPU, which is exactly why FPS drops feel worse on strong GPUs paired with mid-range CPUs. NVIDIA Reflex exists to manage that latency, but only if it’s configured correctly.
Set Reflex to On or On + Boost inside the game, but do not force Low Latency Mode in the NVIDIA Control Panel. Doubling up creates a tug-of-war over the render queue, leading to inconsistent frame delivery and sudden drops when the engine spikes CPU load.
If you’re CPU-limited, On + Boost can help keep clocks high during heavy traversal scenes. If GPU-limited, standard On is usually more stable and avoids unnecessary power spikes.
Windows Hardware Scheduling and Game Mode Tweaks
Windows itself is often the silent culprit behind DLSS instability. Hardware-Accelerated GPU Scheduling should be tested both On and Off, but many players report smoother DLSS behavior with it enabled on RTX 40-series cards.
Game Mode should be On, but background app permissions should be locked down aggressively. Disable background capture, Xbox DVR, and any monitoring tools that poll sensors every frame, as they can interrupt DLSS frame generation timing.
Also make sure your Windows power plan is set to High Performance or Ultimate Performance. Balanced mode can downclock the CPU mid-frame, which DLSS interprets as a timing fault and responds to by dropping generated frames.
Core Parking, CPU Affinity, and Why FPS Drops Feel Random
DLSS Frame Generation is extremely sensitive to CPU core availability. If Windows parks cores or shifts threads during gameplay, FPS drops appear out of nowhere even though GPU usage looks fine.
Disable CPU core parking using a trusted power plan tool or advanced power settings. This keeps render, simulation, and DLSS threads from being shuffled mid-scene, which is a common cause of traversal stutter.
Avoid manually setting CPU affinity unless you know exactly what you’re doing. The engine already distributes threads dynamically, and forcing affinity can reduce performance instead of improving it.
Why These Fixes Work When Others Don’t
At this level, DLSS FPS drops aren’t about resolution or quality presets. They’re about timing, synchronization, and making sure nothing interrupts the frame pipeline once DLSS takes control.
DLL swaps improve prediction accuracy, Reflex stabilizes render queues, and Windows optimization prevents the OS from sabotaging frame delivery. When all three align, Indiana Jones And The Great Circle finally runs the way DLSS was meant to deliver it.
DLSS Alternatives That Perform Better: XeSS, FSR, or Native + Sharpening
If DLSS still tanks your FPS after every stability fix, it’s time to step back and ask the uncomfortable question: is DLSS actually the best option for this engine? In Indiana Jones And The Great Circle, the answer is often no.
This game’s renderer leans heavily on temporal data, dense post-processing, and CPU-driven scene traversal. When DLSS mispredicts motion vectors or loses sync with the CPU, it doesn’t just blur the image, it collapses frame pacing. That’s where alternative upscalers can deliver more consistent performance, even if the raw FPS number looks similar on paper.
Intel XeSS: The Most Stable Drop-In Replacement
XeSS is the closest DLSS substitute in terms of image reconstruction, but it’s far less sensitive to frame timing volatility. In The Great Circle, XeSS consistently avoids the sudden FPS cliffs that plague DLSS during camera swings, interior transitions, and scripted set pieces.
Run XeSS in Quality or Balanced mode and pair it with the in-game sharpening slider around 20–30 percent. GPU load will rise slightly compared to DLSS, but frame pacing is dramatically smoother, which matters more than peak FPS when you’re navigating tight corridors or combat-heavy encounters.
On RTX GPUs, XeSS uses DP4a instead of Tensor cores, which removes the DLSS dependency on perfect prediction timing. The result is fewer dropped frames, fewer micro-stutters, and far more consistent 1% lows.
AMD FSR 2: Lower Ceiling, Higher Consistency
FSR 2 doesn’t win any image quality shootouts, but it wins stability battles. In this engine, FSR 2’s temporal upscaling pipeline is less aggressive, which reduces ghosting and eliminates the DLSS-specific hitching that occurs when the game streams assets mid-frame.
Use FSR 2 Quality mode at 1440p or higher and disable any additional sharpening outside the game. Over-sharpening amplifies edge shimmer, especially on foliage and fine geometry common in jungle environments.
FSR’s biggest advantage here is predictability. The FPS you see is the FPS you get, without sudden drops when traversal, lighting changes, or physics-heavy scenes kick in.
Native Resolution + Sharpening: The Hidden Sleeper Option
For high-end GPUs, native resolution with sharpening can outperform broken DLSS setups in real gameplay. Without upscaling in the frame pipeline, the engine avoids the synchronization overhead that triggers DLSS frame drops in the first place.
Run native with Temporal AA or SMAA, then apply a mild sharpening pass either in-game or via your GPU control panel. This keeps image clarity high while preserving stable frame delivery, especially during cutscenes and rapid camera motion.
This setup shines on RTX 4080 and 4090 systems where raw raster power is plentiful. You trade headline FPS numbers for consistency, and in The Great Circle, consistency wins every time.
Which Option Should You Actually Use?
If your priority is smooth traversal and stable combat pacing, XeSS is currently the most reliable upscaler for Indiana Jones And The Great Circle. If you value predictability above all else, FSR 2 is the safest fallback.
DLSS still has the highest potential, but only when every system variable behaves perfectly. Until engine patches or DLSS updates address its timing sensitivity, these alternatives offer a smoother, frustration-free way to experience the game without fighting your own hardware.
Performance Verification: How to Test, Benchmark, and Lock in Stable FPS
Once you’ve moved off unstable DLSS behavior and settled on a cleaner upscaling or native setup, the final step is proving your system can actually hold frame pacing under pressure. Chasing a higher average FPS means nothing if traversal stutters or combat drops frames mid-animation.
This is where you stop tweaking blindly and start validating. Indiana Jones And The Great Circle is heavily dependent on streaming, animation blending, and lighting transitions, so real-world testing matters more than synthetic numbers.
Build a Repeatable Stress Test Route
Pick a short, repeatable gameplay loop that reliably triggers FPS drops. Fast traversal through dense jungle, rotating the camera during interior-to-exterior transitions, or sprinting through hub areas with NPCs all stress the engine’s streaming pipeline.
Run this same route every time you change a setting. If your FPS dips in the same spot repeatedly, that’s a system or engine bottleneck, not RNG or a one-off hitch.
Consistency here is key. If a fix works, it will work every time on the same route.
Use the Right Monitoring Tools (Not Just FPS Counters)
Average FPS hides the real problem. What you’re hunting is frame time spikes and 1% lows collapsing when the engine loads new assets.
Use tools like MSI Afterburner or CapFrameX to monitor frame time graphs while playing. A stable experience looks like a flat line with minor ripples, not jagged spikes when the camera turns or lighting shifts.
If DLSS was your issue, you’ll see this immediately. Remove it, and the frame time graph should visibly smooth out even if your raw FPS number drops slightly.
Verify GPU and CPU Behavior Under Load
Indiana Jones And The Great Circle can quietly become CPU-limited, especially when DLSS shifts work off the GPU. Watch CPU thread usage during traversal and combat-heavy scenes.
If one or two threads spike while GPU usage dips, you’re hitting an engine-side scheduling wall. This is why XeSS and FSR 2 feel smoother here—they keep the GPU consistently fed without stalling the CPU mid-frame.
Also check VRAM usage. If you’re near the limit, reduce texture quality one notch before touching resolution or upscaling.
Lock Your FPS to Kill Microstutter
Once you’ve identified your lowest stable FPS during stress testing, lock it. A hard cap 5 to 10 FPS below your worst dip dramatically improves frame pacing.
Use in-game caps first, then fall back to your GPU control panel if needed. Avoid external limiters stacking on top of each other, as that can reintroduce latency and uneven pacing.
This game feels far better at a locked 60 or 90 FPS than a fluctuating 120 that drops during every lighting transition.
Final Stability Pass: One Change at a Time
Make only one adjustment per test cycle. Changing resolution scale, sharpening, and post-processing simultaneously makes it impossible to diagnose what actually helped.
If a fix improves frame time stability but costs a few FPS, keep it. Indiana Jones And The Great Circle rewards consistency more than raw speed, especially during cinematic moments and combat where animation timing matters.
Once your frame time graph is clean and your FPS no longer dips during your stress route, you’re done. Stop chasing numbers and start playing.
Lock It In and Move On
With DLSS sidelined and your performance verified, you’ve effectively future-proofed your setup against engine quirks and streaming hiccups. The Great Circle is at its best when the tech disappears and the adventure takes over.
Set it, lock it, and trust your tuning. Indiana Jones deserves smooth exploration, not a frame time boss fight before every session.