Common Loading Screen

Loading screens sit between the player and the game world. When maps are large, assets are streaming, or multiplayer sessions are connecting, that transitional space can frustrate players or pull them deeper into the experience. The CommonLoadingScreen Plugin treats this gap as a design surface rather than a technical holdover, giving developers a structured way to control what appears on screen while the engine works in the background.

Inspired by the Lyra Starter Game's Common Loading Screen, the plugin takes a system that was specific to a sample project and makes it available across earlier versions of Unreal Engine. It is built on Unreal Engine's Common UI framework, which means it integrates with the UI architecture rather than bolting on a separate widget layer. The package then offers a modular setup for managing splash screens, level transitions, and on-demand loading displays.

Splash, Transition, and On-Demand Loading Displays

The plugin covers three distinct loading scenarios. Splash and startup loading screens handle the initial moments when a game launches, establishing branding and tone before the player reaches the main menu. Level transition screens step in during scene changes, hiding the technical loading processes that occur when moving between maps.

The third mode, on-demand loading, gives developers explicit control beyond automatic transitions. Loading screens can be triggered via Blueprint or C++, which means they can be tied to specific gameplay events, server connections, or asset streaming operations rather than just map loads. This is where the plugin moves from a presentation tool into a gameplay-adjacent system. If a match requires a brief synchronization period, or if a large streamed sub-level needs to finish building before the player enters, a custom loading screen can display relevant information instead of a frozen frame.

Triggering Loading Screens via Blueprint or C++

Exposing loading screen control to both Blueprint and C++ opens the system to different team structures. Designers working in Blueprint can wire loading screens into gameplay logic, menu flows, or interaction events without touching code. Programmers can integrate the same triggers into deeper systems, such as server connection handlers or level streaming managers, using C++.

This dual approach also makes the plugin suitable for both single-player experiences and large-scale multiplayer titles. A single-player game might use on-demand loading for cinematic transitions or narrative beats. A multiplayer title might use it to mask connection times, matchmaking handshakes, or server-side preparation.

Using Loading Screens for Player Experience and Branding

A loading screen, when thoughtfully designed, does more than mark time. It can reduce perceived load times through animations, music, and UI feedback. It can present tooltips, game lore, or gameplay tips that teach mechanics without forcing a tutorial. It can reinforce a game's identity through branding, visuals, and storytelling, turning a wait into an extension of the game's tone.

The plugin positions all of this within a modular, customizable framework. Studios can define different loading screen styles for different contexts—a minimal branded splash for startup, an information-rich screen for long level transitions, or a context-sensitive display for multiplayer connections. Because the system is built on Common UI, it works within Unreal Engine's existing widget architecture rather than requiring a parallel UI pipeline.

Handling Dynamic Content and Streaming

Games with large maps and streamed assets rarely load in a single block. Levels arrive in pieces. Sub-levels stream in based on player position. Server connections complete asynchronously. The CommonLoadingScreen Plugin is designed to handle this dynamic content, bridging the gap between scenes while streaming operations continue in the background.

For multiplayer sessions specifically, the plugin can mask periods where the client is connecting to a server or waiting for the initial game state to synchronize. The loading screen keeps the player informed and visually anchored, which reduces confusion during connection sequences that might otherwise look like a hang or crash.

Common UI Foundation and Version Compatibility

The plugin is built on Unreal Engine's Common UI framework. This is a structural detail that shapes how it fits into a project. Common UI is Unreal Engine's system for building scalable, platform-aware user interfaces, and using it as a foundation means the loading screens share that architecture rather than fighting against it. Widgets, styling, and input handling stay within the framework's conventions.

Compatibility covers Unreal Engine 5 (UE5) and earlier versions. The original Lyra Common Loading Screen was tied to the Lyra Starter Game, and this plugin extends that functionality to projects running on older Unreal Engine versions. That makes the system available to titles that cannot or will not migrate to the latest engine release but still want a polished, modular loading screen setup.

Documentation and Support Pipeline

Full documentation and a setup guide accompany the plugin, covering integration and configuration. A demo and overview video are available for developers who want to see the system in action before integrating it. Product support requires ownership verification, and support hours and contact information are published alongside the help resources.

The plugin is tagged as a Widget and Loading Screen system with Blueprint integration, which reflects its primary interaction points. Developers familiar with Common UI will find a familiar widget-based workflow, while those coming from a traditional UMG setup will encounter the framework's specific patterns for styling and scaling.

Where This Fits in a Production

The CommonLoadingScreen Plugin occupies a specific layer in a game's presentation pipeline. It is not a content pack or a visual asset collection. It is a system for controlling when loading screens appear, how they are structured, and what they communicate during technical wait states. Projects that need consistent, branded loading behavior across startup, level transitions, and on-demand events can use it as a shared foundation rather than building separate solutions for each context.

For teams working on large-map games, streamed open worlds, or multiplayer titles with connection sequences, the plugin provides a structured way to turn a pause into a designed moment. Indie developers get a modular entry point that does not require building a loading system from scratch. Studios get a Common UI-based foundation that aligns with Unreal Engine's widget architecture and can be customized to fit a project's visual identity.

Explore Similar Assets

• Screen Space Fog Scattering
• Shader Compilation Screen - remove shader stutters
• MSC Screen & Camera Recorder
• FrameCapture - Screen Capture and Video Recorder
• Simple Screen Damage Indicator