Portal Reaches a Command Stream, With the Frame Still Ahead

Portal continued to be a useful test of the 32-bit path because it combines a large application runtime with a substantial graphics workload. The September work added more of the Vulkan commands its path reached, including buffer updates, image copying, and vertex-buffer binding conversions.

Those conversions have to preserve more than a function name. A 32-bit array of pointers or offsets needs the correct shape on the native side, and the length we validate has to be the same length we later copy. One hardening change explicitly joined that length check and copy, rather than giving them separate opportunities to disagree.

Application imports also continued to surface. The recorded changes include handling a string-pointer query and binding the Steam installation-path query used by the title. These removed particular obstacles in the test path. They didn't turn a title-specific collection of imports into the finished generic Windows strategy.

The important result from the September 26 report is that Portal reached a Vulkan command stream. The equally important limit is that the report claimed no visible Portal frame, no intro, and no menu. I'm keeping that limit right next to the progress because it's the question someone interested in playing the game would actually ask.

Steam diagnostics were also exploring what a stalled worker was waiting for and which code created or signaled particular events. A trace can show that a client has advanced while still leaving the serving state needed by a game unresolved.

I want the eventual milestone to be easy to understand: a real frame, a menu, and an interactive session through the intended runtime. Until then, a command stream is a useful place to continue debugging. It isn't a substitute for the picture we still need to show.