Jump to content

Wes Gardner

Vectorworks, Inc Employee
  • Content Count

  • Joined

  • Last visited

Everything posted by Wes Gardner

  1. @Markvl, can you post up the offending window file and I'll submit a bug. Dunno if it's a trim issue, jamb extension issue, stool issue or some combination. If you could include in the file, set up two scenarios - one where it's broken and one where it works OK. Wes
  2. @Markvl is this what you're referring to? Mine seems to work...my jamb extension is set to 3/4" to match the jamb thickness.. (test file included)...maybe it's a particular window config? Wes Window Issue.vwx
  3. @Mitchell (the other one), my suggestion is Door Styles. For any given project, you can create a style and "lock up" (By Style) those components that are common for that project. As an example, the height might be the same throughout so that all the head heights align but the door size would be allowed to "float" (By Instance) so that you can have different width doors. The texture, etc can also be "by style" so they remain constant. Since these are resources, they can be shared and reused (with any necessary tweaks) for the next project. Wes Example Door.vwx
  4. @vassen, I use the automatic dormer creation sequence to build a conceptual dormer getting it close in size and location on the roof. I then ungroup the dormer resulting in roof faces and walls. From there you can use wall styles, etc. on the dormer. Wes
  5. @trashcan, I got lucky that day when I was shooting that sequence...now, when I try to reproduce it, I get what you get...hmmm. In my opinion, if you have it set to Overall, when you drop a texture on a wall, it should do just that...bug! Wes
  6. Here's a rendering...couple of mistakes but...
  7. @Ride, the plan view is just the ordinary Top/Plan view. The viewports are just the standard hidden line produced from "Create Section Viewport" I must admit, there ARE limitations with what I call our conceptual cabinet tool(s) ... some configurations just aren't possible. Here's the file if you'd like to have a look at the setup. Wes Kitchen 2020.vwx
  8. @Ride This is about as good as I can get them to look - base cabinets with solid lines, top cabinets with dashed lines and countertop dashed for reference. Data Tag provides the tagging. Sorry, the image export washes out some of the line weight. These are just our conceptual cabinets...I'm not up to speed with interiorCAD. Wes
  9. @Putman, yup, I've tried tweeking the surface hatch and all kinds of other workarounds but...sorry Wes
  10. @trashcan, you are correct, that is a limitation. Wes
  11. @Putman, you are correct, this is a known issue. You can often correct the vertical coursing issue by checking the box under the Render tab in the OIP - "Use World Z for Origin" (see attached screenshot) but there is no way to correct for horizontal misalignment. Wes
  12. Looking at the model, that particular wall is Wall Style TPS30 EX - it is set with a Top Bounding of Piano [Story Above]. In this model there is no Story Above for the wall style's level to "see" or to bind to. It appears that you've used "Fit Walls to Objects Above"? My Italian just isn't good enough to go through how the walls are set to interface with the roof system. This may be the reason the interior component isn't working properly. My advice is to NOT use Stories and just set the whole model up using Layer bound walls styles. Wes
  13. @alfresco, please review and compare the file I've attached regarding your Story set up to your file. You also need to look at the bounding set up in your wall style (the 6" Generic one). In the Component for the wall, where do you want it to be bound? Furthermore, and I realize this is REALLY unclear, you change the height/bounding of walls either by changing where the top/bottom is bound to OR by changing the height of the various levels in the Story set-up in the Org palette - you DO NOT change the height of level bound walls in the OIP (this really should be greyed out but...). You might want to thoroughly review the model set up document posted at the top of the Architecture section where it goes through some of the "rules" for level bound walls, etc. Wes 2020BakerrMay18 wg.vwx
  14. @Giovanni, best thing to do is post a file with the offending wall(s) so we can have a look at your set-up. Wes
  15. @alfresco, there are a couple of possibilities - your bounding set-up, are there any offsets in your wall style? Are you using a level bound wall style? The easiest way for us to respond is to post a small file with an offending wall in it. Wes
  16. @Kennedyme, I did this kind of quickly, so you might need to clean up the appearance of the tag. Wes Height Width with Tag.vwx
  17. @vtallon2, can you post a file with an offending wall in it? Are you on version 2017 ? Wes
  18. @Kennedyme, maybe like this? See attached file. Wes Rectangle Height and Width.vwx
  19. @Katie M, if I'm understanding you correctly, all you have to do is click on the boarder and hit delete. In the short video, I place a border and then hit the Delete key to remove it... Wes Delete Boarder.mp4
  20. @ashleighguns1, as Pat says, make sure to specify WHICH LAYER, the screen shots provided are set to frame the layer called "2-Floor Layout" Also, if you've classed your walls, you have to tell it what class to frame as well...in my case it's [Wall]-Exterior (see screen shots.) You get to that by clicking the "Options" button in the Wall Framing dialog down at the bottom left. Otherwise, I think you get the error message shown?
  21. @davidwd...If I'm understanding you correctly, are you talking about something like Sweep 2 or Curve Network in Rhino? If so, then no, in Vectorworks you're limited to just one profile curve if you choose the Bi-Rail mode, or as Pat suggests, but then you loose the ability to have two rails... Wes
  22. @Putman, the Windoor classes have nothing to do with the Windoor Plug-In. The door and the bit of wall shown in the file you have were taken from a full project that has both windows and doors. My personal method is to refer to the common elements in both windows and doors as "Windoor" - this saves me one class each time I use that methodology. I apologize for the confusion. To a large degree, the number of classes and thus the "granularity" required on each project can vary a bit. I like to class everything and therefore retain control ALL the way through a set of drawings. Sometimes all those classes just aren't necessary. Wes
  23. @Putman, here's a door you can experiment with, you can turn trim on/off, you can texture the trim as well as the door itself (both inside and out). This door is set up for class controlled attributes Wes Door with Options.vwx


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...