The best starting point after Half-Life: Alyx’s October 2026 foveated-rendering patch is to update the game, enable Foveated Rendering if your GPU and rendering backend qualify, and judge the result in a repeatable gameplay scene. Then tune SteamVR’s render resolution, Alyx’s Fidelity and Texture Quality separately, and your headset refresh target if the GPU remains overloaded. There is no universal FPS percentage or single Ultra/Low preset: Alyx dynamically changes effective resolution, so extra headroom may become a sharper image instead of a higher displayed frame rate.
At a glance
| Name | Best for | Key spec | Platforms | Checked |
|---|---|---|---|---|
| Foveated Rendering | First performance check on a compatible PC | Toggle is off by default; can increase rendering performance | PC VR; Windows Direct3D 11 or Vulkan, Linux Vulkan | Oct 2026 |
| SteamVR Render Resolution: Auto | Let SteamVR choose a starting resolution | SteamVR Settings > Video > Render Resolution | SteamVR PC VR | Oct 2026 |
| Lower render resolution | GPU-bound systems that still miss the target | Reduce resolution only after trying Auto | SteamVR PC VR | Oct 2026 |
| Low Fidelity, then Texture Quality | Diagnosing Alyx scene-quality pressure | Fidelity and Texture Quality are independent controls | Half-Life: Alyx PC VR | Oct 2026 |
| 90 Hz refresh test | Valve Index systems limited by the GPU | Valve suggests testing 90 Hz rather than a higher target | Valve Index PC VR | Oct 2026 |
What changed in the 2026 Alyx updates?
Two separate releases matter. Valve’s September 14, 2026 update added native Steam Frame support, including standalone foveated rendering and other headset-specific changes. That does not mean every desktop PC VR setup receives Steam Frame’s native depth-reprojection work.
The October 26, 2026 update added the supported desktop-PC Advanced Performance > Foveated Rendering toggle. Valve’s release notes describe it only as “Can increase rendering performance,” which is a conditional capability statement rather than a measured FPS promise. The announcement also records October 28 fixes for an AMD regression and visual glitches affecting decals and splatters, so the post-patch state should be treated as the updated build, not the original October 26 release. See Valve’s current announcements at the Half-Life: Alyx news page.
How do I turn on Foveated Rendering?
On a supported PC, open Options/Settings > Performance > gear icon > Advanced Performance > Foveated Rendering. The switch starts off. Enable it, restart only if the game requests one, and assess it in gameplay rather than in the title menu.
- Update Half-Life: Alyx through Steam so the October 2026 desktop feature and subsequent fixes are present.
- Start the game and open Options/Settings.
- Choose Performance, select the gear icon, and open Advanced Performance.
- Turn on Foveated Rendering when the control is available.
- Load a repeatable gameplay location and note smoothness, image sharpness and any artifacts before changing another setting.
Valve’s linked PC guide documents the feature and its hardware rules at the foveated-rendering guide.
Which GPUs and rendering backends support the toggle?
The patch-linked guide lists NVIDIA GTX 16-series and RTX 20-series or newer, AMD RX 6000-series or newer, and Intel Arc A-series or newer. The backend matters as much as the model.
| System path | Supported route described by the guide | What to do |
|---|---|---|
| Windows with a listed NVIDIA card | Direct3D 11 normally supports the listed NVIDIA cards | Check the in-game menu first; do not add a launch option unless you have a specific reason. |
| Windows with a listed AMD card | Vulkan is required for the feature | In Steam Library, right-click Alyx > Properties > General > Launch Options, enter -vulkan, restart the game, and check Advanced Performance again. |
| Windows with a listed Intel Arc card | Vulkan is required for the feature | Use the same -vulkan launch option and restart before checking the menu. |
| Linux | Vulkan is the default rendering path | Check the toggle after updating; the guide does not require a separate Windows-style backend switch. |
The shorter Valve announcement names NVIDIA and AMD, while the linked guide supplies the fuller Intel Arc qualification. A supported card does not guarantee a particular frame rate, and an unsupported or incorrectly selected backend can hide the control.
Why is Foveated Rendering missing in Half-Life: Alyx?
A missing control usually means the GPU/backend combination does not meet the guide’s requirements, or Windows is using Direct3D 11 on an AMD or Intel card that needs Vulkan. It is not evidence that you need a separate download.
- Check the GPU generation. The documented threshold is GTX 16 or RTX 20 and newer for NVIDIA, RX 6000 and newer for AMD, and Arc A-series and newer for Intel.
- Check the backend. On Windows AMD and Intel systems, add
-vulkanin the game’s Steam launch options, restart, and look in the same Advanced Performance menu. - Check the game build. The desktop toggle arrived in the October 26 update; update Steam before troubleshooting.
- Do not confuse Alyx’s minimum requirement with foveation support. The Steam store lists a GTX 1060 or RX 580 with 6 GB of VRAM as the game’s minimum requirement, but that is not the new foveation compatibility threshold. The current listing is Half-Life: Alyx on Steam.
Do I need eye tracking for Alyx foveated rendering?
No. The guide states that Foveated Rendering can be enabled with any VR headset when the PC meets the GPU and backend rules. Without eye-tracking data, the game can use fixed foveation centered on the view.
Gaze-following foveation is a separate path: the headset and its SteamVR driver must actually provide eye-tracking data to the game. Owning a headset that contains eye-tracking hardware does not establish that the data reaches Alyx, and OpenVR compatibility layers can prevent the integration. Treat eye tracking as optional, not as a prerequisite for the desktop toggle.
Should I use Vulkan on an AMD or Intel GPU?
Use Vulkan on Windows when you have a qualifying AMD RX 6000-series-or-newer or Intel Arc A-series-or-newer card and want the foveation control; the guide specifies Vulkan for those paths. Add -vulkan under Steam Library > Half-Life: Alyx > Properties > General > Launch Options, restart Alyx, and then inspect the menu.
That requirement establishes feature availability, not a universal performance ranking between Vulkan and Direct3D 11. Compare your resulting in-game smoothness with the previous setup rather than assuming Vulkan is always faster. Linux already uses Vulkan by default according to the guide.
What settings should I change first when the GPU is overloaded?
Change one variable at a time, starting with the controls that most directly reduce GPU work. Valve’s support guidance recommends SteamVR’s resolution controls, Alyx’s Fidelity diagnostic, independent texture adjustment, and a lower refresh target when appropriate.
- Record a baseline. In a repeatable gameplay scene, note the headset refresh target, SteamVR render resolution, Alyx Fidelity, Texture Quality, GPU, and whether Alyx is using Direct3D 11 or Vulkan. Record observations rather than treating the menu as a benchmark.
- Enable foveation first when supported. Return to Performance > gear icon > Advanced Performance and switch it on. Keep the other values unchanged for the first comparison.
- Set SteamVR resolution to Auto. Open SteamVR > Settings > Video > Render Resolution and try Auto. If the system still misses its target, reduce the resolution gradually.
- Use Low Fidelity as a diagnostic. In Alyx’s Performance menu, try Low Fidelity to determine whether overall scene quality is the main pressure point. Move upward gradually once the target is stable.
- Adjust Texture Quality separately. Texture Quality is independent of overall Fidelity, so lower it only when texture memory or scene detail is the limiting factor. Do not assume changing Fidelity also changed textures.
- Test the refresh target. If a Valve Index is GPU-bound at a higher refresh setting, Valve suggests testing 90 Hz. This is a target-setting experiment, not a promised frame-rate result.
- Recheck in the same gameplay scene. Menus can conceal the workload that causes reprojection or stutter. Use the same location and change only one control between comparisons.
Valve’s performance guidance is available at Steam Support’s performance FAQ.
Should SteamVR render resolution be Auto?
Auto is the sensible first setting because it lets SteamVR choose a starting render resolution for the headset and system. If Auto still leaves the GPU short of the target, reduce the resolution in stages and decide whether the improvement in consistency is worth the loss in image sharpness.
Resolution is separate from Alyx’s Fidelity and Texture Quality. A lower SteamVR value affects the whole rendered image, while the in-game controls let you investigate scene quality and textures independently. Keep a note of the value you used so a later comparison is meaningful.
Why didn’t FPS go up after the patch?
Alyx dynamically adjusts its effective resolution as performance headroom changes. Foveation can create headroom that the game spends on clearer rendering, so the displayed frame rate may remain near the same target while the image improves. An unchanged FPS counter therefore does not prove that the toggle failed.
Other limits can also dominate: a CPU-bound scene, a refresh target that already caps the presentation rate, or a resolution setting that leaves little room for the game’s dynamic system to react. Compare smoothness, dropped or reprojected frames and image quality in gameplay, not just a menu number. Valve’s release note supplies no universal percentage uplift, and the guide supplies no patch-wide measured result.
What does Alyx’s foveated image actually render?
The guide describes three regions: an inner area rendered at full resolution, a middle area with reduced shading, and an outer area rendered more coarsely. Its documented quarter and sixteenth fractions describe the rendering resolution assigned to those regions; they are not claims of four-times or sixteen-times FPS.
With fixed foveation, the high-detail center follows the configured view center rather than your gaze. With functioning eye tracking, the high-detail region can follow where you look, but driver and compatibility-layer support determine whether Alyx receives that data. The practical trade-off is additional GPU headroom in peripheral regions versus possible visibility of reduced detail outside the center.
Should I change the developer foveation variables?
Not at first. The guide says its defaults should work for most people and labels console variables as advanced tinkering. Start with the supported menu toggle and normal SteamVR/Alyx controls so you can recover easily if image quality becomes distracting.
If you deliberately explore the console, the guide identifies fove_level values lo, med, hi (the default), and ultra. The effective presets change when eye tracking is unavailable, so “ultra” is not a universal best choice. Increase quality only after confirming that the current setting is stable, and judge the peripheral image in actual gameplay.
How can I make a controlled comparison without dynamic resolution?
For a temporary comparison only, the guide gives Steam launch options +vr_fidelity_level_auto 0 +vr_fidelity_level 3 to disable Alyx’s dynamic resolution and hold a fixed fidelity level. This can make two settings easier to compare, but it is not a permanent optimization.
- Close Alyx.
- Open Steam Library > Half-Life: Alyx > Properties > General > Launch Options.
- Enter
+vr_fidelity_level_auto 0 +vr_fidelity_level 3. - Run the same gameplay scene with one setting changed at a time.
- Remove both launch options when the comparison is complete so Alyx can resume dynamic resolution.
Do not turn a fixed-resolution comparison into a claim about the patch’s general FPS gain. It deliberately removes one of Alyx’s normal adaptive behaviors.
What should I do when a specific symptom appears?
| Symptom | Likely explanation | Next action |
|---|---|---|
| The toggle is absent on Windows AMD or Intel | The game is probably on Direct3D 11, while the guide requires Vulkan for those GPU families. | Add -vulkan in Steam Launch Options, restart, and verify the GPU generation. |
| The toggle is absent on an older card | The card may meet Alyx’s minimum game requirement but not the foveation threshold. | Check the documented GTX 16/RTX 20, RX 6000 or Arc A-series minimums before considering hardware changes. |
| FPS appears unchanged | Dynamic resolution may be spending new headroom on clarity, or another component may be limiting. | Compare the same gameplay scene and inspect smoothness and image quality, not only FPS. |
| The image looks soft everywhere | SteamVR render resolution may be too low, or Alyx may be using a low Fidelity setting. | Raise SteamVR resolution or Fidelity one step at a time after confirming the target is stable. |
| Peripheral detail looks distracting | Reduced-resolution outer regions are visible under the chosen foveation level or without gaze-following data. | Try a less aggressive fove_level only after the default menu setting is understood, and prioritize stable gameplay over a nominal preset. |
| AMD-specific glitches appear | The original October 26 build had an AMD regression; Valve recorded fixes on October 28. | Update Alyx fully before judging the current behavior. |
| Decals or splatters look wrong | Valve recorded visual fixes for those effects after the initial desktop release. | Confirm that Steam has installed the post-October 26 fixes. |
How these settings are prioritized
The order favors supported, reversible controls before advanced overrides. First comes the official foveation toggle and its GPU/backend check; next are SteamVR resolution and Alyx’s Fidelity and Texture Quality controls; finally come refresh-rate changes and developer variables. The choices account for the documented compatibility matrix, Valve’s performance guidance, Alyx’s dynamic-resolution behavior, image-quality trade-offs and the need to test in real gameplay without claiming a universal benchmark result.
FAQ
What happens to text and small objects with fixed foveation?
The center of the view receives the highest-detail treatment, while peripheral regions use reduced shading or resolution. Text that sits outside the center can therefore look less crisp until you move your view toward it; the exact visibility depends on the selected level, headset optics and SteamVR resolution.
Can Linux users enable the feature without adding a launch option?
The guide describes Vulkan as Linux’s default rendering path, so the Windows-specific -vulkan step is not normally needed. You still need a listed GPU and an up-to-date Alyx build for the menu control to appear.
Does Steam Frame’s September support change every desktop PC VR headset?
No. Steam Frame support was introduced in a September 14 update, while the desktop-PC Advanced Performance toggle arrived on October 26. Features described for Steam Frame, including native depth reprojection, should not be assumed on unrelated PC VR hardware.
Is the GTX 1060 or RX 580 a safe purchase target for foveated rendering?
No buying conclusion follows from Alyx’s minimum requirement. Valve’s store listing identifies those 6 GB cards for running the game at its minimum specification, whereas the foveation guide lists newer GPU families for the toggle; check the existing card and backend first.
Frequently Asked Questions
What happens to text and small objects with fixed foveation?
The center of the view receives the highest-detail treatment, while peripheral regions use reduced shading or resolution. Text that sits outside the center can therefore look less crisp until you move your view toward it; the exact visibility depends on the selected level, headset optics and SteamVR resolution.
Can Linux users enable the feature without adding a launch option?
The guide describes Vulkan as Linux’s default rendering path, so the Windows-specific -vulkan step is not normally needed. You still need a listed GPU and an up-to-date Alyx build for the menu control to appear.
Does Steam Frame’s September support change every desktop PC VR headset?
No. Steam Frame support was introduced in a September 14 update, while the desktop-PC Advanced Performance toggle arrived on October 26. Features described for Steam Frame, including native depth reprojection, should not be assumed on unrelated PC VR hardware.
Is the GTX 1060 or RX 580 a safe purchase target for foveated rendering?
No buying conclusion follows from Alyx’s minimum requirement. Valve’s store listing identifies those 6 GB cards for running the game at its minimum specification, whereas the foveation guide lists newer GPU families for the toggle; check the existing card and backend first.