Reference
What is not checked
Understand which runtime behaviour and systems an asset-focused Framegain scan cannot prove.
An asset-focused scan cannot prove every cause of a slow frame. The following areas are outside the documented eight-check scope.
#Materials and shader complexity
Material graphs, shader complexity, and shader compilation behaviour require tools that observe rendering and compilation.
#Runtime-only work
Animation, audio, networking, Blueprint execution, and other code-driven work are not established by reading asset metadata alone.
#Streaming and memory behaviour
Runtime streaming, residency, and device-specific memory pressure need a runtime capture and the target environment.
Important
An empty Framegain result says only that the supported checks found no finding above their thresholds. It says nothing about the areas above.