Course contentsShow
← Unreal Engine Game Development
Lesson 805 of 88011. Performance Profiling and OptimizationFree lesson

Optimizing Asset Footprint Through Texture Group Configuration

Learners will configure texture LOD biases and compression settings to effectively manage VRAM usage across different hardware performance tiers.

In this lesson, you will learn how to leverage DefaultTextureLODSettings.ini and Texture Groups to dynamically scale asset fidelity based on hardware performance tiers.

The Strategy of Texture Groups

While we’ve previously discussed managing texture streaming pools and mipmap chains, those are global settings. To truly optimize your VRAM footprint, you must define Texture Groups. These groups allow you to categorize textures (e.g., World, Character, UI, Effects) and apply specific compression and LOD rules to each, ensuring that a background rock doesn't consume the same VRAM budget as a hero character’s face.

Configuring Texture Groups

You can define these rules in your project's DefaultDeviceProfiles.ini or via the Texture Group setting inside each UTexture asset. By grouping assets, you can force lower resolutions or more aggressive compression on lower-end devices without manually adjusting every texture.

For example, you might adjust the LODBias for the World group to shrink VRAM usage on mobile platforms:

[TextureGroup.World]
LODBias=1
MinLODSize=256
MaxLODSize=2048
CompressionSettings=TC_Default

In this snippet, LODBias=1 effectively skips the highest-resolution mipmap level globally for any texture assigned to the World group. This is a surgical way to sacrifice a small amount of visual sharpness in exchange for significant VRAM headroom.

Scaling Across Tiers

The true power of this system is the integration with Device Profiles. By setting up a BaseDeviceProfile and then overriding specific Texture Groups in a Mobile or LowEnd profile, you create an automated hierarchy. When the game detects the user’s hardware, it applies these profiles, automatically dropping the MaxLODSize for high-memory textures on weaker GPUs.

This prevents the engine from loading textures that exceed the hardware's capacity, keeping the Texture Streaming Pool from overflowing and causing hitches or driver crashes. Always audit your VRAM usage in the Statistics window (Ctrl+Shift+Comma) after applying these group changes to ensure your budget is effectively balanced across all target performance tiers.

Key Takeaway: Use Texture Groups to apply uniform LOD biases and compression constraints, allowing you to scale visual fidelity and VRAM footprint automatically across different hardware tiers without manual asset-by-asset updates.