ErichR Posted April 25, 2006 Share Posted April 25, 2006 (edited) In v12.0.1, VW crashes when doing a final quality Renderworks rendering. Settings are for moderate levels of detail, at 72 DPI. I thought the problem might be mitigated with a reduction of the rendering window, or lowering of the DPI setting, but this does not help; VW still crashes. Also, when restricting the perspective window (this is a model layer with layer links), the image, or parts of it disappear. Seems like these are serious bugs, but if I'm overlooking something, I would appreciate being set on the right course. Edited April 25, 2006 by ErichR Quote Link to comment
Guest Posted April 25, 2006 Share Posted April 25, 2006 Erich, What happens if you use Fast RW or Fast RW with Shadows? Quote Link to comment
ErichR Posted April 25, 2006 Author Share Posted April 25, 2006 Both Fast and w/ Shadows work as expected. Quote Link to comment
Vectorworks, Inc Employee Dave Donley Posted April 25, 2006 Vectorworks, Inc Employee Share Posted April 25, 2006 Hello ErichR; What happens when you use Custom RW with NURBS turned off? Also, if you select all then click the Fit To Objects button in the view bar, does the document zoom out to a ridiculous size (millions of feet)? Quote Link to comment
ErichR Posted April 26, 2006 Author Share Posted April 26, 2006 (edited) Dave, 1. Custom Renderworks works, so this is a welcome workaround. 2. There doesn't appear to be a NURBS option. 3. Fit to Objects does not zoom out, with all selected. 4. Then this is a bug with Renderworks? 5. Are there fewer capabilities (NURBS, for instance) with Custom Renderworks than with Renderworks? Edited April 26, 2006 by ErichR Quote Link to comment
ErichR Posted April 27, 2006 Author Share Posted April 27, 2006 Sorry, there IS a NURBS option. In addition, I got an out of memory message (4GB available) when invoking the Convert Copy to Lines command. This isn't Renderworks, but it is part of the rendering function. Again, this crashing with Renderworks does appear to be a bug. Is the Convert Copy to Lines problem also a bug? Quote Link to comment
grant_PD Posted April 28, 2006 Share Posted April 28, 2006 what platform are you using? Quote Link to comment
ErichR Posted April 28, 2006 Author Share Posted April 28, 2006 Grant, WXP OS Turns out that one of the limitations of Custom Renderworks is that it puts an ugly opaque color rectangle into all of the image props. I had replaced all of the trees with image props,in order to reduce file size and, maybe, ease processing issues, and now not only will it not render with standard Renderworks, the image props are all unacceptable. Fooled with all of the image prop variables, and their class color assignments to no avail. So, the bottom line is that RW doesn't appear to work, but it's curious that we don't see a lot of similar posts. Quote Link to comment
G_Hannigan Posted April 28, 2006 Share Posted April 28, 2006 Erich, When you created the image prop, did you select Use Mask under Mask Options? In Choose Prop Mask Image, Reuse an Image From a Texture Resource - This Prop's Color. Then in Create Mask, Source for Mask, Transparent Color - use the eyedropper on the background. The preview will show the outline of the object. You can fine tune if necessary. It will not have the opaque frame in your rendering. George Quote Link to comment
Vectorworks, Inc Employee Dave Donley Posted April 28, 2006 Vectorworks, Inc Employee Share Posted April 28, 2006 Hello again ErichR: Also you have to render with a render mode that uses transparency. Final Quality does this. If you see opaque rectangles as multiple image props overlap, you need to use Custom RW with the raytracing recursion level set to twice the number of overlapping surfaces, i.e. set it to 12 if you have 6 overlapping props. Quote Link to comment
G_Hannigan Posted April 28, 2006 Share Posted April 28, 2006 Dave, It seems to work OK for me with Open GL, Fast & Final RW, Final & Custom Rad. Only Fast Rad showed shadows of transparent sections. George Quote Link to comment
ErichR Posted April 28, 2006 Author Share Posted April 28, 2006 (edited) George, I didn't create the image props. They came from the VW library. The Model>Create Image Prop dialog box, for editing an image prop, does not appear to be intended to be used for editing and is confusing and was sort of dead-ended when attempted. Dave, Why is recursion levels an issue with Custom Renderworks, and not with standard Renderworks? I set it to 20 recursions and still the image prop rectangles are opaque. This is beginning to be a really, really clutsy workaround for something that shouldn't be an issue. Again, is it a Renderworks bug that causes VW to crash? If so, will it be fixed? So far, I can render (only with Custom Renderworks), but not using the image props the way they came with VW. Edited April 28, 2006 by ErichR Quote Link to comment
ErichR Posted May 2, 2006 Author Share Posted May 2, 2006 The silence is deafening. Renderworks (Final Quality)doesn't work for me. Is it broken? Is there a bug? Quote Link to comment
Guest Posted May 2, 2006 Share Posted May 2, 2006 How many instances of the image prop do you have in the drawing? Can you send a file demonstrating the problem along w/ a description to tech@nemetschek.net? Quote Link to comment
ErichR Posted May 3, 2006 Author Share Posted May 3, 2006 I turned off the image prop class, since I am not able to get them to render properly with Custom Renderworks, so zero instances. FTP would be better, since it's 100MB. Thanks. Quote Link to comment
Christiaan Posted May 3, 2006 Share Posted May 3, 2006 FTP would be better, since it's 100MB. Friend of mine just recommend YouSENDit to me. Quote Link to comment
Guest Posted May 3, 2006 Share Posted May 3, 2006 FTP.NEMETSCHEK.NET Username: upload Password: file-put Please send me an email once the file has been uploaded letting me know it's there. Thanks! Quote Link to comment
ErichR Posted May 3, 2006 Author Share Posted May 3, 2006 I apologize. Renderworks works fine on an earlier iteration of the same file (with v12.0.1). So, there is something wrong with the newer file. I aborted the FTP to Katie, because it was taking over an hour, and it seems I should probably try to find the problem myself. Thanks anyway. Quote Link to comment
ErichR Posted May 5, 2006 Author Share Posted May 5, 2006 (edited) By using a process of elimination, the errant object, which caused Renderworks crashing, turned out to be an extrusion. Upon this discovery, I remembered having a similar problem before. Double-clicking on an extrusion revealed the 2D object that was used to make the extrusion. It was a polyline. There is some incompatibility between polylines and extrusions, at least as far as Renderworks is concerened. Simply converting it to a polygon didn't work: the resulting shape was divided into many polygons. However, using the polyline as a template and cliping a new one from a rectangular surface, a two-step positive to negative to positive process, I was abale to produce an acceptable polygon and then to extrude it. So, it appears that renderworks can't handle an extrusion made from a polyline, but it can process one made from a polygon. Wonder why this is, and why there doesn't seem to be any documentation covering this. I've wasted untold hours without knowing what the problem was or what I was looking for. Edited May 5, 2006 by ErichR Quote Link to comment
islandmon Posted May 5, 2006 Share Posted May 5, 2006 To easily convert Polyline >Polygon: 1) Convert Polyline to Line 2) Compose Polylines should be converted to NURBS then Taper Extrude > 3D. Quote Link to comment
Vectorworks, Inc Employee Dave Donley Posted May 5, 2006 Vectorworks, Inc Employee Share Posted May 5, 2006 Hello ErichR: I would love to see this file. RenderWorks works best with polylines versus polygons; this is likely a very specific bug. Quote Link to comment
ErichR Posted May 9, 2006 Author Share Posted May 9, 2006 I would love to get rid of it. I'll email it to you. Quote Link to comment
Vectorworks, Inc Employee Dave Donley Posted May 9, 2006 Vectorworks, Inc Employee Share Posted May 9, 2006 Hello again Erich: It looks like it is crashing when it is trying to extrude the polyline for rendering. There are ultimately going to be a lot of vertices generated for this polyline and its holes when it being rendered. This is a bug that is already fixed for the next major release. To workaround it in this file I would split the polyline into multiple objects. I will try this myself (by splitting it with several vertical lines probably), and let you know if it fixes the crash. HTH, Quote Link to comment
Vectorworks, Inc Employee Dave Donley Posted May 9, 2006 Vectorworks, Inc Employee Share Posted May 9, 2006 Hello again Erich: I split it about five times with vertical lines using the Split tool and it is rendering without crashing, so this may be a workaround for you. Quote Link to comment
Jim_Allen Posted May 10, 2006 Share Posted May 10, 2006 Dave, Do you mean update not release?? I am assuming it will not cost additional to get bug fixes? 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.