Develop

Forward Shading Renderer

Updated: Apr 14, 2026

Overview

Unreal Engine provides a forward shading renderer optimized for VR. The forward renderer is the recommended rendering path for Meta Quest development, and the Meta XR Project Setup Tool also recommends forward shading for PC-VR applications connected through Meta Link. Quest devices use the mobile forward renderer by default, and the majority of Meta sample projects (13 out of 19) configure forward shading explicitly.

Forward renderer vs deferred renderer

The primary advantage of the forward renderer is that it is substantially faster than the deferred renderer. The forward renderer outputs lit pixels directly, whereas the deferred renderer outputs material properties to a set of buffers, and then reads them back to apply lighting in a separate pass.

Because the forward renderer does not render to intermediate buffers, it can take advantage of multi-sample anti-aliasing (MSAA). MSAA increases image sharpness and can provide significant savings in GPU utilization compared to temporal anti-aliasing (TAA).

Not all features from the deferred renderer are available in the forward renderer, but many of these features require trade-offs that disproportionately impact VR development. For example, screen space effects may introduce stereo disparities that can be uncomfortable for users.

Enable forward shading

Forward and deferred rendering are configured through standard Unreal Engine rendering settings, not through Meta XR Plugin-specific settings.

Quest (mobile)

Quest devices use the mobile forward renderer by default. To verify or change this setting:

Go to Edit > Project Settings > Engine > Rendering > Mobile.

Set Mobile Shading Path to Forward.

The Meta XR Project Setup Tool recommends this setting automatically for Quest targets.

PC-VR

For PC-VR applications using Meta Link:

Go to Edit > Project Settings > Engine > Rendering > Forward Renderer.

Enable Forward Shading.

The Meta XR Project Setup Tool recommends this setting automatically for PC-VR targets.

Configure MSAA

MSAA is the recommended anti-aliasing method for Quest applications and requires forward shading to be enabled. The Meta XR Project Setup Tool recommends 4x MSAA for all Quest devices.

To configure MSAA:

Go to Edit > Project Settings > Engine > Rendering > Mobile.

Set Mobile Anti-Aliasing Method to MSAA.

Set MSAA Sample Count to 4.

Meta sample projects commonly set these three console variables together:

r.MobileMSAA=4

r.Mobile.AntiAliasing=3

r.MSAACount=4

Note: r.MobileHDR=False is typically paired with forward shading for Quest development. All Meta sample projects that use forward shading also disable Mobile HDR.

Feature trade-offs

The forward renderer does not support all features available in the deferred renderer. Consider the following when choosing a rendering path:

Nanite: Requires the deferred renderer. Not available with forward shading enabled.

Lumen: Requires the deferred renderer. Not available with forward shading enabled.

Screen space effects: Some screen space effects may introduce stereo disparities in VR. These effects are generally unavailable or limited in the forward renderer.

Foveated rendering: Both Fixed Foveated Rendering (FFR) and Eye Tracked Foveated Rendering (ETFR) are compatible with the forward renderer. Foveated rendering uses variable rate shading and is agnostic to the forward vs deferred rendering path.

For more information on forward shading in Unreal Engine, see Epic’s Forward Shading Renderer⁠ documentation.

Rendering — Overview of rendering considerations for Meta Quest

Using Fixed Foveated Rendering — Configure FFR levels for GPU savings

Eye Tracked Foveated Rendering — Use gaze-based foveation on supported devices

Fork engine performance — Performance optimizations in the Meta fork, including dynamic local lighting options for the forward renderer