Uploaded August 2026 | Updated September 2026, 2 weeks ago
What if Microsoft PowerPoint isn't just a tool for bullet points and quarterly slide decks, but secretly a high-performance procedural animation and physics engine?
In this technical deep dive, we break down Project CLASH—a cinematic combat encounter between the heavy digitigrade Goliath Mech and an autonomous Viper-Drone running at a locked 60 FPS using 46 native PowerPoint shapes with zero third-party runtime plugins.
We explore the engineering marvel behind bypassing PowerPoint’s legacy performance ceilings, deconstructing how the yoAnime TypeScript SDK decouples heavy mathematical evaluation from slide rendering to unlock fluid, procedural physics.
⏱️ Timestamps & Chapters
00:00 — Live Demo: Project CLASH (Goliath Mech vs. Viper-Drone)
00:20 — The Core Question: Can PowerPoint Run a Game Engine?
01:26 — Section 1: Deconstructing Math — Autonomous Agents
01:42 — 2-Bone Analytical Inverse Kinematics (IK) & Digitigrade Walking
02:40 — Drone Behavior: Finite State Machine (FSM) Modes (Stalk ➔ Strafe ➔ Evade)
03:09 — Reciprocal Combat: Dynamic LookAt Auto-Cannon Tracking & Energy Shield Deflection
04:01 — Section 2: The Antagonist — The COM Bottleneck
04:39 — Why Office Apps Lag: Single-Threaded Apartment (STA) Marshaling (1.17ms Delay)
05:12 — The "Drive-Through Window" Analogy
05:40 — Benchmark Telemetry: Framerate Drop from 31.5 FPS down to 6.1 FPS
06:20 — Section 3: The Architecture — Unlocking 60 FPS
06:34 — Two-Layer Architecture: C# VSTO Host + WebView2 TypeScript Sandbox
07:04 — Core Philosophy: "The author declares, the runtime evaluates, the renderer rasterizes"
07:34 — The Two-Rail System: Live Rail (Snail) vs. Baked Rail (Rocket)
08:06 — 4-Step Execution Pipeline (Evaluate ➔ Compile ➔ Inject CustomXML ➔ Playback)
09:03 — Conclusion: Unlocking Hidden Potential in Everyday Software
🧠 Key Engineering Takeaways
The COM Bottleneck Explained: Why direct shape manipulation via the Component Object Model caps performance and causes severe framerate degradation when animating multiple objects.
Decoupled Sandbox Evaluation: How running math (IK, trigonometry, state machines) inside an isolated WebView2 JavaScript runtime eliminates interface freezing.
CustomXML GPU Injection: How compiling procedural trajectories into compressed payloads and injecting them directly into PowerPoint's native GPU timeline delivers locked 60 FPS playback across standard corporate machines.
🔗 Resources & Links
SDK Documentation & Repository: github.com/theteacherpoint1977/yoanime-sdk
YoAnime Studio Download: apps.microsoft.com/detail/9pp5t5lhg1jl?hl=en-US&gl=IN
Try the Code Snippet: github.com/theteacherpoint1977/yoanime-sdk/tree/main/samples/console-scripts
#powerpoint #gamedev #softwareengineering #typescript #coding #programming #physicsengine #softwarearchitecture #inversekinematics #yoanime #computerscience #webdevelopment #animation #tech #gamedevelopment
What if Microsoft PowerPoint isn't just a tool for bullet points and quarterly slide decks, but secretly a high-performance procedural animation and physics engine?
In this technical deep dive, we break down Project CLASH—a cinematic combat encounter between the heavy digitigrade Goliath Mech and an autonomous Viper-Drone running at a locked 60 FPS using 46 native PowerPoint shapes with zero third-party runtime plugins.
We explore the engineering marvel behind bypassing PowerPoint’s legacy performance ceilings, deconstructing how the yoAnime TypeScript SDK decouples heavy mathematical evaluation from slide rendering to unlock fluid, procedural physics.
⏱️ Timestamps & Chapters
00:00 — Live Demo: Project CLASH (Goliath Mech vs. Viper-Drone)
00:20 — The Core Question: Can PowerPoint Run a Game Engine?
01:26 — Section 1: Deconstructing Math — Autonomous Agents
01:42 — 2-Bone Analytical Inverse Kinematics (IK) & Digitigrade Walking
02:40 — Drone Behavior: Finite State Machine (FSM) Modes (Stalk ➔ Strafe ➔ Evade)
03:09 — Reciprocal Combat: Dynamic LookAt Auto-Cannon Tracking & Energy Shield Deflection
04:01 — Section 2: The Antagonist — The COM Bottleneck
04:39 — Why Office Apps Lag: Single-Threaded Apartment (STA) Marshaling (1.17ms Delay)
05:12 — The "Drive-Through Window" Analogy
05:40 — Benchmark Telemetry: Framerate Drop from 31.5 FPS down to 6.1 FPS
06:20 — Section 3: The Architecture — Unlocking 60 FPS
06:34 — Two-Layer Architecture: C# VSTO Host + WebView2 TypeScript Sandbox
07:04 — Core Philosophy: "The author declares, the runtime evaluates, the renderer rasterizes"
07:34 — The Two-Rail System: Live Rail (Snail) vs. Baked Rail (Rocket)
08:06 — 4-Step Execution Pipeline (Evaluate ➔ Compile ➔ Inject CustomXML ➔ Playback)
09:03 — Conclusion: Unlocking Hidden Potential in Everyday Software
🧠 Key Engineering Takeaways
The COM Bottleneck Explained: Why direct shape manipulation via the Component Object Model caps performance and causes severe framerate degradation when animating multiple objects.
Decoupled Sandbox Evaluation: How running math (IK, trigonometry, state machines) inside an isolated WebView2 JavaScript runtime eliminates interface freezing.
CustomXML GPU Injection: How compiling procedural trajectories into compressed payloads and injecting them directly into PowerPoint's native GPU timeline delivers locked 60 FPS playback across standard corporate machines.
🔗 Resources & Links
SDK Documentation & Repository: github.com/theteacherpoint1977/yoanime-sdk
YoAnime Studio Download: apps.microsoft.com/detail/9pp5t5lhg1jl?hl=en-US&gl=IN
Try the Code Snippet: github.com/theteacherpoint1977/yoanime-sdk/tree/main/samples/console-scripts
#powerpoint #gamedev #softwareengineering #typescript #coding #programming #physicsengine #softwarearchitecture #inversekinematics #yoanime #computerscience #webdevelopment #animation #tech #gamedevelopment
