Summary
Assets.digest.verse is regenerated on every Verse compile and includes every asset in the project’s Content folder that qualifies for Asset Reflection — there is currently no way to exclude specific paths/folders from this generation. On projects with a large asset count, this causes the digest file to balloon in size, which slows down Verse compilation and LSP semantic analysis (error/warning turnaround in VS Code).
In our case, the project has 1,200+ assets (materials, meshes, textures, etc.), and Assets.digest.verse has grown to the point where it is a genuine productivity bottleneck for the team. Most of these assets are never referenced from Verse code at all — they’re purely visual/level-design content — but they’re still reflected into the digest because EnableVerseAssetReflection is an all-or-nothing toggle at the project (.uplugin) level, with no folder-level granularity.
Please select what you are reporting on:
Verse
What Type of Bug are you experiencing?
Assets
Steps to Reproduce
- Create a UEFN project with Asset Reflection enabled (
EnableVerseAssetReflection: true). - Import/create 1,000+ assets (materials, meshes, textures) across multiple Content subfolders.
- Add at least one Verse file and compile.
- Observe the size of the generated
Assets.digest.verseand the time taken for Verse compilation / LSP error-checking in VS Code.
Expected Result
Creators should be able to designate which Content paths are included in Asset Reflection (e.g. via a per-folder flag, a .uplugin exclusion list, or an ignore file), so only assets that are actually meant to be referenced from Verse are written into the digest — not the entire Content tree.
Observed Result
All eligible assets in the project are reflected into Assets.digest.verse regardless of whether they are ever used in Verse code. With 1,200+ assets, the digest file has grown up to 10MB (depends on how many parameters per material you have), which noticeably increases Verse compile time and LSP semantic analysis time (VS Code takes longer to surface errors/warnings).
Platform(s)
Windows
Additional Notes
This is not a new issue — digest size/performance has been reported before, and this specific request (path-level exclusion) has also been raised separately without a response yet:
- Related open feature request: [Request] Creators can filter the paths of the assets generated by Verse in the digest
- Related prior performance report: Verse Server - Major Performance Issue - Assets.digest.verse Code Analysis
A path-exclusion mechanism would directly address both the compile-time and LSP-performance impact as project asset counts scale, without removing Asset Reflection as a whole.