[Depends on #8332] Integrate fgviewer
to the engine side
#8344
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR should be merged after #8332 is in.
In this PR, I intergrate the fgviewer to the filament engine side, right now the engine will update the framegraph info to the debug server every frame.
FrameGraph::getFrameGraphInfo
method to convert current state tofgviewer::FrameGraphInfo
fgviewer::DebugServer
member to theEngine
class and initialize it as the engine loop startsfgviewer::DebugServer
and unregister it as it gets terminatedRenderer::renderJob
afterFrameGraph
is compiled