DDDesign Posted October 4, 2005 Share Posted October 4, 2005 I have some textures in a file created as filtered images. After a while, when I use FQ or custom RW some of the faces turn grey. Strangely, some faces on solids on different planes are OK. I've found I can get the rendering back to normal if I go through and slightly change the mapping scale in the OIP. However the problem recurs after a while, and I have to do it all over again. Quote Link to comment
Vectorworks, Inc Employee Dave Donley Posted October 5, 2005 Vectorworks, Inc Employee Share Posted October 5, 2005 Hello DDDesign: Do the faces overlap? The raytracing recursion level may need to be increased to account for the overlapping surfaces. The default for FQRW mode is 5. In general you will need to set this to twice the number of overlapping surfaces. So if you have 4 overlapping 3D polygons use Custom RW mode with the raytracing recursion set to 8. This is required for overlapping image props too. Quote Link to comment
DDDesign Posted October 5, 2005 Author Share Posted October 5, 2005 The objects are single extruded rectangles-one in front of the other. If I'm understanding correctly what you mean by overlap, then this explains why the top faces render ok, but the the front visible face is grey. However, I'm not sure how this theory explains the change in render when the mapping scale is changed. Or why everything works OK, and all of a sudden the problem occurs. If I set Custom RW to shadow mapped shadows, instead of ray-trace, would it also solve the problem? Quote Link to comment
APE Design Ctr Posted October 5, 2005 Share Posted October 5, 2005 I have this issue frequently (if it is the same issue). I believe it has to do with how the symbol is grouped... I honestly think this is a bug, but if you change your fill style to Solid/Pattern fill it renders correctly. Try it and let me know. Quote Link to comment
DDDesign Posted October 5, 2005 Author Share Posted October 5, 2005 I got the problem occuring in groups as well as symbols. At the moment I can't get the problem to reproduce itself, even if I change the mapping scales back to the original, so it probably IS a bug. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.