billtheia

Thanks, Jim.

Thanks for the recommendations. In the end, I did as Pat suggested and rotated the sheet around the worksheet. Thankfully, you can rotate titleblocks. I added my +1 to the wish list request.

Yes, this would be useful. I have just run into a case where I needed a worksheet to be sideways on the page and it would have been nice to simply be able to rotate the worksheet. Instead, I had to rotate the entire page around the worksheet. Not very intuitive or user-centered.

I have a worksheet that I'd like to rotate 90 degrees on my sheet layer but it seems that neither command L or use of the rotate tool works. Is there another way to rotate worksheets?

I use RW for interior renderings quite often. I don't typically try to get completely photorealistic output, though because I usually want clients to focus on design decisions rather specific materials & colors. With the implementation of the C4D rendering engine in RW, I have found it quite easy to get good interior renders with an HDRI background and a single directional light (heliodon.) The key for me was using Custom Renderworks, setting the Indirect Lighting to 4 Bounces, and turning off ambient lighting. Then I play with the intensity of the HDRI background (often greater than 100%) and the directional light to get the lighting to look the way I want. I will generally work without material textures (other than clear glass to let light in) to set lighting levels and then apply textures. I generally create a RW Style and then tweak it as I go. Then I can apply it to other scenes to get consistent output. Ben, can you post examples of renderings that you have created and tell us what you'd like to improve?

Didn't realize that the image was a bitmap. Bummer.

Can't you do something like this now, in VW2013 & 14? I thought that you could now put an elevation of windows & doors in the schedule worksheet.

Thanks, John. I figured out my problem. I had the class on in the VP but off in the drawing itself. As soon as I turned the class back on, all worked as expected.

I understand that, John. I can't get it to work with objects drawn in the annotation space. It used to work but, recently, it stopped. I don't know if it's something that changed with the last service pack for VW2013 or if something else has gone wrong with my installation. Have you verified that it works properly in VW2013-SP5? Your signature shows that you are working with SP4. Is that correct or have you just not updated your signature yet?

I recently noticed that the "Activate Class" right-click option isn't working in VP annotation space, when using VW2013. It works just fine when working on a design layer but does nothing when working in the annotation space of a VP. Is anyone else out there having this problem? Can anyone recommend a fix? Thanks.

I would love for the eye dropper tol to be able to grab just the render settings. In the mean time, use of render styles will get you very close to the same result.

Really? In something as basic as a door?

Thanks. Any idea why doesn't it work with doors NOT inserted as symbols?

What is the expected outcome?

Hi all. I've been using VW for quite some time now and I've never been quite clear on what the "door break with caps" and "?without caps" settings are for. They don't seem to make any difference. Can someone out there enlighten me? Thanks.

Would you be willing to share that worksheet? Sounds like it would be very useful.

Robert, I'm not working with a roof object. I'm already working with roof faces.

I just discovered this "feature." I am working on a roof that I would like to have vertical cut eaves (so that I can hang gutters on them) and square cut holes (so that I can put skylights in. Unfortunately, the "logic" used by VW seems to make that not really possible. I really don't understand why the 2d hole representation on a roof would be based on the bottom face. The roof is never viewed (in 2d) from the bottom. I'm also a little surprised that this behavior has existed since 2004 and NVW hasn't fixed it. Is there a work-around that would allow me to do what I need to do here?

Thanks, Majic. I hadn't thought of using a single, EXISTING, layer type. I think that could work for me too. I might also add an ORIGINAL layer - I generally keep an unmolested copy of the building's original state for existing elevations and for reference. I also like the class prefixes. I think I'll look at incorporating something like that into my standard class list. I'm still going to avoid, though, creating separate classes for existing vs new. That results in really long class list and I don't think that I need it if I'm separating things by layer.

Thanks for the responses. Majic, do you use custom layer types (E-Floor, N-Floor, etc.) or just set existing layer types to "none?" Vincent, I have considered using classes instead of layers before. Using layers just seemed simpler because I didn't need to have new- and existing- classes for everything (walls, windows, doors, floors, ceilings, casework, lighting, etc.) Using layers allows everything to work with the same (smaller) set of classes. Jeffrey, thanks for sharing your examples. It would be really useful, I think, if VW had example files for renovation projects too. When I first started using VW, in 2007, I found the Alexandria Lofts example file to be invaluable. Anybody else out there willing to share an example file for their renovation project?

Hi. I've been using VW since v12.5 and am currently using V2013 (waiting for v2014 to become more stable.) Most of my projects are renovations so I have a need to be able to distinguish between new, existing, and demolition. Currently, I use separate design layers for new and existing (one per floor) and show new walls with a gray fill, existing walls with a white fill, and demolished walls with a dashed line (typical US convention.) I put new and existing walls in the same class and use wall types to show the desired fill. I put demolished walls in a separate class with it's line type set to dashed. My current setup is based on the Alexandria Lofts project that VW shows as a "BIM" example. I have started looking at using stories (haven't used them yet) because VW says that they will make my workflow easier. Unfortunately, it doesn't look like stories were designed with renovation projects in mind and none of the example files that VW shows on their web site seem to use stories (at least none that I looked at.) It looks like you can only have one of each layer type (floor, ceiling, etc.) in each story so I can't figure out how I would set up a renovation project using stories. Can anyone out there show me a best practice for using stories on a project that has new AND existing work? I'd love to see how some of you handle layer,class, and story definitions. Thanks in advance for the help.

You can get the same basic look by using a sheet layer viewport set with background rendering to render works (fast, custom, final) and foreground rendering set to hidden line. This method doesn't create the lines between floors.

Got it! Thanks!

In VW2012, you could hit the escape button to cancel a rendering. With background rendering implemented in VW2013, this doesn't seem to work now. Is there another way to stop a viewport render mid-stream?

In theatre, where I work much of the time, $1,000 +/- per week of billable time can often be the norm. From my perspective you seem as profit oriented as NV. Is that ok, of course. So why is it so wrong for NV? The reality is that VW exists because NV are able to generate revenue to support development and keep the shareholders happy. KM Yes, I am interested in making profit. I live in a capitalistic society that relies on $. WIthout profit, I would have no roof over my head or food on my table. I do not begrudge NVW making a profit. I begrudge them increasing profit while simultaneously decreasing quality and dedication to user satisfaction.