Can`t use another push constants block alongside with vsg's view-projection PC block.

[paveltrpn]

I define push constant block in fragment shader:

layout(push_constant) uniform PushConstants {
    vec3 colorMajor; 
    vec3 colorMinor; 
    float majorDivisor; 
} pushConst;

and try to pass some data to it:

const auto commands = vsg::Commands::create();

    const auto colorMajor = vsg::vec3{ 0.1f, 0.2f, 0.9f };
    const auto colorMinor = vsg::vec3{ 0.2f, 0.2f, 0.5f };
    const auto majorDivisor = 5.0f;

    auto conf = vsg::floatArray::create(
        { colorMajor.r, colorMajor.g, colorMajor.b, 1.0, colorMinor.r, colorMinor.g, colorMinor.b, majorDivisor } );
    _confPushConst = vsg::PushConstants::create( VK_SHADER_STAGE_FRAGMENT_BIT, 128, conf );

    commands->addChild( _confPushConst );

    const auto drawCmd = vsg::Draw::create( 6, 1, 0, 0 );
    commands->addChild( drawCmd );

    const auto tr = vsg::MatrixTransform::create();
    tr->addChild( commands );

    _stateGroup->addChild( tr );

RenderDoc showing that vkCmdPushConstants() command properly called, i check layout of
data and other things in pipeline layout creation but i have nothing data passed to FS.
Can you point me to some example of using push constants in VSG?

i run on rtx 5070.

[AnyOldName3]

I don't think there's enough context to tell what's going wrong here. We might be able to tell if we're given the RenderDoc capture, and the Vulkan validation layers might be able to tell you what's wrong if you enable them, but if those aren't viable, then you'll want to reproduce the issue in a test app that you can send us the full source code of.