Jump to content

Joe-SA

Member
  • Content Count

    212
  • Joined

  • Last visited

Community Reputation

20 Great

About Joe-SA

  • Rank
    Journeyman

Personal Information

  • Location
    Grand Rapids, MI

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. To make this a little more clear for newbies......use the concept of the 'container' class. For example, you can take a portion of your floor plan objects and put everything unique to Option 1 in a single Group. Place that Group in a class called Option 1. Do this while the class structure inside the Group is preserved to your original class structure. Turn off Option 1 class and the whole Group is turned off. Do the same for other design options. Groups are only one of many objects that function as containers where the container class can be different from the class of the objects inside.
  2. I agree that there is more than one way to skin a cat. I think VW learned in the early 2000's to add features all they want but be very careful about removing them. The Trim Command vs Split Tool comes to mind. Since then the number of different methods to do the same thing have only grown. I find it interesting that you don't really 'like' the method very much (of placing most or all text and dims in annotations) but you do it because you feel it is the prescribed method. I never felt that way. The first time I tried to do plan dimensions in SLVP Annotations I immediately abandoned it as far too cumbersome with little benefit over what I was already doing...that is, isolating model objects and sheet notation objects on separate Design Layers for floor plan development. SLVP Annotations was a welcome addition in other areas and we use them extensively on every project. It just isn't a hard and fast rule and we don't force ourselves to use them where we feel their use is more of a detriment to the task at hand. For instance, the benefits we gain from generating building and wall section details off of a fairly detailed model far outweigh the difficulty jumping in and out of SLVP's to do overlay drafting and notations. I actually had a long running debate with a former co-worker who disagreed with this and insisted on drafting all of his wall sections on design layers just so he didn't have to deal with annotation layers. That's crazy talk. ūüôā Back in the early days of DLVP's and being able to 'flatten' them I even thought we would move all of our detail development including notes over to Design Layers. The benefit here would be maintaining the model generated wall section but being able to quickly move all overlay drafting elements and notes around without the constant jumping in and out of annotations for each detail. At the time there was some limitation...the graphics of a 'flattened' 2D DLVP wall section just didn't match the graphics of an SLVP wall section so we never made the switch. I think I ranted in an old forum post about this at the time. I never re-visited the issue. I think one of the greatest assets to using VW is the kind of flexibility it gives based on your own needs and preferences. People like RLB who started this thread might be searching for 'the one best method' but it is more about what is best for you. Here you have multiple people who have been using the software for decades at a very high level but all using very different methods and all of them moving forward with the software. It does make the learning task a bit harder for new users but in the end your skillset is better for it. Lately I've had young new hot-shots coming in and actually buying into the system, taking the training I give them, and building on that foundation to advance our use of the program even further. They teach this old dog new tricks all the time.
  3. A couple things to add here.....turn what you import into an Auto-Hybrid object to get proper 2d/3d hybrid output. Also, crank up your Smoothing angle in the Viewport Rendering settings for any hidden line work to eliminate all the facets of the curves. I often use 25-30 degrees.
  4. I guess I'm a little confused by these replies from these very experienced users. As a VW user since the 90's I have a different take. Any time I have text in a Design Layer the scale of that Design Layer will always match the intended scale of the Sheet Layer Viewport. Certainly if I'm cutting a detail from a model then all the text will be in SLVP Annotations and source scale won't matter but many details are simply drafted and noted in a Design Layer and then viewport'ed to the Sheet Layer. Some sheets may have a mix of multiple scales drafted this way. The scale of those detail Design Layers will always match the final printed scale. This insures a 9pt font no matter what scale the detail is ends up the same size on the printed Sheet. The scale of my plan layers (and thus my model) will always match the printed scale of the plan on the sheet....usually 1/4" but not always. My plan notations and dimensions are always on a different Design Layer from the hybrid plans. My fonts scale properly to the printed floor plan no matter what plan scale I'm using. I would never dimension an entire floor plan from sheet layer annotations. The Site Plan Design Layers will also be scaled to the intended print scale. The floor plans (which are at a different scale) get Design Layer Viewport'ed into the Site Plan Design Layer and get re-scaled as needed for both the Site Plan and the Site Model. Again, any 9pt font on a 1 to 30 site plan prints the same as all the other 9pt fonts on all the other scales once they all get to the sheet. The only time this is not the rule is with model generated SLVP's like Building Elevations and Sections or Enlarged Floor Plan details where all the text exists exclusively in the annotations layer in the SLVP. In this instance, the source Design Layer's scale doesn't matter.
  5. Thanks Matt. We are not usually early adopters but with VW2021 we might need to make an exception.
  6. Something like this is what I'm picturing you are trying to make. This is one Custom Stair Object with 4 winders and 5 straight runs. If I need a configuration that I can't make in a single object I will stack two stairs and just offset the top of the bottom run and the bottom of the top run and piece the two together. This can happen with some landing configurations or if the tread width changes in a way the plug-in can't handle.
  7. The DLVP's are always updated first because without doing so nothing shows in Hidden Line in the SLVP. We are not seeing this impact the Renderworks result in the SLVP. We are seeing the same behavior when rendering the DLVP directly from the design layer. It doesn't appear to be an issue with SLVP's at all since it is happening before we even get to the sheet. Renderworks is simply ignoring the cut.
  8. I'm quite certain this can be done in a straight forward fashion using the legacy Custom Stair Tool. If you don't have access to it you can edit your Workspace and move it into a tool palette. This is the only stair tool we use having never found its replacement very useful.
  9. We are having a similar issue with our perspective Section Viewports that did not exist in VW2019 but has persisted through VW2020. We have not yet tested in VW2021. In our case we are creating perspective sections where the camera is not in the room but set back from the cut plane. Although they are generating correctly in OpenGL the Renderworks engine is failing to recognize the section cut. We have seen this when generating section SLVP's using the clipcube. We have also seen this when generating section DLVP's and then creating a second viewport to the sheet from there. In both cases the line work and OpenGL recognize the section cut but Renderworks is showing the full model as if the cut didn't exist. We are getting the same behavior when rendering in the design layer itself. In the attached image you can see the hidden line foreground only, the Renderworks background only, and the combined image. This works as expected in VW2019. Any chance this is also fixed in VW2021?
  10. Make sure the fonts you are using are equivalent on both platforms.
  11. Tight construction schedule and no need for a finished 3D presentation led to a lack of finesse in the model. With more fine tuning and maybe some displacement mapping the 3D could have been improved. This was done in VW2016. Computing speeds and VW's memory management were quite a bit different at that time.
  12. I find it easier to just make the entire countertop out of a FLOOR object and cut the sink opening out of it instead.
  13. I'm not an expert in it but the Surface Array tool may allow you to take a symbol that represents your first extrude and array it along the warped surface. I've been waiting for years for the Extrude Along Path tool to allow for a symbol based profile similar to how the Framing Tool can link to a custom symbol profile.
  14. We recently did a series of log houses constructed with half-logs hung on a standard 2x8 stud wall. We put a log texture on the face of a 5" thick exterior component. We had to offset the side elevation texture to account for the lapping of the logs as they turned the corners. Custom corner log symbols showed the full round ends of the logs while other elements like log brackets and fully modeled gable log trusses assisted in hiding the lack of depth in the wall texture. We used window and door symbols with custom hole cuts and splayed edges to achieve the log recess. We had to 2D mask overlay the flat faced wall in the details with actual half log profiles. This wasn't perfect if your intent is photo-realism but it worked very well for CD production with model generated elevations.
  15. Try a Subtract Solid with a big extrusion to remove the tapered portion from a square stair object. Make it a symbol if you need to clean up the 2D presentation. This preserves the original stair object for later editing. Seems to work with both current and 'old' Custom Stair Tool. My firm is one of those that has never converted from this old stair tool except in special circumstances.

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

√ó
√ó
  • Create New...