第 8 章 命令与状态管理本章定位Vulkan 是「命令驱动」的 API。本章讲清 VSG 如何用Command/StateCommand/StateGroup把 Vulkan 的状态绑定管线、描述符、顶点缓冲优雅地挂到场景图上。8.1 本章目标理解vsg::Command与vsg::StateCommand的角色掌握vsg::StateGroup的「压栈/弹栈」语义认识常用的状态命令BindGraphicsPipeline/BindDescriptorSet(s)/BindVertexBuffers等会用「底层路径」手动拼一个带状态的StateGroup不依赖GraphicsPipelineConfigurator。8.2 前置准备第 6 章场景图节点与第 7 章几何体已读了解 Vulkan 的vkCmdBindPipeline/vkCmdBindDescriptorSets基本概念。8.3Command可录制的原子操作vsg::CommandInheritObject, Command是能被录进CommandBuffer的原子操作关键两个方法compile(Context)编译期准备 Vulkan 对象record(CommandBuffer)录制期写出vkCmdXxx调用。vsg::Commands是Command的容器类似Group但专装命令CPU 开销更低用addChild(ref_ptrCommand)添加子命令。常见命令Draw/DrawIndexed/BindGraphicsPipeline/BindDescriptorSet(s)/BindVertexBuffers/BindIndexBuffer。8.4StateCommand与状态栈vsg::StateCommandInheritCommand, StateCommand是「带状态语义」的命令多一个slot字段用于在录制时按槽位slot组织状态栈slot0通常是BindGraphicsPipelineslot1通常是BindDescriptorSet(s)顶点/索引绑定命令也占用各自 slot。状态栈的意义进入StateGroup时把它的stateCommands压栈遇到Command如Draw时应用栈顶状态离开StateGroup时弹出。于是同一个管线/描述符只需声明一次就能作用于整棵子树。8.5StateGroup状态与子图的结合点StateGroup继承自Group额外有StateCommands stateCommands本组要施加的状态命令列表add(ref_ptrStateCommand)追加一条状态命令children子图继承自Group。auto stateGroup vsg::StateGroup::create(); stateGroup-add(vsg::BindGraphicsPipeline::create(pipeline)); // slot 0 stateGroup-add(vsg::BindDescriptorSet::create( // slot 1 VK_PIPELINE_BIND_POINT_GRAPHICS, pipelineLayout, 0, descriptorSet)); stateGroup-addChild(geometry);RecordTraversal碰到StateGroup时先 push 所有stateCommands→ 遍历children录制 Draw 时自动应用这些状态→ 离开时 pop。第 5 章里GraphicsPipelineConfigurator::copyTo(stateGroup)干的正是上面的add(BindGraphicsPipeline)——只是它连PipelineLayout、顶点输入等一起塞好了。8.6 常用状态命令一览状态命令对应 Vulkan说明BindGraphicsPipelinevkCmdBindPipeline绑定图形管线slot 0BindDescriptorSet(s)vkCmdBindDescriptorSets绑定描述符集slot 1BindVertexBuffersvkCmdBindVertexBuffers绑定顶点缓冲通常由Geometry自动生成BindIndexBuffervkCmdBindIndexBuffer绑定索引缓冲由Geometry自动生成ViewportState视口/裁剪视口与裁剪矩形也是GraphicsPipelineState此外所有GraphicsPipelineState子类顶点输入、光栅化、混合、深度模板、多重采样等也都是状态会在管线创建时合并进GraphicsPipeline而非运行时逐条vkCmd*。8.7 底层路径示例手动拼装带状态的 StateGroup下面不使用GraphicsPipelineConfigurator直接展示状态如何落地管线pipeline与pipelineLayout的创建见第 9 章// 假设已建好 pipeline / pipelineLayout / descriptorSet / geometry auto stateGroup vsg::StateGroup::create(); // 状态 1绑定图形管线 stateGroup-add(vsg::BindGraphicsPipeline::create(pipeline)); // 状态 2绑定描述符集uniform / 纹理 stateGroup-add(vsg::BindDescriptorSet::create( VK_PIPELINE_BIND_POINT_GRAPHICS, pipelineLayout, 0, // firstSet descriptorSet)); // 子树几何体内部自动 BindVertexBuffers / BindIndexBuffer stateGroup-addChild(geometry);下面给出一个完整可运行的 C 示例把「创建pipeline/pipelineLayout/descriptorSet」到「组装StateGroup与Geometry」串成一条完整流程着色器编译与交换链等细节见第 9、10 章#include vsg/all.h // 1. 创建 DescriptorSetLayout 与 PipelineLayout auto descriptorSetLayout vsg::DescriptorSetLayout::create( vsg::DescriptorSetLayoutBindings{ {0, VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER, 1, VK_SHADER_STAGE_VERTEX_BIT, nullptr} // binding 0uniform 缓冲 }); auto pipelineLayout vsg::PipelineLayout::create( vsg::DescriptorSetLayouts{descriptorSetLayout}); // set 0 使用上面的布局 // 2. 创建 DescriptorSet 并绑定 uniform 缓冲 auto descriptorSet vsg::DescriptorSet::create( descriptorSetLayout, vsg::Descriptors{vsg::DescriptorBuffer::create( uniformBuffer, 0, VK_WHOLE_SIZE)}); // 绑定到 binding 0 // 3. 创建 GraphicsPipeline着色器见第 9 章 auto shaderSet vsg::ShaderSet::create(vsg::paths::shaders()); shaderSet-add(vsg::ShaderStage::create(VK_SHADER_STAGE_VERTEX_BIT, main, shaders/vert.vert)); shaderSet-add(vsg::ShaderStage::create(VK_SHADER_STAGE_FRAGMENT_BIT, main, shaders/frag.frag)); auto pipeline vsg::GraphicsPipeline::create( vsg::GraphicsPipelineStates{ vsg::VertexInputState::create(), vsg::InputAssemblyState::create(), vsg::RasterizationState::create(), vsg::ColorBlendState::create(), vsg::DepthStencilState::create()}, shaderSet, pipelineLayout); // 4. 创建 Geometry内部自动生成 BindVertexBuffers / BindIndexBuffer auto geometry vsg::Geometry::create(); geometry-arrays.push_back(vsg::vec3Array::create(vertices)); // 顶点坐标 geometry-arrays.push_back(vsg::vec3Array::create(normals)); // 法线 geometry-indices vsg::uintArray::create(indices); // 索引 // 5. 组装 StateGroup把状态命令挂到场景图上 auto stateGroup vsg::StateGroup::create(); stateGroup-add(vsg::BindGraphicsPipeline::create(pipeline)); // slot 0绑定管线 stateGroup-add(vsg::BindDescriptorSet::create( // slot 1绑定描述符集 VK_PIPELINE_BIND_POINT_GRAPHICS, pipelineLayout, 0, descriptorSet)); stateGroup-addChild(geometry); // 子树几何体 // 6. 挂到场景根节点交给 RecordTraversal 录制 auto scene vsg::Group::create(); scene-addChild(stateGroup);对比「便捷路径」第 5 章auto pipelineConfig vsg::GraphicsPipelineConfigurator::create(shaderSet); pipelineConfig-enableArray(inPosition, VK_VERTEX_INPUT_RATE_VERTEX, sizeof(vsg::vec3), VK_FORMAT_R32G32B32_SFLOAT); pipelineConfig-init(); pipelineConfig-copyTo(stateGroup); // 等价于上面的 add(BindGraphicsPipeline) 设置 pipelineStates stateGroup-addChild(geometry);两条路径最终效果一致便捷路径适合常规网格底层路径适合需要精细控制管线状态的场景。8.8 常见问题现象可能原因排查步骤与解决方案状态没生效如没绑管线StateCommand没add进StateGroup或slot冲突1. 检查stateGroup-add(...)是否真的执行确认StateCommand已挂到目标StateGroup2. 打印各StateCommand的slot值确认slot 0只被BindGraphicsPipeline占用未被其他命令覆盖。描述符绑定后着色器读不到firstSet/dstBinding与PipelineLayout不匹配1. 核对BindDescriptorSet的firstSet是否等于pipelineLayout-setLayouts中对应DescriptorSetLayout的下标2. 用 Vulkan 校验层Validation Layers或vkCmdBindDescriptorSets的返回状态确认绑定是否成功并检查着色器里layout(set..., binding...)与dstBinding是否一致。多个 StateGroup 状态串味误以为状态是全局的1. 检查嵌套StateGroup的层级确认内层StateGroup是否在离开时正确 pop 掉自身状态2. 在RecordTraversal回调或调试器中观察进出StateGroup时状态栈的 push/pop 顺序确认没有遗漏 pop。顶点缓冲未绑定没用Geometry也没手动BindVertexBuffers1. 确认Geometry已作为StateGroup的children加入且其内部BindVertexBuffers已生成2. 若手动绑定检查BindVertexBuffers的vertexBuffers数组与offsets是否与顶点数据布局一致必要时用 RenderDoc 抓帧确认顶点缓冲是否被正确提交。8.9 小结Command是可录制的原子操作StateCommand带slot组织成状态栈StateGroup的stateCommands对子树「压栈—录制—弹栈」是场景图与 Vulkan 状态的桥梁常用状态命令BindGraphicsPipeline(slot0)、BindDescriptorSet(s)(slot1)、BindVertexBuffers/IndexBuffer多由Geometry自动生成便捷路径GraphicsPipelineConfigurator::copyTo与底层路径最终等价。8.10 延伸阅读与下一章预告第 9 章《着色器与管线》如何真正创建pipeline/pipelineLayout/ShaderModule第 10 章《描述符与资源绑定》descriptorSet从哪来、BindDescriptorSet怎么填第 12 章《RenderGraph 与 CommandGraph》这些Command最终如何被录进CommandBuffer。
