Start Building

Your FPS already has solid gameplay and multiplayer; now it is time to level up the visuals so it looks as good as it plays. Unreal Engine 5’s Lumen and Nanite can give you cinematic lighting and dense geometry without the old bottlenecks, and a tuned post-process and material pass will make combat feel punchy and readable. This lesson walks you through enabling and tuning advanced graphics so your game looks portfolio-ready while staying performant.

By the end you will know how to use Lumen for global illumination, when and how to use Nanite, how to set up a post-process volume for your FPS, and how to add a few material touches that make weapons and impacts pop.

Why advanced graphics matter for FPS

In a first-person shooter, players constantly scan the environment for threats, cover, and objectives. Readability (clear shapes, contrast, and feedback) matters as much as raw fidelity. Good lighting and post-processing make silhouettes clear, highlight interactive objects, and sell impacts and explosions. Pushing graphics too far can hurt frame rate and readability; the goal here is a balanced, professional look that runs well on your target hardware.

Pro tip: Profile on your minimum-spec target (e.g. a mid-range GPU). It is better to ship with slightly conservative settings that scale up than to lock out part of your audience.

Step 1: Understand and enable Lumen (global illumination)

Lumen is UE5’s real-time global illumination and reflection system. It removes the need to bake lightmaps for many scenes and gives you soft, bounced light and accurate reflections that update as the level or time of day changes.

  1. Check project settings

    • Edit → Project Settings → Engine → Rendering. Under Default RHI, ensure you use Default or DirectX 12 (Lumen requires SM5+).
    • Under Global Illumination, set Dynamic Global Illumination Method to Lumen. Set Reflection Method to Lumen if you want Lumen to handle reflections as well (recommended for consistency).

  2. Scene setup

    • Lumen works with static and dynamic lights. Add a Directional Light (sun) and optionally Sky Atmosphere and Volumetric Cloud for an outdoor look. For interiors, add Rect Lights or Point Lights; Lumen will bounce their light.
    • Ensure your level has some reflection capture coverage or rely on Lumen for reflections; otherwise reflections may look default or flat.

  3. Tune for performance

    • Project Settings → Engine → Rendering → Lumen: Adjust Screen Trace Resolution and Hardware Ray Tracing (if enabled) to balance quality and cost. Start with defaults and lower if needed on minimum-spec hardware.
    • Use Lumen Scene quality (in the same section) to reduce how much geometry is considered for GI; lowering this can help in very dense levels.

Common mistake: Leaving Screen Space Global Illumination (SSGI) or old Lightmass enabled alongside Lumen can cause double cost or conflicting look. Use one GI method.

Step 2: Use Nanite where it helps

Nanite is UE5’s virtualized geometry system. It allows extremely high triangle counts for static meshes (e.g. environment art) with predictable performance, because only visible pixels are shaded and geometry is streamed at the right detail level.

  1. When to use Nanite

    • Enable Nanite on static meshes that are complex and do not need deformation: architecture, rocks, props, terrain. In the Static Mesh asset, check Enable Nanite (and rebuild if needed).
    • Do not use Nanite on: skinned characters, weapons held by the character, or anything that uses vertex deformation or morph targets. Use regular meshes for those.

  2. FPS-specific choices

    • Environment and level geometry: good Nanite candidates.
    • Player-held weapon: keep as a regular mesh; it is always on screen and often uses custom shaders or effects.
    • Enemies: typically skeletal meshes; no Nanite.
    • Projectiles and small VFX: usually simple meshes or Niagara; no need for Nanite.

  3. Performance

    • Nanite reduces draw calls and can improve CPU/GPU balance. If you see better performance after enabling it on large environment meshes, keep it; if a mesh is very simple, the overhead may not be worth it. Profile before and after.

Pro tip: Use Nanite on your biggest, most detailed static assets first. Leave hero props (weapons, key pickups) as standard meshes so you can use full material and animation features.

Step 3: Add a Post Process Volume for FPS feel

Post-processing ties the image together: bloom, color grading, contrast, and optional effects like vignette or film grain. For an FPS you want clarity first, then mood.

  1. Create a Post Process Volume

    • Place a Post Process Volume in your level (or use the one in your template). Set Unbound to true so it affects the whole level, or leave it bound and place it where you need different moods (e.g. interior vs exterior).

  2. Essential settings

    • Bloom: Keep it subtle so muzzle flash and explosions glow without washing out the scene. Intensity around 0.5–1.0 and a low Threshold often work.
    • Exposure: Use Auto Exposure with a reasonable min/max range so bright and dark areas are readable.
    • Color Grading: Slight Saturation and Contrast boost can make combat readable; avoid over-stylizing unless you are going for a specific look.
    • Vignette: A light vignette can focus attention toward the center (crosshair); keep it low so it does not feel claustrophobic.
    • Motion Blur: Optional; many competitive FPS players disable it. If you use it, keep Amount low so it does not obscure targets.

  3. Anti-aliasing

    • Temporal Anti-Aliasing (TAA) is usually on by default in UE5. It smooths edges; if you see ghosting on fast-moving weapons, tune TAA settings in Project Settings → Engine → Rendering or in the post-process Rendering Features.

