Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →iTechGuides 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
For better DirectX 12 performance on an Intel Arc GPU, change the game’s own resolution, render scale and most expensive effects first. If the game supports XeSS, test its quality and performance modes at your target resolution. Use Intel Graphics Software profiles and telemetry to measure each change, and treat V-Sync, Smooth Sync and Game Compatibility as display or troubleshooting controls—not guaranteed FPS boosters.
What actually improves DX12 performance on Intel Arc?
There is no universal Intel Arc switch that makes every DX12 game render faster. Performance depends on the specific game engine, driver version, GPU model, CPU, resolution, memory configuration and graphics options. A setting that helps one title can have no effect—or create a visual or compatibility problem—in another.
The reliable approach is controlled tuning:
- Measure a repeatable scene or the game’s built-in benchmark.
- Change one setting at a time.
- Record average FPS and whether frame delivery feels consistent.
- Keep the change only if it solves your performance problem without an unacceptable image-quality or latency cost.
Intel Graphics Software provides per-application profiles and live telemetry for FPS, memory use, clock speed, temperature and voltage. Use those readings to compare the same workload before and after a change. Telemetry can show what the GPU is doing, but it is not a substitute for a controlled benchmark; no general percentage gain applies to all Arc cards and DX12 games.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated 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 matchStart with the current Intel software and driver
Use Intel Graphics Software on current systems
Intel Graphics Software is Intel’s current utility for Arc settings, application profiles, driver access and monitoring. Its available controls can vary by product and platform, so a menu shown in one installation may not appear on another. Open the application and confirm that the game is detected before creating a profile.
#1 Best Overall
- Next-Gen Intel Arc Graphics: Powered by Intel Arc A580 GPU with Intel Xe HPG microarchitecture, featuring 384 XMX engines for enhanced AI acceleration and content creation.
- High-Performance Memory: 8GB GDDR6 on a 256-bit interface running at 16 Gbps, delivering excellent bandwidth for 1440p gaming and creative workloads.
- Factory Overclocked: Engine clock set at 2000 MHz out of the box, providing optimized performance for smooth gameplay and multimedia tasks.
- Advanced Dual-Fan Cooling: Features a dual-fan design with striped axial fans and an ultra-fit heatpipe for efficient thermal management. 0dB Silent Cooling stops fans completely at low temperatures for silent operation.
- Durable Construction: Includes a stylish metal backplate for enhanced PCB rigidity and a premium aesthetic, backed by ASRock's Super Alloy components for long-term reliability.
Profiles let you keep settings associated with a particular executable instead of changing a global value that affects every game. This is especially useful when one DX12 title needs a workaround but other games run correctly with their normal settings.
Understand the Arc Control references in older support pages
Intel Arc Control is the older interface. Intel’s support articles for Arc Control remain useful for legacy installations and for explaining features such as Frame Delivery and Game Compatibility, but they should not be treated as a map of every current Intel Graphics Software menu. If a control is missing, check the utility and driver generation you actually have rather than assuming the feature was removed or is required for performance.
Read the driver notes for the game
DX12 problems can be tied to a particular game and driver release. Before changing several settings, read the current Intel Graphics Driver Release Notes and the game developer’s support information. Release notes can supersede older workarounds as drivers change.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Change the game’s most expensive rendering settings first
Open the title’s Graphics, Video or Display menu. The exact labels differ, but the following settings usually offer the most direct quality-versus-performance choices. Lower one item, replay the same scene and note the result before changing another.
Rank #2
- System Compatibility Note: This 2-slot card measures 271 x 112 x 39 mm and requires a single 12V-2x6-pin power connector. Please verify chassis and PSU compatibility before purchase.
- Dedicated Support: Please contact us directly through Amazon for any product questions or assistance you may require.
- Professional Intel Arc Pro B70 GPU: Built on the Intel Xe2-HPG architecture, it features 32 Xe cores and 256 XMX engines, designed to accelerate AI, rendering, and complex visualization workloads.
- Massive 32GB GDDR6 VRAM: Equipped with 32GB of high-speed GDDR6 memory on a 256-bit bus, running at 19 Gbps, which allows for handling large AI models and complex datasets locally.
- High-Performance Engine Clock: Delivers an engine clock of 2540 MHz, providing the compute power needed for demanding professional applications and AI inference.
| Setting to test | Why it can matter | How to test it |
|---|---|---|
| Output resolution | Rendering more pixels increases GPU workload. | Try the next lower supported resolution only if the loss of clarity is acceptable. Keep the display mode and scene identical for comparison. |
| Render scale or resolution scale | Reduces the internal render resolution while preserving the display output. | Lower the scale in small steps and check fine geometry, text and motion for unacceptable softness. |
| Ray tracing | Ray-traced lighting, reflections and shadows can be among the heaviest effects in a title. | Disable or lower ray-tracing options individually. Compare the same area with identical lighting conditions. |
| Reflections, global illumination and volumetric effects | These effects can add substantial GPU work even when the overall preset looks similar. | Reduce the highest-cost effect first instead of dropping every option to Low. |
| Shadow quality and distance | Higher resolution and longer shadow distances increase rendering and memory work. | Lower quality or distance one step and inspect moving shadows and contact detail. |
| Texture quality | Textures mainly affect memory capacity and streaming. Lowering them may not raise FPS when the GPU is compute-limited. | Change this after heavier effects. Watch telemetry for memory pressure and texture pop-in. |
Do not assume that lowering every option produces the best experience. A small reduction in one expensive effect can preserve more image quality than using a low preset, and some options affect CPU time more than GPU time. If GPU utilization is already low, reducing GPU quality settings may not address the actual bottleneck.
Should you enable XeSS?
XeSS is available only in games that integrate it. In a supported title, open the display or graphics settings, find the upscaling option and select XeSS. Intel’s support guidance describes the path as: “If your game supports XeSS, navigate to its display or graphics settings look for the upscaling options and select ‘XeSS’ to enable it.” The wording and location vary by game.
Choose a XeSS mode for your output resolution
| XeSS choice | Trade-off | Best way to decide |
|---|---|---|
| Quality | Preserves more image detail but generally provides less performance headroom than more aggressive modes. | Start here at the display’s native resolution, then check motion, foliage and fine text. |
| Balanced or intermediate mode | Moves further toward performance with a greater reconstruction compromise. | Use when Quality does not provide enough headroom and the image remains acceptable in motion. |
| Performance | Uses a more aggressive internal resolution and can provide more performance at a greater image-quality cost. | Consider it for demanding resolutions or effects, but inspect shimmering, ghosting and softness. |
These labels are not a promise of a particular FPS increase. The useful mode depends on the game’s implementation, your Arc model, output resolution, other effects and personal tolerance for reconstruction artifacts. Test XeSS with the same scene and avoid comparing a static menu with active gameplay.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Use Intel Graphics Software profiles and telemetry to validate a change
- Open Intel Graphics Software and select the game’s application profile, if it is listed.
- Record the current driver version and the game’s graphics settings.
- Run a repeatable route or built-in benchmark for long enough to include the problem area.
- Note FPS, GPU memory use, clock speed, temperature and voltage from the live telemetry.
- Change exactly one game setting or XeSS mode.
- Repeat the same route under the same resolution, display mode and scene conditions.
- Keep the change only if it improves the target problem without unacceptable image quality, input latency or frame-time behavior.
Average FPS and smoothness are different measurements. A higher average can still feel worse if frame times contain severe spikes. Use the same route and pay attention to traversal stutter, shader-compilation pauses and dips in crowded areas. Intel’s software exposes live readings, but the figures are not a controlled benchmark of every Arc GPU.
Rank #3
- OC Edition Boost Clock: 2760MHz
- TORN Cooling 2.0
- Metal Backplate
- Blue Breathing Light
- Graphic card sag bracket
Do V-Sync, Smart VSync or Smooth Sync increase FPS?
Frame-delivery options govern synchronization and tearing. They do not inherently make the GPU render more frames. Choose among them based on your display and the game’s behavior.
| Option | Documented behavior | Use it when |
|---|---|---|
| Application Choice | V-Sync follows the game’s own graphics setting. | You want the title itself to control synchronization or need to preserve its tested behavior. |
| Smart VSync | Intel says it enables V-Sync when the application’s render rate exceeds the display refresh rate and disables it when render rate falls below that rate. | You are troubleshooting tearing or the interaction between render rate and refresh rate, and the game’s own V-Sync behavior is unsuitable. |
| Smooth Sync | Intel describes a dithering filter that blurs distracting tearing. | Your display lacks VESA Adaptive-Sync and tearing is more distracting than the filter’s visual compromise. |
Variable-refresh-rate or Adaptive-Sync capability is a display feature, not an Arc rendering-performance mode. It can make changing frame rates look smoother, but it does not remove the workload of rendering the frames. If latency matters, compare the game’s own V-Sync, driver synchronization and refresh-rate limits in the same scene rather than enabling every option at once.
Use Game Compatibility only for a specific problem
Intel’s Game Compatibility feature applies tested solutions to particular game problems, mostly functional issues such as crashes or corruption. Intel states that, when enabled, the solution is applied without requiring a full driver update. The feature is not a global DX12 performance preset.
What the compatibility levels mean
- Recommended: Intel’s normal suggested solution level for the detected issue.
- Basic: A less complex set of changes.
- Advanced: More involved changes that may have broader side effects.
Intel warns that compatibility changes can affect performance. Record the original state, apply the least invasive level relevant to the reported issue, and test the game again. If the problem is gone but performance worsens, restore the original setting and report the behavior through the game or Intel support channel. Do not enable an aggressive level globally in the hope of gaining FPS.
Rank #4
- System Compatibility Note: 2‑slot ITX card, 169.9x123.5x39.2mm, single 8‑pin power, recommended 500W PSU. Verify chassis clearance before purchase.
- Dedicated Support: Please contact us directly through Amazon for any product questions or assistance you may require.
- Intel Arc A380 GPU: Powered by Intel Xe architecture with 6GB GDDR6 on 96‑bit bus – ideal for compact gaming, HTPC, and media builds.
- 2250MHz GPU Clock: Factory overclocked core delivers solid performance for esports titles and everyday creative tasks.
- Small Form Factor ITX Design: Compact 2‑slot card fits easily into mini‑ITX and small form factor cases without sacrificing performance.
Why game-specific driver notes matter: the Apex Legends example
Intel has published an Apex Legends support article describing a DX12 low-GPU-usage and low-FPS case with Resizable BAR enabled, along with a launch-option workaround. That workaround is specific to the documented Apex Legends symptoms; it is not a general Arc or DX12 launch option.
Intel’s May 13, 2026 driver notes also list an Apex Legends DX12 corruption issue. The two notices illustrate why you should check the driver release that is installed and the latest notes before copying a workaround. A setting that addresses one title’s bug can be irrelevant or harmful in another game. Resizable BAR, launch options and compatibility controls should therefore be changed only when Intel or the game’s developer documents them for your exact symptom.
A practical order for troubleshooting a slow DX12 game
- Verify the baseline: Confirm the game is using the Arc GPU, record the driver version and reproduce the slowdown in a repeatable scene.
- Check current notes: Look for a listed issue or workaround for that game and driver before changing global settings.
- Lower one heavy effect: Test ray tracing, volumetrics, reflections, shadows or render scale before reducing everything.
- Test XeSS: If the game supports it, start with Quality and compare more aggressive modes only if needed.
- Measure with a profile: Use Intel Graphics Software telemetry and preserve the game-specific settings in its profile.
- Address synchronization separately: Choose Application Choice, Smart VSync, Smooth Sync or the game’s VRR configuration to solve tearing or pacing—not to promise higher rendering throughput.
- Apply compatibility controls only for symptoms: Use Game Compatibility for a documented crash, corruption or functional problem and retest after each level.
- Undo changes that do not help: A lower setting that produces no measurable improvement is not worth its image-quality cost.
Common mistakes that make DX12 tuning harder
- Changing several options together: You cannot tell which change helped or caused a new artifact.
- Comparing different scenes: A quiet corridor and a crowded outdoor area do not provide a valid before-and-after test.
- Confusing tearing with low FPS: Synchronization settings change presentation, not the amount of rendering work.
- Expecting XeSS in every game: The option appears only when the game includes XeSS support.
- Copying an old Arc Control menu path: Current Intel Graphics Software and legacy Arc Control do not expose identical interfaces.
- Using compatibility levels globally: Intel designed Game Compatibility for tested, game-specific problems and warns that performance can change.
- Quoting a universal percentage gain: Intel’s materials do not establish one DX12 FPS increase that applies to every Arc GPU and game.
What result should you expect?
Expect a decision based on your game and display, not a guaranteed number. Lowering a costly effect or render scale can provide more GPU headroom; XeSS can trade reconstruction quality for performance when supported; synchronization options can improve tearing or pacing; and compatibility controls can resolve a documented functional issue. None is a universal fix.
The most defensible Arc DX12 workflow is to keep the game-specific change that improves the repeatable workload, preserve it in an Intel Graphics Software profile, and leave unrelated global controls alone. Recheck the game’s driver notes after a driver update because a workaround may become unnecessary or be replaced.
Quick Recap
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.
