6 Commits

Include renames

Author	SHA1	Message	Date
dhkatzandClaude Opus 5.5	2d9da249fa	Draw the whole 3D view in place of the client's renderer ... The full view is now the default. While the renderer process covers the whole view (Channel::covering, set after each frame it presents), the adapter skips the client's renderer's clears and draws, decided per frame; the client's renderer still gets state and resources, and draws again as soon as the renderer process stops covering the view. The client's window no longer gets WS_CLIPCHILDREN: the client draws when its window gets WM_PAINT, which a window entirely covered by clipped children never gets (it fell to about one frame a second). The flip model swap chain shows above the client's drawing anyway. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-28 18:14:17 -07:00
dhkatzandClaude Opus 5.5	7d17cb0b1f	Note the renderer's speed on real hardware ... Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-28 07:39:30 -07:00
dhkatzandClaude Opus 5.5	3cdda4c7ed	Map projections' depth like the client's renderer ... IMVU's projections give depth from -1 to 1; its Direct3D renderer maps it to 0 to 1, and now so does ours. Without that, the nearer half of the depth range was clipped, the whole 2D overlay (name tags, the frame rate, the room's title) with it. The adapter also draws drawTrianglesFromMemory without indices, and sums up what the client draws in its log. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-28 07:01:47 -07:00
dhkatzandClaude Opus 5.5	a04dba18c1	Draw particles, match the client's fog, and measure frame delay ... Particles (point sprites) are drawn as instanced camera-facing squares sized like Direct3D 9's. Fog is by depth buffer value, as Direct3D 9 does with IMVU's projections. At most one frame is queued for display, frames carry the adapter's timestamp so the renderer process logs the delay to presenting, and the log's lines from several processes no longer mix. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-28 06:11:51 -07:00
dhkatzandClaude Opus 5.5	5c35c8b63a	Note the renderer process spike's results ... Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-28 05:22:28 -07:00
dhkatzandClaude Opus 5.5	9a7d7d2908	Add the renderer process ... The renderer becomes two programs: the adapter (t5deRenderEngine.dll, 32-bit, in IMVU's process) and a 64-bit renderer process (t5de-renderer.exe) drawing with Diligent Engine, fetched with FetchContent and pinned. For now a spike: the adapter starts the renderer process for each engine and signals each frame through a shared memory channel, and the renderer process draws a box into a child window in the client's 3D view. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-28 05:17:03 -07:00