Our team is currently working on a project in UEFN with thousands of assets, and Verse is generating an Assets.digest.verse for it. The problem is that this file is almost 10,000 lines of code, and it slows the Verse server (compiler) down immensely. My guess is Verse is running code analysis on this file as well, which it shouldn’t, considering it should be a read-only digest file.
When writing Verse code on custom devices, it can take VS Code almost 2 minutes or more to generate errors or warnings. I compared this to a new project with no Assets.digest.verse and the code analysis was almost instantaneous.
If this could please be addressed, I’d appreciate it. It seems as if the Assets.digest.verse is being generated because scriptable game objects (material, texture_2d, etc) will be supported in the future. But, given this functionality is not yet supported by Verse and the digest files are not writable, there should be no need for the Verse compiler to run code analysis for this file.
I’ve tried to exclude the Assets.digest.verse within the VS Code workspace settings but it doesn’t seem to fix the performance hit.
