billtheia

OK. Thanks. Will do.

I am unable to get class overrides to work in viewports with roof faces in VW2016. I want to have some views use a texture with 3d hatch and some views use a texture with NO hatch but I can't get it to work. Can someone out there help me? Thanks. File attached.

Thanks, Jim. That is what I'm looking for.

Can anyone out there help me figure out how to model a square, domed skylight? I've tried using extrude along path but the result looks more like the dome was mitered together than blow-moulded. I assume that there is some other 3-d tool that will provide the result that I'm after but I can't figure out which tool that is. Thanks.

I've just upgraded to VW2016 and am having trouble with renderworks quitting mid-render for no apparent reason. Is anyone else having this problem? Any ideas what I can do to fix it? Thanks.

Thanks, Zoomer. I'm already familiar with ISO, aperture, and shutter speed. I just need to spend some time fiddling with it to see what works best.

Thanks, Tim. Interesting post. I see now that the "physical camera" allows me to set ISO, shutter speed, & aperture. I'll have to mess around with those & see what happens.

In the process of making the jump from VW2015 to VW2016. The Render Style dialog box has changed. There is no longer an Exposure setting. In VW2015 (and before,) I used this variable to tune in my renders. For interiors, I frequently needed to crank this up to 200 or 250 to get a sufficiently bright image. I tried using the Emitter Brightness setting but it didn't seem to have any effect (as I have found to be the case in previous versions of VW.) I'm using a single heliodon and a physical sky. In VW2016, I've had to resort to changing the brightness settings for each of my light sources. This allowed me to get bright interior renders but it doesn't allow me to easily tweak the light settings between viewports. With the exposure setting, I could crate multiple Render Styles with different exposure settings. That allowed me to have Render Styles for both interior and exterior renders using the same light sources. I also allowed me to apply different exposure settings to different interior renders. Has this setting been moved or has NVW eliminated it? See attached screenshots.

Use "custom renderworks," turn on indirect lighting, and set the number of bounces for interior (assuming it's an interior.) You can adjust emitter brightness to get your scene dialed in. Emitter brightness can be set to more than 100%. For interiors, I range from 150% to 250%.

I found my problem. I save all of my default files (wall styles, line types, hatches, etc.) in one location and then place aliases in each of the corresponding directories in my user library (~/Library/Application Support/Vectorworks/2016/Defaults/... This allows my to keep all of my default information in one place making periodic updates and VW upgrades easier. This approach has worked fine until now. Now, I have to put the physical file in the VW wall styles library folder. All other default files (hatches, line types, etc.) still work with aliases just not the wall styles. I wonder if this is something that could be fixed in the future.

Yes, I saw that. I also tried putting my file in the Walls-Slabs-Roofs directory but it still didn't work. Any other ideas? Has anyone else had trouble with this?

I'm moving up to VW2016 & have run into a problem. I can not get my (not VW's) default wall styles to show up in the wall style drop down list. I have put my default wall styles file in ~/Library/Application Support/Vectorworks/2016/Libraries/Defaults/Walls-Slabs and Walls-Slabs-Roofs directories but they do not show up in the wall style drop down when using the walls tool. Can anyone out there help me? Thanks.

Awesome. Thanks.

Thanks, Hippocode. So GetPref is for boolean variables and GetPrefInt is for integer variables?

Thanks, guys. SetPrefInt did the trick. Why does pref 506 require us to use SetPrefInt while 95 allows us to use SetPref?

Thanks, Markus. That's getting closer. It now redraws the screen but it changes my layer mode to active only, regardless of how it was set initially. Any idea why that's happening?

Hi all. I'm using VW2015 and am considering hiring a contractor who uses VW2012. He says that he has worked with a number of other architects who were using later versions of VW without any problems. He says that they were able to open his VW2012 file, make changes, and then save as VW2012 to send back to him for further modification. In earlier versions of VW, I found that opening files from earlier versions would often result in problems and strange behavior. I haven't, though, tried this recently so I'm wondering if current versions of VW are better at this kind of cross-version exchange. Has anyone out there had experience with working back and forth with different versions of VW? If so, what have your experiences been like and what kind of best practices would you recommend? Thanks.

Yes. And ReDrawAll. They don't work. Here's the script: PROCEDURE ToggleShow2D; BEGIN SetPref(95, not GetPref(95)); SetPref(102, TRUE); ReDrawAll; END; RUN(ToggleShow2D);

Thanks, Raymond. The odd thing is that the script actually does toggle the show 2d option (if you use the script and then go into unified view options you'll see that it has checked or unchecked the appropriate box) it just isn't refreshing the screen to show the new condition. Thanks for filing the bug. Unfortunately, I think that NVW has already issued the last service pack for VW2015 so I don't think this will get fixed.

OK. I'm starting to use VW2015 more now and Raymond's suggestion isn't doing what I need. It's actually just toggling stack layers on and off. I'm trying to toggle the display of 2d information in non-2d views, which is pref 95 not 94. My script appears to be changing the setting but I can't get the screen to refresh without manually changing views. Can anyone out there help me? Thanks.

I'm not sure how Pat did it because his movie wouldn't work on my computer but I usually just cut the foundation wall on both sides of the opening and change the wall height. Then I insert the door in the wood framed wall above with a negative z height to move it down into the notch I created. Good luck.

That would be great!

I was wondering if you could use two separate door instances, one as a cased opening (no door leaf) and one with just the door leaf (jambs set to 0.) The cased opening could be a symbol set to NOT be on the door schedule and the door leaf could then have all of the schedule information attached to it. That way you could still change the symbol for the door type while allowing each door to have unique schedule info. You would still have to manually enter the door type in the door PIO but I don't think there is any way to avoid at least some level of manual intervention with this scenario. Seems kind of complicated, though and again I wonder if you wouldn't spend more time setting the whole thing up, maintaining it, and dealing with unexpected issues than you would just doing it all manually in the first place.

OK, Josh. I see what you mean now. I think that Michel is right about the best way to "automate" this type of system - creating a door from a symbol so that you could make global changes to the symbol while maintaining individual PIO records for each individual door. You might consider just doing this all manually, though, to avoid complication. It will require a little more manual coordination but you're going to have to do some level of manual coordination anyway. You could create symbols for each of the door types (with default data set for each) and set the symbols up to convert to PIO on placement. You could then just use a user field for Door ID. Much simpler and less prone to unexpected problems. Please let us know what you do in the end. I'm curious to see how you ultimately work this thing out. Good luck.

tessaro, I'm confused about what you are trying to achieve. Exactly what are the "slight differences" between various instances of the same door? And where are you going to call out these differences (another worksheet?) How will someone reading your drawings know which D001 you are talking about? It seems to me that either all of each door type (D001, D002, etc.) are the same or they aren't the same door.