Archived

This topic is now archived and is closed to further replies.

d3dxeffect issue

This topic is 5590 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi, I was going to write code for a shader implementation when I saw d3dxeffect. it looks very nice and robust, but it has one drawback: one cannot determine which states get changed by its techniques. since I use state-caching to avoid redudant states, this becomes a problem. either I update the state cache with GetRenderState() calls after using the technique, or I flush it, making some redundant state calls possible. I don''t want to scrap the state cache since redundant state calls may harm the performance. Any suggestions?

Share this post


Link to post
Share on other sites