Precompile your project's PSOs before gameplay so first-render frame spikes never reach the player — paced, memory-bounded, and one package for UE 5.2 through 5.8.
Ship without the first-time shader hitches.
The first time your packaged game renders a given material on a given mesh, Unreal stops to build a graphics pipeline state (a PSO) for it. That build cost lands during play — the micro-freezes and frame spikes players call shader stutter. The editor never shows it, because the editor already holds those PSOs; your players hit it on a cold install.
Shader Precompiler Pro builds those pipeline states up front, the right way. Instead of loading your whole project and compiling it in one memory-busting pass, it walks your content a capped batch at a time and compiles against a per-frame time budget — releasing each batch and collecting garbage before the next. Resident memory stays flat whether your project is a vertical slice or a 200 GB open world, and the loading screen stays responsive the whole time. By the moment the player takes control, the pipeline states they're about to hit are already warm.
Wire it up once from Blueprint — get the subsystem, bind a progress event to your loading bar, call Start Precache — and you're done. No C++. Installed from Fab it's already compiled, so it drops straight into a Blueprint-only project.
Please see document:
Easy setup and proof video is coming soon...
Key features
Eliminates first-render shader hitches in packaged builds by precompiling PSOs ahead of gameplay.
Flat memory footprint — capped batches + garbage collection between them keep RAM steady on projects of any size.
Smooth loading screens — a per-frame millisecond budget time-slices the work so the UI never locks up.
Broad coverage, resolved automatically — static, instanced, spline, skeletal, cloth, Nanite, Niagara, landscape, hair/groom, geometry collection, Alembic, Cascade and Water vertex factories, across mobility and world-position-offset permutations.
Nanite-aware — precaches the Nanite vertex factory and per-material Nanite override materials.
Finishes when shaders are actually ready — coordinates the engine pipeline cache and the runtime precache queue, with a framerate-independent, configurable drain wait.
Skips work it doesn't need — a per-machine fingerprint (GPU, driver, RHI, OS, quality settings) means repeat launches start in milliseconds.
One package, seven engine versions — UE 5.2 → 5.8 from a single install; version-specific engine APIs switch on automatically.
Blueprint-first — no C++ required; full Project Settings page for targeting, memory, pacing and permutation control.
How it works (3 steps)
Install & enable the plugin, then open Project Settings → Plugins → Shader Precompiler Pro (defaults are production-ready).
Call Start Precache from your loading screen Blueprint and bind the progress / finished events.
Ship. The warm-up runs while the loading screen is up and reports back when the shaders are ready.
Supported versions & platforms
Unreal Engine: 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 5.8
Platforms: Windows (Win64), Mac, Linux, iOS
Project type: Blueprint or C++ — no compiler required for Blueprint-only projects
What's included
Full plugin (runtime module) with a Project Settings configuration page
Blueprint API: StartPrecache, StopPrecache, IsPrecaching, GetProgress, GetTotalAssets, GetProcessedAssets, GetCurrentAssetName, GetRemainingShaderCompiles, IsCacheReady, AreShadersReady, plus OnPrecacheProgress and OnPrecacheFinished events
User Guide and feature/version documentation
Commercial EULA, email support
FAQ
Do I need to know C++? No. Setup is entirely Project Settings + a few Blueprint nodes.
Will it work in my Blueprint-only project? Yes — the Fab build is precompiled for your engine version, so no Visual Studio or compiling is required.
Does it freeze the loading screen? No. Work is split into small batches against a per-frame time budget specifically so the loading screen stays smooth.
How much memory does it use? A bounded amount you control via Assets Per Batch — memory stays roughly flat regardless of project size.
Does it support Nanite / Niagara? Yes. Nanite is covered (vertex factory + override materials) and Niagara materials are warmed up, with no hard dependency on the Niagara plugin.
What about different hardware? The warm-up is fingerprinted per machine and settings, so each player warms up once for their setup and skips it on later launches.
Support
Questions before or after purchase: cagrikaganerkmen@gmail.com