dhkatzandClaude Opus 5.5 065c7e9300 Never make the client wait for drawing, or hold up its steps ...

The renderer process now takes each view's chunks on a thread of its own as
they come, and draws the newest frame on its main thread: the client no longer
waits for the previous frame to be drawn (on a VM, 22 of a frame's 25 ms).

The adapter records the client's steps (SceneViewer::step, by replacing its
entry in the exported IFrameListener vtable, after checking it), and the frame
pacer doesn't ask for a frame that wouldn't end before the next step is due: a
late step made the client catch up two at once, which showed as hitches. While
the renderer process covers the view, the client's renderer doesn't begin or
present frames, which could wait for the display.

The engine's stats now include the time in the client renderer's methods.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-10-28 21:30:46 -07:00

..

architecture.md

Never make the client wait for drawing, or hold up its steps

2026-10-28 21:30:46 -07:00

interface.md

Draw render targets in the renderer process

2026-10-28 19:09:48 -07:00