Troubleshooting and operator guides

Guide 01

Slow editor FPS with Lumen and Nanite

Viewport hitching often comes from high-quality lighting and dense Nanite scenes left on while you iterate. Lower the editor path first; leave shipping scalability for package profiles.

1. 1

   Confirm the bottleneck

   Press Ctrl+Shift+, (or open the console with ~) and check stat unit / stat gpu. Note whether Game, Draw, or GPU dominates.

2. 2

   Drop viewport scalability while editing

   Use the viewport Scalability shortcut (or Editor Preferences) and set a Medium or Low preview. Avoid editing with Epic quality and ray-traced-looking Lumen settings on a laptop GPU.

3. 3

   Tune Lumen for the editor

   In Project Settings, search Lumen. Prefer Software Ray Tracing for daily work if Hardware Ray Tracing is unstable. Reduce Final Gather quality and reflection resolution for the editor-only path when needed.

4. 4

   Contain Nanite cost

   Hide unused Nanite layers, use levels or World Partition loading ranges, and avoid opening every high-poly set in one viewport. Temporary wireframe or unlit views help isolate mesh density issues.

5. 5

   Restart with a clean Derived Data Cache path

   If hitching spikes after plugin or engine upgrades, clear or relocate DDC to a fast local SSD. Network DDC stalls look like “engine lag” even when GPU load is low.

Guide 02

Packaging failures and Output Log triage

Most packaging failures are missing modules, platform SDK mismatches, or cook errors that already appear earlier in the Output Log. Read the first red error, not only the last line.

1. 1

   Match platform SDK to the engine version

   For Windows packages, confirm Visual Studio workloads and Windows SDK versions listed for your UE release. For Android/iOS, install the exact NDK/Xcode pair the engine release notes name.

2. 2

   Cook a Development build first

   Package Development before Shipping. Shipping strips asserts and can hide the real cook failure. Confirm maps are listed under Project Settings → Packaging → Maps to cook.

3. 3

   Disable unused plugins

   Third-party plugins that fail to load often stop packaging even if the editor opens. Turn off plugins you are not shipping, then regenerate project files if you use a C++ project.

4. 4

   Fix soft references and missing assets

   Search the log for “Failed to load” and “Couldn’t find file”. Redirectors left after moves are a common cook breaker. Resave offending assets in the Editor.

5. 5

   Clear Intermediate and Saved when stuck

   Close the Editor, delete project Intermediate and (carefully) Saved/Cooked folders, then reopen and package again. Keep a backup of Config if you customized ini files.

Guide 03

Disk space and launcher component downloads

The Epic Games Launcher pulls engine components on demand. There is no single fixed installer size. Plan free space for the engine, DDC, and temporary download caches.

1. 1

   Pick a drive before you install

   In the launcher, set the Unreal Engine install location to a drive with headroom. Changing drives later means another full download of selected components.

2. 2

   Install only the targets you need

   Skip Android, iOS, Linux, or Starter Content until you need them. Each target platform adds substantial component data.

3. 3

   Watch the download cache

   If installs fail mid-way with “not enough space,” clear launcher download caches and empty Recycle Bin / Trash. Temporary archives can briefly double disk use.

4. 4

   Prune old engine versions

   Remove engines you no longer open. Keep one prior version only if a live project still requires it for binary compatibility.

Storage estimates and platform buttons live on the download page.

Guide 04

Antivirus false positives on engine tools

Large toolchains, cook workers, and signed binaries sometimes trip heuristic scanners. Prefer exclusions for known Epic/Unreal paths over disabling protection entirely.

1. 1

   Confirm the download path

   Install through the Epic Games Launcher with an authenticated account. Avoid mirrored archives from unknown sources. See trust and security.

2. 2

   Check quarantine logs first

   If UnrealEditor.exe, UnrealBuildTool, or cook workers vanish after a scan, restore them from quarantine and note the rule name before adding exclusions.

3. 3

   Add folder exclusions carefully

   Exclude the engine install directory, your project folder, and the DDC path if your AV product allows path-based exclusions. Do not exclude the entire system drive.

4. 4

   Re-run Verify in the launcher

   After restoring files, use the launcher Verify action so missing binaries are repaired from Epic’s download set.

Guide 05

Windows 11 setup basics for UE 5.8

Windows 10 and Windows 11 64-bit are supported development platforms. A clean Windows 11 box still needs GPU drivers, Visual Studio workloads, and enough free disk before the first editor launch.

1. 1

   Update GPU drivers

   Install current Studio or Game Ready drivers from your GPU vendor. Outdated drivers commonly break Hardware Ray Tracing and crash on first Lumen scenes.

2. 2

   Install Visual Studio workloads

   For C++ projects (and many packaging paths), install Desktop development with C++ and the Windows SDK versions called out for your engine release.

3. 3

   Allow long paths if builds fail oddly

   Deep Intermediate trees can hit MAX_PATH. Enable long path support in Windows policy when build tools report truncated paths.

4. 4

   Create an Epic account and install the launcher

   Sign in, install Unreal Engine 5.8 from the Library tab, then create or open a project. Requirements tables sit on the download page.

5. 5

   Smoke-test with a template

   Open a First Person or blank template before importing a large production scene. Confirm PIE runs, then scale into Nanite/Lumen content.