Common mistake: Cranking bloom and exposure too high so that bright effects blind the player or dark corners become unreadable. Test in both daylight and dark areas.

Step 4: Improve materials for weapons and impacts

Small material tweaks can make weapons and hit reactions feel more impactful without rebuilding your art.

  1. Weapon materials

    • Add a subtle Fresnel or Edge Highlight so weapon silhouettes read well against varied backgrounds.
    • Use Normal and Roughness maps to break up flat surfaces; even simple noise can help.
    • If you use Emissive for screens or lights on the weapon, keep intensity moderate so it does not blow out the image.

  2. Impact and decals

    • Decals (bullet holes, scorch marks) should use materials that respect Roughness and Normal of the surface they project onto; use Decal material domain and DBuffer or Deferred Decal blend modes.
    • Slight Emissive on impact decals can sell the “hot” or “fresh hit” look for a frame or two.

  3. Performance

    • Avoid expensive material operations (many texture samples, complex math) on objects that are drawn every frame in the center of the screen (e.g. the first-person weapon). Prefer simpler shaders there and push complexity to environment or VFX.

Pro tip: Reference official Unreal content (e.g. Lyra or FPS samples) for weapon and impact material patterns; copy the structure and adapt to your art style.

Step 5: Lighting hierarchy for readability

FPS levels benefit from a clear lighting hierarchy: the most important areas (objectives, threats, pickups) should be slightly brighter or more contrasted so the player’s eye goes there.

  1. Key lights

    • Use your main Directional Light (or key light) to define time of day and overall mood. Add Rect Lights or Spot Lights in combat arenas to create pools of light and shadow (cover vs open).

  2. Accent lights

    • Place small Point or Spot Lights near health packs, ammo, or objectives so they read as “important” without a huge HUD arrow.
    • Muzzle flash and explosions already draw the eye; ensure they are not the only bright spots or the scene will feel flat between firefights.

  3. Lumen and accents

    • Lumen will bounce these lights; you do not need to fill every corner with extra lights. A few well-placed accents plus Lumen often look better than an over-lit level.

Troubleshooting

Scene is too dark or too bright

  • Adjust Auto Exposure range in the Post Process Volume. Ensure you do not have multiple overlapping volumes with conflicting exposure. Check that your main light (e.g. Directional Light) has a reasonable Intensity (often 3–10 for a sun).

Lumen looks noisy or flickers

  • Increase Lumen quality in Project Settings (Screen Trace Resolution, etc.) or reduce camera motion. In some cases enabling Hardware Ray Tracing for Lumen (if supported) can stabilize reflections.

Weapon or HUD looks blurry

  • TAA can soften the center of the screen. Ensure your first-person weapon and UI use appropriate resolution; you can also tune TAA Sharpening in rendering options if available.

Low FPS after enabling Lumen/Nanite

  • Profile with Unreal Insights or the built-in GPU Profiler. Disable Lumen or Nanite on the heaviest meshes and see the delta. Scale Lumen Scene or shadow resolution as needed for your target hardware.

Mini challenge – graphics checklist

Before moving to testing and QA:

  • [ ] Enable Lumen for global illumination (and reflections if desired) and confirm your main level looks correct.
  • [ ] Enable Nanite on at least one large static mesh (e.g. a building or terrain) and verify it renders and performs well.
  • [ ] Configure a Post Process Volume with bloom, exposure, and color grading so bright and dark areas are readable.
  • [ ] Add one material improvement to your weapon or impact decals (e.g. edge highlight or emissive pulse).
  • [ ] Run the level on your minimum-spec target and hit your frame-rate goal (e.g. 60 FPS).

Recap and next steps

You used Lumen for real-time global illumination and reflections, Nanite for high-detail static geometry, Post Process Volume for bloom, exposure, and color grading, and material tweaks for weapon and impact clarity. Together these give your FPS a more polished, portfolio-ready look while keeping performance in check. In the next lesson you will focus on testing and quality assurance so the game is stable and ready for beta and launch.

For deeper dives, see Unreal Engine 5 Lumen documentation and Nanite virtualized geometry. For performance tuning, revisit Lesson 12: Performance Optimization & Scalability.

Frequently asked questions

Do I need a ray-tracing GPU for Lumen?
No. Lumen’s default software ray tracing runs on a wide range of hardware. Hardware ray tracing is optional and can improve quality and stability on supported GPUs.

Should every static mesh use Nanite?
No. Use Nanite on complex, high-poly static meshes (environment, props). Keep character meshes, weapons, and deforming objects as regular meshes.

Why does my FPS look washed out?
Check Auto Exposure (expand the range or disable for testing) and Bloom (lower intensity and raise threshold). Too much bloom or a narrow exposure range can wash out the image.

Can I mix baked lighting with Lumen?
For new UE5 projects, Lumen is usually the primary GI solution. Mixing with fully baked Lightmass can be done but is more advanced; for this course, stick to Lumen for consistency.

Found this useful? Bookmark it and share a before/after screenshot of your level with the community.