Jump to content

  • Log In with Google      Sign In   
  • Create Account

#ActualTom KQT

Posted 08 January 2013 - 04:29 PM

You mean the effect framework, right? It simply sets the render or sampler state the same way you would (device->SetRenderState etc.), there's no magic behind it. It definitely doesn't set it per vertex/pixel ;)
You can do some optimizations if you do it manually (for example don't set a state to the same value it already has), but that's not directly related to your question, and the performance gain may be very small (if any).

#3Tom KQT

Posted 08 January 2013 - 04:28 PM

You mean the effect framework, right? It simply sets the render or sampler state the same way you would (device->SetRenderState etc.), there's no magic behind it. It definitely doesn't set it per vertex/pixel ;)
You can do some optimizations if you do it manually (for example don't set a state to the same value it already has), but that's not directly related to your question, and the performance gain may be very small.

#2Tom KQT

Posted 08 January 2013 - 04:27 PM

You mean the effect framework, right? It simply sets the render or sampler state the same way you would (device->SetRenderState etc.), there's no magic behind it. It definitely doesn't set it per vertex/pixel ;)
You can do some optimizations if you do it manually (for example don't set a state to the same value it already has), but that's not directly related to your question.

#1Tom KQT

Posted 08 January 2013 - 04:27 PM

You mean the effect framework, right? It simply sets the render or sampler state the same way you would (SetRenderState etc.), there's no magic behind it. It definitely doesn't set it per vertex/pixel ;)

You can do some optimizations if you do it manually (for example don't set a state to the same value it already has), but that's not directly related to your question.


PARTNERS