feedback - not to call FrameInfoManager for standalone rendering

Author: z3moon

filament/src/FrameInfo.h

@@ -163,9 +163,9 @@ class FrameInfoManager {
     // call this immediately before "swap buffers"
     void endFrame(backend::DriverApi& driver) noexcept;
 
-    details::FrameInfo const& getLastFrameInfo() const noexcept {
-        // if pFront is not set yet, return front() but in this case front().valid will be false
-        return pFront ? *pFront : mFrameTimeHistory.front();
+    details::FrameInfo const getLastFrameInfo() const noexcept {
+        // if pFront is not set yet, return FrameInfo(). But the `valid` field will be false in this case.
+        return pFront ? *pFront : details::FrameInfo();
     }
 
     utils::FixedCapacityVector<Renderer::FrameInfo> getFrameInfoHistory(size_t historySize) const noexcept;

filament/src/details/Renderer.cpp

@@ -525,16 +525,8 @@ void FRenderer::renderStandaloneView(FView const* view) {
                         1'000'000'000.0 / mDisplayInfo.refreshRate),
                 mFrameId);
 
-        // This need to occur after the backend beginFrame() because some backends need to start
-        // a command buffer before creating a fence.
-        mFrameInfoManager.beginFrame(driver, {
-                .historySize = mFrameRateOptions.history
-        }, mFrameId);
-
         renderInternal(view);
 
-        mFrameInfoManager.endFrame(driver);
-
         driver.endFrame(mFrameId);
     }
 }