In this lesson, you will learn how to leverage UInvalidationPanel to drastically reduce the CPU overhead of complex, static, or infrequently changing UMG widget hierarchies.
Understanding the Invalidation Workflow
Normally, Unreal’s Slate rendering engine performs a "pre-pass" on every widget every frame to determine if any geometry needs to be rebuilt. If you have a screen full of icons, text, and nested containers, this pre-pass becomes a significant bottleneck.
An Invalidation Panel acts as a cache for its children. When you wrap a set of widgets in an Invalidation Panel, the engine takes a "snapshot" of the rendered output. As long as nothing inside that panel changes—such as position, opacity, or content—the engine skips the expensive layout and paint calculations for those children, simply drawing the cached texture instead.
Implementing the Optimization
To use this, simply wrap your complex UI elements (like a static inventory grid or a character stat panel) inside an InvalidationPanel widget in the UMG designer.
If you need to trigger a redraw because of a dynamic update, you can invalidate the panel manually in C++:
// In your custom widget class
void UMyWidget::UpdateStatDisplay()
{
// Logic to change text or images goes here...
// Tell the Invalidation Panel to refresh its cache
MyInvalidationPanel->InvalidateLayoutAndVolatility();
}
When to Use It
It is tempting to wrap your entire HUD in an Invalidation Panel, but be careful: if the contents of the panel change every frame (like a progress bar that updates its percentage constantly), the panel will invalidate and re-cache every single frame. This creates more overhead than if you hadn't used the panel at all.
Use Invalidation Panels for "mostly static" content. If a sub-section of your UI only changes when the player opens a menu or levels up, that is the prime candidate for this optimization. By isolating high-complexity, low-frequency UI elements, you ensure the Slate renderer spends its cycles on what actually moves rather than re-calculating pixels that have remained unchanged for seconds at a time.
Key Takeaway: Invalidation Panels optimize performance by caching the draw state of a widget tree, but they are most effective when applied to content that changes infrequently rather than content that animates every frame.