2 replies to this topic

[Migi0027]

Hi guys,

 

I'm working with Directx 11 shaders.

Is it more efficient to create a single class that handles the responsibilities of all shaders, or use individual classes for each independent shader?

In my own experience, I've used a single class, which works reasonably well, but makes it much harder to send different information to each shader.

Which approach is more efficient for typical DirectX 11 applications?

 

Thank You

[NiteLordz]

I have one class "shaders" and separate struts for parameters and samplers. I then have a list of both in the shaders. Upon binding, I apply each list. I found this works nicely, and it doesn't matter what kind of shader it is, vs, PS, gs, cs, etc... they all work and is east to maintain

[Hodgman]

I've used a single class, which works reasonably well, but makes it much harder to send different information to each shader.

As mentioned above, every shader receives the same type of information -- buffers and textures and samplers. So you can easily have 1 shader class, but then different types to help put data into different buffers.