Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by jtempleton

  1. @Wes Gardner thanks for the reply. I understand why annotations should be done in a viewport space. And I always aim to evolve as the technology does. But in terms of windows and doors, can you articulate why using data tags would be a better way to generate a window and door schedule, if that is your position? (vs. using the tags available in the window and door object settings) Do the two features work essentially the same way? I like the tag to show up in both plan and elevation view for my projects- do data tags accommodate that, or would I be placing double data tags to achieve that goal? Do you have any good idea/ tip/ workaround for compiling a skylight schedule, or is the "old fashioned" way, the best we can do at this time? I did search the forum to see if I could dig up any ideas/ suggestions, but did not come up with anything. Thank you for your reply. I really appreciate. - julie
  2. I have skylights inserted into roof objects. I'm trying to determine the best way to collate them in a schedule, as the window and door schedule worksheet "create report" feature does. After looking at the data tag tool, it seems I'm not able to link tags to this type of object. Further, I'm not able to assign any sort of letter value using a number tag, and I'm not able to use the tag style for windows or doors, guessing because I'm not actually tagging that type of object. (I can place a window or door tag on a skylight, but I am not able to see or edit the text of the tag, and a yellow triangle with an exclamation mark appears in the tag). Would be great to have a way to automate this process more, but I am finding zero ways to automate, link, make it easier specifically for skylights. Any tips appreciated. In watching the video about data tags put out by Vectorworks ( I believe in September of 2018), I'm still a bit confused about how it works, and how to gain greatest functionality from the tool. The video seemed to suggest that the door and window tagging will be going away at some point in the future, so get to know the data tag tool. How do you deal with window and door schedules, and is there a way to break down schedules say by floor or story, and interior vs. exterior door types? Again, any tips appreciated.
  3. I love creating polygons over my elevation viewports when the board and batten or brick doesn't line up, then clipping out holes so the windows show. Then adjusting the holes when I move windows. Surprised you don't like this method, Tom. But I do like your blame the printer work-around. (sarcasm) I REALLY want the exterior wall hatches to align from layer to layer, floor to floor, particularly when the walls align.
  4. And, here's an additional question. I have replaced the hatch associated with the surface texture, which was the only way I was able to make this change from batten strips at 8.5" to ~ 24" oc. But, and this was also true before I changed the associated hatch, the hatched don't line up floor to floor, though the walls do line up, which is maddening. I'd like the batten strips to continue vertically from first floor to second floor, rather than being offset as shown. Any ideas on how to accomplish this?
  5. Michael- will this affect the texture globally or only in the drawing file in which I am working?
  6. To reiterate, STAIRS. The tool used to be pretty good. The new stair tool bogs down making it impossible to work with. Are people making 3d geometry to stand in for stairs? I don't know how people can even use this tool and still have functional files. The lag t i m e i s SO l o n g when I make small edits or move a stair. I'm doing pretty simple residential drawings. Windows- would love to be able to easily make a cottage style double (or single) hung window. A slider that is XOX where the center panel is the size of the two side panels combined, instead of 3 equal panels. And a Nana type bifold glass door, where one panel also works as a single door. Viewport editing that does not crash. I had excellent stability after mini cad became VW . I skipped a few years, and upgraded to 2018/2019 and the stability is like one of my original mac laptops circa 1998. I get several crashes a week. Which, back in the day would have been pretty normal, but things should be working better in 2019 than they were 20 years ago.
  7. I'd like to create simple elevation line drawings. I currently use wall textures which, of course, in hidden line rendering, show as a hatch. Without knowing how to create new textures and associated hatched, I'm limited to the available hatched in VW architect. Is there a way to apply a hatch to a wall (or exterior wall component) so that it renders as desired? For example, VW has like an 8" board and batten hatch, but I want something with greater spacing. I dont see where it's possible to edit textures the same way it is hatches. I'm sorry if this has been answered before. I searched, but didn't come up with exactly what I was looking for. Thanks
  8. I'm having this same issue with walls doing nothing when I ACE> Fit Walls to Objects. I'm using a roof object, not roof faces, so I don't think there's any "leaks" in the geometry. Trying to get a section to look correct where there would be a scissor truss, and also cheat it, so I have accurate exterior elevations as well. To achieve the look, I create two roof layers, one roof with the exterior pitch, and the second layer with a roof with half the pitch to mimic what would be the bottom chord of the truss. I fit the walls on the main floor plan to the layer containing the roof with half pitch. I then create a layer for the gable end walls in hopes of generating this geometry automatically for the elevation and section views. Are there any other tips for making this work, or is it just a buggy and unpredictable feature? I've had it work so pleasingly well, terribly, and not at all- with some success trouble shooting, except that sometimes one fix works here but not there. Does binding walls by layer height and elevation affect this command? I've tried copying the walls and roof to a new file, lowered the base elevation of the layer on which the walls are contained, removed wall peaks after each attempt, deleted and then created new walls using different types of walls, created new roofs, shortened the walls so they don't interfere with the roof edges- and all kinds of other things. Screen shot shows the walls selected to fit. Spending more time troubleshooting this than actually getting work done.
  9. Hi Jeremy, Thanks for the response. These are good tips that I wouldn't have known to check on my own. I will test it out to try to determine the problem. I didn't think to check the workspace. This definitely occurs in all files so far, and sometimes I even get a crash when returning to the viewport. Fun!
  10. It used to be that when editing viewport annotations, right click, edit design layer (or elevation or section in place) then clicking the "Return to Viewport " would put me right back to where I was working in the viewport when I left. Now, it navigates back to the sheet layer, in an odd place on the page, usually not near where I was working, and I have to exit the viewport and then double click to open up the viewport for annotation again, adding two extra steps that previously did not exist. Will the previous functionality be restored to this feature? Let me know if you want more details or a video screen grab. Thank you.
  11. I have not had so many crashes since vectorworks was called Mini Cad 7. I'm using most current version of VW (2019 SP4) on a MacBook pro 2.5 GHz intel core i7, 16 GB High Sierra 10.13.6. I've started using the section viewports tool, creating the viewports on sheet layers and editing them on design layers, rather than my previous convert to lines method of creating sections (before section viewports worked they way the do now). I get frequent crashes when "editing in place" via a section viewport. The crash most often occurs when I navigate back to the section viewport after I've made the changes I wanted to make in the building model on design layers. I've fairly new to 2018/19 versions of VW- I like the section viewport feature, but the crashes are frustrating. I do have back up files set to save every 5 minutes, but the disruption in work flow is frustrating. I'm not too keen on updating to Mojave, but would consider if it would fix the crash issue. This does seem to happen multiple files. (So I tend not to think it's an issue with this one file that's causing the crashes today).
  12. I have window ID tags displayed in elevation viewports. I have assigned a class to the id tag so I can turn it off and on independent of the window depending on the view / drawing. In very small windows, the exterior trim covers /obscures the ID tag (because the tag is wider than the window). I've tried changing the attributes of the trim class to no fill, but that has not yielded the results I am looking for. I also have exterior trim in it's own class so I can keep it off in plan view. I tried to move class display order around, but that doesn't seem to be a feature in the class display options of individual viewports, nor in general. In the window settings dialog box it displays the way I would like for it to display. Any tips on what to try to achieve the desired display properties? Changing the attributes of my "exterior trim" class to no fill does not make a difference in the way this renders in hidden line. The window ID tag has a solid fill (both classes mentioned set to "use at creation"). Any guidance appreciated. Thanks in advance. - Julie
  13. Thank you all so much for the replies. The file was converted from an older version. The issue was repeating, but to a lesser degree with the copy + paste to a new file (but there were also fewer objects in the blank file... so?). Ultimately I did a save as, to make a new file. I deleted the offending section viewports & their container layers from the file, created new design layers for the section viewports, new section viewports on design layers, then section viewports on sheet layers (is that an excessive extra step?) and was able to get this to go away. I can't say exactly what it was for certain, but it seems to be rectified. I'm almost afraid to open my file this morning for fear the issue will reappear. @Stephan Moenninghoff it is possible there was an extruded open poly offender- good tidbit to know. Again, I thank you all for your consideration. The responses sparked many ideas about what could be wrong. I work alone, am completely self taught in VW (since mini cad 7) and all the discourse on this forum, youtube videos and VW resources by others have helped me tremendously over the years. You served as my weekend tech support, and truly, I am grateful. Until my next catastrophe.... Happy New Year!
  14. I appreciate your input, and apologize for my ignorance. If I knew more, I could ask better questions. I recently updated to VW 2018 from 2014. I used to make sections by model > cut 3d or 2d section, and detail a section from there using lines and basic 2d graphics. That is gone, and I'm struggling with how to generate section views that I can work with. (If that information is of any insight- or if anyone has insight on how to do this efficiently, that's helpful as well) I've tried making a viewport model on a design layer, then for elevations for example, I create sheet layer viewports of each of the 4 sides (front, back, left, right), and draw over that to get the appearance I need (showing siding and trim details for example, + annotations). To make sections: I used the same viewport of the building model to create section viewports on a sheet layer. I though maybe the issues was making a viewport of a viewport, so I created new section viewports, cut from the design layers containing the floor plans and roofs. But I get the same result in hidden line rendering. As far as symbols, I'm using all 2D/3D symbols + base & wall cabinets from the VW tool set. It looks like it comes from the windows. The model looks fine in a wireframe view, usually (first image) but sometimes shows the disaster lines as well. If I try to convert a viewport or copy to lines, I definitely get all the disaster lines. Then the rendering happens, obscuring things the shouldn't be obscured. I've tried ticking and unticking viewport options in the object info palate and changing class visibilities for the viewport with no success. I don't use a ton of classes, so perhaps I should revise that habit. I did assign a unique class to exterior window trim (in hopes I could turn it off in plan view, but keep it in elevation, this has been unsuccessful, however. it still show in plan view even with the class turned off). In terms of an origin issue, I'm not sure how to check on that. But here's what I did, ctl +a then ctl + 6 to fit all objects on all the design layers referenced in the viewport. normally if I have some origin point the fit to objects will revel that. I might not fully understand that point. But I do get that problem occasionally if I import a survey into a drawing file. Typically I import the survey into a blank file, and copy and paste what I need to avoid getting weird objects in outer space. My drawings are relatively small, I would guess.
  15. I'm trying to create a section to work with, and these invisible lines obliterate the details of the drawing. I've tried changing class visibilities, rendering settings..... Can provide more details, but wondering if it's something totally obvious that I'm just missing.
  16. Eddie is right. I have been thru this with tech supportthey tell me the following: Currently the 64-bit Windows OS is not officially supported by VectorWorks. VW 11 is not optimized for the 64 bit processor. Although VectorWorks 11.5 may run on the 64-bit OS it is not recommended. Microsoft's Web site says that "Windows on Windows 64 is a 32-bit Windows subsystem that allows you to run 32 bit applications on 64-bit Windows. Because 32-bit applications run in an emulation mode, Microsoft recommends running 32-bit applications on 32-bit hardware for optimal performance." Currently the 64-bit Windows OS is not officially supported by VectorWorks.
  17. Ray- Thanks for your input. Service Pack 2 actually did help with the laging when using ctrl. commands. I do still experience some, but not as much, nor as severe. My system is brand new, and XP was just installed with in the last 2 months, but I have not used this computer untill finally making the VW11 upgrade. Tech support suggested I un & re install VW. I will try that when time allows. Although I must say, after all the time spent with this upgrade...is it really worth it? Appologies if I am using this board improperly ("where is the official response to this thread") Thanks again- Julie Templeton
  18. Forgive my ignorance in regards to the 64 /32 bit thing. I dont know how the tech support guy would even know which version of XP i am running (32 or 64 bit) or how he determined my AMD Athlon was a 64 bit, Because I didn't even know. So I asked the guy who built my machine, and he said I definitly do not have 64 bit anything, everything is 32 bit. So there is still no explination for the lag time when using ctrl key comands. Although- I installed service pack 2 today, and that may have helped. It seems it did, but too early to tell. (quick tests provided good results, but in time, who knows if the stability will decrease) I see you have SP2, Ray, and perhaps this was in fact my problem, as you dont seem to have any. If not, I move on to the graphics card....perhaps. Thanks!
  19. I checked out this board after upgrading to 11.5.1 this week. I too experience the same speed issues described in the first post on the topic. I am running on windows XP on an athlon amd procssor, new mother board, and and older but clean hard drive w/ 1 G ram. I am totally frustrated by any comand using the control key, ctrl + m, ctrl + z, ctrl + b, all of which i use ALL THE TIME, using these causes delays of up to 30 seconds. Funny, the commands I first started using to increase my speed and productivity, are now slowing me down. (btw i am not on a dell) so I read all the threads here, and sent 2 e mails to tech support. I got a reply today from tech support guy dave: Currently the 64-bit Windows OS is not officially supported by VectorWorks. VW 11 is not optimized for the 64 bit processor. Although VectorWorks 11.5 may run on the 64-bit OS it is not recommended. Microsoft's Web site says that "Windows on Windows 64 is a 32-bit Windows subsystem that allows you to run 32 bit applications on 64-bit Windows. Because 32-bit applications run in an emulation mode, Microsoft recommends running 32-bit applications on 32-bit hardware for optimal performance." Currently the 64-bit Windows OS is not officially supported by VectorWorks. I dont get all the technical mumbo jumbo- I'm and architect, not the tech person. But this seems completely absurd to me. Also, are thoes of you who experience pouring of mollasses in winter when trying to use control key commands running a 64 bit system? sorry for the lengthy post.


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