Hello!

I have tried to phrase my question in multiple ways, mostly because I don't think I understand the complexity of this particular topic, so thanks for your patience!

Yet another rephrase:

1. Can I write Vertex Data to the VertexBuffer for two different objects, (square, triangle), with either the same or different input layout?
2. Can they both use different vertex shaders, pixel shaders, and textures?

3. Could I write a sort of Shader Selector in HLSL that reads a parameter from the input element and dynamically chooses a different pixel shader or texture?

Related C++ Code

When I create an input layout, can I do this without specifying an actual Vertex Shader, or somehow specify more than one?

NS::ThrowIfFailed(
result = NS::DeviceManager::Device->CreateInputLayout(
NS::ModelRenderer::InitialElementDescription,
2,
vertexShaderFile->Data,
vertexShaderFile->Length,
& NS::ModelRenderer::StaticInputLayout
)
);

When I set the VertexShader and PixelShader, how do I associate them with a particular model in my VertexBuffer? Is it possible to set more than one of each?

?

DeviceManager::DeviceContext->IASetInputLayout(ModelRenderer::StaticInputLayout.Get());

DeviceManager::DeviceContext->VSSetShader(ModelRenderer::StaticVertexShader.Get(), nullptr, 0);
DeviceManager::DeviceContext->PSSetShader(ModelRenderer::StaticPixelShader.Get(), nullptr, 0);

you need to pass a pointer to the compiled bytecode of a vertex shader in order to create an input layout.

Just a few* questions for clarification, if you don't mind: (I also cleaned up my initial question.)

Are there any issues with passing in a null pointer?

If I use multiple draw calls for models that require different shaders, do I just release the buffer, bind all the new vertex instance data, and draw? Or do I have to re-bind/re-set all of my shaders as well since the input layouts will be different?

DrawInstanced allows you to effectively point at a different model template in one buffer, and instance info for that model from another to render the model + instance data.

Is it possible to have the VertexShader define multiple output types so that a different pixel shader could be called?

Thanks for your help!

Thanks, I am just trying to find the most efficient way to have different pixel shaders used by the same type of mesh, but colored differently. For example, I would like square and triangle models in the vertex buffer, and for the pixel shaders to act differently based on instance data....

Is there a good way to accomplish this?

To answer all 3 of your questions, you can only ever have 1 shader bound for each stage. ..

What do you mean by stage? I was thinking that a Vertex Shader /was/ a stage. I am trying to bind 3 vertex shaders via the input layout, (which apparently won't work), or at least 3 shaders into the DeviceContext, using VSSetShader .... Can there only ever be 1 shader "pipeline" per DeviceContext?