Ok, I looked up the material struct in A7 and the d3deffect was indeed at a different position there. Only in A8 it got a fixed position and was documented. In the last A7 version, d3deffect was 8 bytes after its current position in A8. It could have been at other positions in different A7 versions.
I'm using the final A7 version, could you post an example on how to access d3deffect? I guess i just have to change the MATERIAL struct the right way and that should be it (moving the d3deffect pointer one or two positions further to the end in the struct...?)
As to the ENABLE_VIEW issue, I tested your sample, but the problem does not happen in A8. So it was indeed something A7 specific.
Thanks for the info. I created a workaround and now don't have any problems with ENABLE_VIEW anymore. It's a little more user-unfriendly now, but should still be ok to work with for the end user of Shade-C.
[edit] Also wanted to mention that the rendertarget sharing works like a charm
