PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The best Path of Exile 2 settings depend on your bottleneck. Keep native resolution when your GPU reaches its frame-rate target, then lower shadows, lighting and particle effects before sacrificing image sharpness. If the GPU is overloaded, test an appropriate upscaler; if the CPU is the limiter, lowering resolution will help little. Compare DirectX 12 and Vulkan on your own PC, and judge every change during real combat rather than in a quiet hideout.
Start with a target, not a preset
Choose the experience you want before changing sliders. A practical target includes your monitor resolution, the frame rate you want to sustain, and whether you value maximum clarity, lower input latency or steadier frame times. A 60 Hz display does not need the same settings as a 144 Hz display, and a laptop running at 1080p has a different decision than a desktop driving 1440p or 4K.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
GPVHOSO RTX 2060 8GB Super Graphics Card 256Bit GDDR6, | $239.99 | Buy on Amazon |
| 2 |
|
msi Gaming GeForce RTX 2060 6GB GDRR6 192-bit HDMI/DP 1710 MHz Boost Clock Ray Tracing Turing... | $345.00 | Buy on Amazon |
There is no universally best preset. The same setting can be harmless on one graphics card and expensive on another, while a busy map, a large spell effect or a crowded league encounter can behave very differently from a character standing in town. Change one group of settings at a time, keep resolution and gameplay conditions constant, and record whether the result improves frame rate, frame-time consistency, visibility, input response or hardware headroom.
Check which published requirements apply to your PC
Grinding Gear Games staff published one set of specifications in a September 2024 forum post. Steam Support currently reproduces a different store listing, including DirectX 12 and additional Intel Arc examples. Neither list is a guarantee of a particular frame rate, and the Steam page does not state a publication date for its reproduced requirements. Treat the figures as hardware anchors and confirm the live listing for your edition before making an upgrade decision.
#1 Best Overall
- Enhanced Performance: The RTX 2060 Super delivers exceptional gaming performance with 8GB of GDDR6 memory and a boost clock speed of up to 1650 MHz. It efficiently handles modern gaming titles at high settings, making it ideal for gamers seeking an immersive experience.
- Real-Time Ray Tracing: Equipped with Turing architecture, the RTX 2060 Super supports real-time ray tracing technology. This feature allows for realistic lighting, shadows, and reflections, enhancing visual fidelity in supported games and applications.
- VR Ready: The RTX 2060 Super is optimized for virtual reality (VR) experiences, providing low-latency and high-performance rendering. Gamers can enjoy an immersive VR environment with smooth graphics and responsive gameplay.
- DLSS Support: The graphics card supports Deep Learning Super Sampling (DLSS), which utilizes AI rendering to produce sharp images and increase frame rates without compromising quality. This technology ensures smoother gameplay, particularly at higher resolutions.
- Multiple Display Outputs**: With support for up to three displays, the RTX 2060 Super offers versatile connectivity options. It includes DisplayPort 1.4 and HDMI 2.0b outputs, enabling multi-monitor setups for enhanced productivity or gaming immersion.
| Source and status | Minimum specification | Recommended specification |
|---|---|---|
| Grinding Gear Games staff forum post, September 2024 | Windows 10; four-core 2.8 GHz x64-compatible processor; 8 GB RAM; NVIDIA GeForce GTX 960 or AMD Radeon RX 470; DirectX 11; broadband connection; 100 GB storage | Windows 10; eight-core 3.6 GHz x64-compatible processor; 16 GB RAM; NVIDIA GeForce RTX 2060 or AMD Radeon RX 5600 XT; DirectX 11; broadband connection; 100 GB storage; SSD recommended |
| Steam Support reproduced store listing, current crawled content; listing date not stated | 8 GB RAM; NVIDIA GeForce GTX 960 with at least 3 GB of VRAM, Intel Arc A380 or AMD Radeon RX 470; DirectX 12; 100 GB available storage | 16 GB RAM; NVIDIA GeForce RTX 2060, Intel Arc A770 or AMD Radeon RX 5600 XT; DirectX 12; SSD recommended |
The conflicting DirectX versions and the Steam listing’s explicit 3 GB VRAM note are why you should not treat either table as a universal performance promise. Settings adjustments can make a system more consistent, but they cannot turn hardware far below the minimum into a reliable high-resolution machine.
Identify a CPU or GPU limit before changing quality
Path of Exile 2’s in-game performance graph can help you compare CPU and GPU latency. A community forum discussion recommends using that graph and testing Vulkan and DirectX 12 on the same system. This is player advice, not a developer guarantee, so use it as a diagnostic method rather than an official ranking of renderers.
- Pick a repeatable scene. Use the same map area or combat sequence, with similar effects and enemy density. A hideout is useful for checking menus and baseline smoothness but may hide combat-related spikes.
- Note the current frame time. Watch whether the graph identifies CPU or GPU latency as the larger contributor and whether spikes occur during effects, movement or asset loading.
- Change only one variable group. For example, test a renderer first, then resolution scaling, then shadows. Do not change five settings and assume the largest visual difference caused the performance change.
- Repeat the scene. Compare average feel and the worst stutters, not just the highest number visible for a moment. A setting that raises a peak frame rate but creates inconsistent frame times is usually a poor trade for action combat.
If GPU latency is consistently higher, reduce rendered pixels or expensive GPU effects. If CPU latency dominates, lowering resolution may produce little benefit; close background workloads, use a sensible frame cap and lower settings that create large numbers of dynamic effects. If neither side is clearly dominant, prioritize frame-time consistency and visibility rather than chasing a nominal maximum.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose between DirectX 12 and Vulkan
| Renderer | How to evaluate it | When to keep it |
|---|---|---|
| DirectX 12 | An older 2024 GameSpot guide suggests it as a starting point. That is a starting recommendation, not a universal result. | Keep it when it produces steadier frame times, fewer crashes and better performance in your normal combat scenes. |
| Vulkan | The community discussion recommends trying it when comparing renderers on your own PC. | Keep it when it reduces stutter or GPU latency without making effects less visible or introducing instability. |
Use identical resolution, upscaling, frame cap and scene conditions for both tests. A renderer that feels faster in a quiet area can still perform worse during a spell-heavy encounter. If one option crashes, shows corruption or has severe hitching, return to the stable renderer even if a short test looked faster.
Set resolution and upscaling in the right order
Keep native resolution when it is already fast enough
Native output preserves the most detail in enemy silhouettes, ground effects and small interface text. If your GPU reaches the desired frame rate with acceptable frame times, there is no performance reason to add an upscaler. This is especially important when visibility matters more than a higher peak frame rate.
Use an upscaler when the GPU is the bottleneck
DLSS, FSR or XeSS may be available depending on your graphics hardware and the current game build. Each renders internally at a lower resolution and reconstructs the output, reducing GPU work. Start with the highest quality tier that meets your target, then move to a more performance-oriented tier only if combat remains below target. Inspect moving foliage, spell edges, thin objects and text; a nominally faster mode is not an improvement if it makes threats harder to read.
Use the vendor-appropriate option when several are offered, but judge the result on your own card. The available methods and quality labels can change with patches, and no verified universal FPS gain applies to every tier or resolution.
Treat dynamic resolution as a trade-off
Dynamic resolution changes internal resolution to protect a frame-rate target. A forum contributor reports that it can make the image look muddy. That is a subjective observation, not a measured defect, so compare it in motion during combat. If image clarity falls noticeably, use a fixed resolution with a lower upscaling tier or reduce shadows and lighting instead.
Lower the settings that cost the most GPU time
Shadows
Shadows are one of the first settings to test when GPU latency is high. Reduce them one step at a time and check whether character outlines, ground hazards and nearby geometry remain easy to distinguish. Very low shadows can remove useful depth cues, so stop at the lowest level that still lets you read terrain.
Global illumination and lighting
Global illumination or lighting quality can be expensive in scenes with many light sources and effects. Lower it when the graph shows a GPU limit, particularly if you are already using native resolution. Watch dark areas after each change: a faster setting is not useful if it obscures enemies or makes ground effects blend together.
Rank #2
- Memory Speed:14 Gbps.Digital Max Resolution:7680x4320
- Chipset: NVIDIA GeForce RTX 2060
- Video Memory: 6GB GDDR6
- Memory Interface: 192-bit
- Output: DisplayPort x 3 (v1.4a) / HDMI 2.0b x 1
Particle effects
Particle effects can create sudden load during large packs and cooperative encounters. Reduce them when frame-time spikes occur specifically during spell-heavy combat. Test a representative fight, because a calm area will not reveal the cost. Keep enough effect detail to distinguish your own skills, enemy telegraphs and hazardous ground effects.
Texture quality and VRAM
Texture quality is often a relatively low-cost visual setting when your graphics card has sufficient VRAM. Keep it higher if memory headroom is available and you want sharper surfaces. If you see texture streaming, sudden hitching or memory pressure, lower textures before adding more aggressive upscaling. The Steam Support listing explicitly states at least 3 GB of VRAM for its minimum GPU entry; that figure belongs to that listing and is not a universal VRAM recommendation for every resolution or texture setting.
Preserve visibility, latency and consistency
Brightness and HDR
Adjust brightness so dark detail is visible without washing out highlights. HDR can improve contrast on a correctly configured display, but an incorrect operating-system or monitor profile can make shadows too dark or effects look clipped. Compare the same scene with HDR enabled and disabled, then keep the mode that makes enemy attacks and ground indicators easiest to read.
VSync and frame caps
Use a frame cap that matches what your system can sustain rather than an unstable maximum. VSync can prevent visible tearing, while disabling it may reduce display latency at the cost of tearing. Test both with the same cap and choose based on whether smooth presentation or the lowest possible response is more important to you. A cap also leaves headroom for sudden combat effects instead of letting the GPU run continuously at its limit.
Resolution, interface scale and visibility
Do not lower output resolution solely to fix a CPU limit. It reduces image detail while leaving much of the simulation and game logic unchanged. If text or interface elements become difficult to read after changing resolution, adjust the interface scale separately where the current build provides that control.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Use a profile that matches your hardware goal
| Profile | Starting choices | What to verify |
|---|---|---|
| Clarity-first | Native resolution; highest stable texture quality; native rendering or the highest-quality upscaler; moderate shadows and lighting; fixed frame cap | GPU latency remains below your target and busy fights do not produce distracting spikes |
| Balanced | Native resolution if possible; quality-tier upscaler when GPU-limited; reduced shadows and lighting; moderate particles; textures kept high only with VRAM headroom | Effects remain distinguishable while frame times stay consistent in dense combat |
| Performance-first | Performance-oriented upscaler; lower shadows and lighting; reduced particles; conservative texture quality if VRAM is tight; stable frame cap | Enemy telegraphs, ground hazards and interface text remain readable at the chosen output resolution |
| CPU-limited | Keep a sensible resolution; prioritize a stable cap; reduce effect-heavy options and background workloads; compare renderers | Lowering resolution does not solve the problem, while CPU latency or simulation spikes remain the dominant graph signal |
These are starting configurations, not guaranteed presets. Move one setting back toward quality whenever your measured headroom allows it.
Test in the situations that actually cause trouble
Use at least three checks: an ordinary traversal, a dense pack with several skills, and the area where you normally notice stutter. Include loading into a map and moving through new terrain if asset streaming is part of the problem. Record renderer, output resolution, upscaling mode, frame cap and the settings you changed. Repeat after a patch because shader compilation, renderer behavior and available options can change.
Do not rely on a single FPS number. Look for consistent frame delivery, readable effects and responsive input. A quiet hideout can make an unstable configuration appear excellent, while a brief combat test can exaggerate a one-time hitch. The useful result is the setting that remains comfortable across your normal play, not the largest number shown in an isolated scene.
Troubleshoot common symptoms
High GPU latency or low frame rate everywhere
- Confirm that the game is using the intended graphics processor rather than an integrated adapter.
- Test an upscaler at its highest quality tier, then reduce shadows and lighting if more headroom is needed.
- Lower particle effects for dense encounters and check whether textures are consuming available VRAM.
- Compare DirectX 12 and Vulkan under the same scene and cap.
Stutters only during large fights
- Repeat the fight after reducing particles, shadows and lighting one group at a time.
- Check whether CPU latency, rather than GPU latency, spikes on the performance graph.
- Use a stable frame cap instead of allowing unrestricted swings between high and low frame times.
- Close background applications that compete for CPU time or memory.
Muddy or shimmering image
- Return from a performance-oriented upscaling tier to a higher-quality tier.
- Disable dynamic resolution temporarily and compare the same moving scene.
- Restore native resolution if the GPU can sustain the target.
- Check that sharpening, HDR and monitor scaling are not exaggerating reconstruction artifacts.
Textures look blurry or appear late
- Verify available VRAM and lower texture quality if memory pressure or streaming hitching is visible.
- If VRAM is not constrained, raise texture quality while leaving expensive lighting settings reduced.
- Use an SSD when available; the 2024 GGG recommendation lists an SSD as recommended, and Steam’s reproduced listing also recommends one, but neither promises a specific loading-time improvement.
Renderer crashes or displays visual corruption
- Switch between DirectX 12 and Vulkan and retest in the same area.
- Return experimental quality combinations to a stable baseline before changing another option.
- Keep the renderer that completes normal play reliably; a theoretical performance advantage is not useful if it causes crashes.
When settings are not enough
If your PC is below the published minimum, severe compromises may still leave combat unstable. If it is near the minimum, target a lower output resolution and conservative effects rather than expecting recommended-tier clarity. For a system below the recommended anchor, an NVIDIA GeForce RTX 2060 or AMD Radeon RX 5600 XT is a reference point from the September 2024 GGG post, not a required purchase and not a promise of a particular frame rate. Upgrade only after checking that your measured bottleneck is actually the graphics card; a CPU, memory or storage limitation will not be fixed by a faster GPU.
Quick Recap
A practical final sequence
- Write down your display resolution and sustainable frame-rate target.
- Confirm which published requirement list matches your platform and note your CPU, RAM, GPU, VRAM and storage.
- Run the same combat scene with DirectX 12 and Vulkan.
- Use the performance graph to decide whether CPU or GPU latency is dominant.
- Keep native resolution if the target is already stable; otherwise test an appropriate upscaler.
- Lower shadows, lighting and particles in that order while checking visibility.
- Keep textures high only when VRAM and streaming behavior remain comfortable.
- Set brightness or HDR for readable dark detail, then choose VSync and a frame cap based on tearing and latency.
- Repeat the test in dense combat and keep the configuration that delivers the clearest, steadiest play.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
