Troubleshooting
Find the right next step for installer, engine-version, scan-scope, and report problems.
Start by identifying whether the problem is installation, compatibility, scope, or runtime evidence.
#The installer does not start
The Windows installer is unsigned. Confirm that you downloaded it from the Framegain download page and review Windows’ publisher warning before choosing whether to run it.
#Framegain is not in the editor
Close the editor, confirm that the plugin is under YourProject/Plugins/Framegain/, and reopen the project. Check that the plugin build matches Unreal Engine 5.7 or 5.8.
#The result is empty
Confirm the target preset and scan scope. An empty result means no supported check crossed its threshold in that scope; it is not a proof that runtime performance is healthy.
#The estimate and PIE result disagree
That is an evidence boundary, not necessarily a failure. The scan estimates from project data; the PIE benchmark measures one runtime scenario. Keep both contexts when deciding what to do next.
#A fix needs to be undone
Use the manifest created for the applied batch. If the project state is unclear, stop making further changes and contact support with the manifest and relevant log.