Jump to content

Boh

Member
  • Content Count

    1,336
  • Joined

  • Last visited

Everything posted by Boh

  1. Adding 3d loci to the site model source data works for me and I am using VW2016. Maybe what is happening is that you are trying to make the site model bigger by adding 3d loci beyond the boundary of the current site model but not updating the site model crop object? VW by default creates a site model crop around the boundary of the original site model source data. I've quickly tested and found that adding 3d polygons to the source data will automatically redefine the extents of the site model crop, however adding a 3d loci does not. I.e. the site model crop does not change if you add 3d loci beyond the extent of the current site model but it does change if you add 3d polygons. I suggest that you try, (after adding the 3d loci), right clicking on the site model, click edit site model crop, and delete the crop object.
  2. Ok cool. Thanks Gerard. I hadn't imported a plug-in before so have learnt something new today! Bonus is that it actually works!
  3. Thanks for that. Yes I wouldn't normally use this but I am reworking a symbol library and template files from scratch so I thought this might be useful. I have a lot of light symbols for example that I would like to set default records for. With that being the case, for me it would be better suited as a script command contained only in the symbol library file rather than as a menu command.
  4. Hi Gerard. I tried downloading the file, unzipping, copying contents of file into a new script and it didn't work. I'm clearly doing something wrong? Can you point me in the right direction?
  5. Under "tools" menu there is a rename classes tool. You can add a prefix or replace certain text in many different classes in one go. You can add a prefix with a "-" to create a hierarchical class naming structure. Ideally however, if you are doing similar projects using the same classes you would create a template file with classes already created instead of creating them as you go. This is fairly standard practice. Your suggestion of having a group class - a class in which groups are placed so that you can control visibilities of the variously classed objects contained within the group in one go is another option however it does mean that in order to see the objects contained within the group both the object and group class need to be set to visible. I've used this technique and it is o.k. however it can get confusing for another user trying to work with your file as occasionally they wil lbe stumped as to why certain objects aren't visible even though their class is set to visible - not realising of course that these objects are in a group class which is turned off.
  6. Hey TKA. Yes that is the "hierarchical" display mentioned as attached screenshot: In addition to the viewport class visibilities dialogue it would also be great to see hierarchical display used in the "new class" dialogue. Currently I have to scroll down through dozens and dozens of template file classes to find the one I want to import. This would be a lot quicker if an option to show in hierarchical display was provided. Btw there was a recent post about setting up viewport templates and using the eyedropper tool to transfer visibilities from one viewport to another:
  7. I understood it to be about hierarchical display of classes in the class visibilities dialogue of viewport settings.
  8. Yes, this would be handy. Meanwhile there is this script from @Pat Stanfordthat will update all viewports on a sheet: Procedure UpdateSheetLayerVPs; {Selects, Updates and Deselects each viewport on a sheet layer} {Revised to handle both sheet layer and section viewports} {? 2008, Coviana, Inc - Pat Stanford pat@coviana.com} {Licensed under the GNU Lesser General Public License} Begin DSelectAll; SelectObj((ST=REGVIEWPORT) or (ST=SECTVIEWPORT)); While FSActLayer<>Nil do Begin UpdateVP(FSActLayer); SetDSelect(FSActLayer); End; End; Run(UpdateSheetLayerVPs);
  9. Nice! It would be great if this was available straight from the selected object right click context menu rather than have to go to the nav palette.
  10. Yes there is similar control in the edit class dialogue which is great for Turing on or off a class in all viewports or saved views in one hit. I have a "NonPlot" class for drafting lines or anything I use that I don't want printed. I use the edit class control to turn it off in. All viewports before printing. Very handy.
  11. Boh

    Curtain Wall Design

    I am interested in this too. I often have situations where building elements span multiple floors. Where these elements are identical on each floor, such as columns or structural walls, I model them floor by floor using symbols or design layer viewports so they can be edited efficiently as well as show up correctly in top/plan view for each floor. i haven't found an efficient way to do it yet where theses elements change from floor level to floor level. Avaysee's curtain wall is a good example of that. What do some of the more experienced vw users do?
  12. A wishlist item has been added to make class descriptions more user friendly.
  13. The class description needs to be more visible. At least not be an additional click away in the "Edit Class" dialogue. It should be viewable and editable from within the "edit Class" dialogue. With the common practice of classes being duplicated the class description is also duplicated and invariably not updated to suit the use of the new class. Clearly the description needs to be more easily kept up to date with the use of the class otherwise it is a bit of a waste of time. I note that the class description is included as a column header in the "New Class" dialogue so surely it is not hard to add it to the organisation dialogue as Zeno suggested.
  14. Yes please! Is there anyone out there who uses it in it's present form? There is a thread that discusses being able to generate a worksheet of used and unused classes in a file. If this could be integrated into the organisation dialogue that would be even better.
  15. Thanks Pat. Yes I've tested this approach out and the flip options are available as a second click when you make the symbol active in the resource browser. I think that is the direction I'm heading along with developing a library of door & window styles. This is fine for new doors/window but does not address the issue when editing/revising an existing drawing. Perhaps a wishlist item could be VW providing that automatic second click orientation option even when just dragging existing objects into walls.
  16. Yes I only discovered it recently and I'm finding the more I use it the more I like it.
  17. I have wrestled with this same issue also for my templates. My work around is to have the template set up with viewports on each sheet for the various required plans with all their class/layer/overrides/visibilities already set. In a new project file made from the template I will typically initially develop an as-exisitng or proposed floor plan first which is nicely formatted/cropped and positioned on my sheet exactly how I want it (complete with a drawing label in the annotations). Then once I need to start on another drawing, say an electrical layout plan, I will copy the viewport of the previous floor plan and paste-in-place on the Electrical Plan sheet. I will now have two viewports on this sheet - one being the one just pasted and the other being the default "electrical plan" viewport. I then use the eyedropper tool to copy the attributes of the template viewport to my pasted in place viewport and then just delete the template viewport. This approach gives me the correct visibilities on a nicely formatted viewport which line up with other plans on other sheets. Even the drawing label updates. Some edits/adjustments are usually required but generally this works o.k. As mentioned by Art V it does require that classes/layers names are standardised etc. It would be nice if standard viewports could be made into symbols that could be saved in a library file and brought into files as required. I'd be interested in how others might approach this.
  18. I don't know about a script but why not just use the magic wand tool (otherwise known as the"Select Similar Tool")? Adjust the tool settings to select by class then choose an item on the class you want and it will select all other selectable objects on the same class.
  19. I prefer to use the Windoor tool which can produce either windows and doors also in combination units. (i understand it is only available in Australasia). Typically I have many different types, sizes or styles of windows/doors in one project with multiple duplicates or similar instances of each type throughout the file. Using the tool each time to create a new window/door seems slower to me as you either have to update the default settings of the tool each time you create a window/door or as Pat mentioned use the eyedropper tool once the unit is created. Also when designing or revising drawings you are working more often than not with existing windows and doors and so are always taking them out and reinserting back into walls. My method of duplicating an extg window/door and flipping it is pretty quick and ensures the exact same style of door/window is recreated. The only hassle is having to flip the door around. I think it would be a good development for VW to address this little issue in future releases. For now I think a good work around for me would be to create symbols of each common type of door/window in the file. When you "make active" the symbol in the resource manager it then gives you the option of selecting the orientation when you insert it. (Note that just dragging the symbol from the resource manager does not give the orientation selection options). I need to investigate window/door styles more as I imagine this will help speed things up too. At the moment I don't have a library of door/window styles and tend to create a new one for each project.
  20. Thanks for the reply however the video doesn't really respond to the question. The video was about use of the door/window tools and creating them and inserting them in walls in the correct orientation as you go. It didn't discuss controlling the orientation of a door/window that you already have in your drawing and you want to insert it into a wall. Mostly I create new doors and windows by duplicating already existing ones and then moving them into the correct wall. I don't use the door/window tools much once I have some of the correctly set and formatted doors/windows already in the drawing. Perhaps this is not the best workflow as having to keep flipping doors and windows around can be time consuming.
  21. You shouldn't have to manually save your file all the time. Instead You can change your preferences for how often back ups are created. Go to tools menu then options. It is under the auto save tab I think. i have backups every 5 minutes and save 50 backups. That way I only lose max 5 min of work if it crashes. also are you getting a lot of crashes? If you are getting a lot perhaps you need a system check?
  22. Re your approach. You have essentially still have two models as your "walls to be demolished" are replicated in different classes on both your existing and demolition plan design layers. You do not need to replicate these if you don't want to. Instead if you set all your wall and wall component classes to "by-class" attributes then you could just have one set of "walls to be demolished" objects placed on a demo class which has dashed lines. Then in your as-existing plan you can use viewport class overrides to change the dashed lines into solid lines to match the other "walls to be retained" objects. The override effects only that viewport, elsewhere the demo walls would still have dashed lines. In this way the same walls will be dashed in your demo plan and solid in your as-existing plan. i think also in your approach you are using design layers to control visibilities when this is really the main job of classes. Layers are more for containing groups of objects and (in architectural work at least) usually represent different z heights of a building(basement, ground floor, ceiling, roof etc). For example in my suggestion above both the walls to be retained and demo walls are on the same floor so can be on the same design layer (with their visibilties controlled by classes). In fact if you want you could also have your proposed walls on this same design layer as well with one design layer being used to generate your as-extg, demo, and proposed drawings. Generally I wouldn't have multiple design layers representing the same z elevation in the same model if one will do the job. Re the issue about walls and doors: my file set up discussed in my previous post with seperate demolition and proposed models makes it easy to resolve. In my demo model the "walls to be retained" are modelled with the windows to be removed in these walls shown dashed. In my proposed model on a "proposed floor plan" design layer the same "extg to be retained wall" is also modelled but this time with the new door/window configuration. Portions of the "extg to be retained wall" where a window is removed to be filled in with new wall are just "cut" out of that portion of extg wall and placed in my "proposed" wall class. Note that I am not using the same wall to show both demo and proposed as I am using seperate models for these. I don't know with this scenario of different extg and new window configurations there is an easy way to have the "extg to be retained wall" only modelled once. Perhaps others can chime in on that as it is not how I work, I'd be interested to know however. btw as all my doors and windows are inserted into walls I just leave them on the "none" class as their visibility is controlled by the wall they are inserted into. I don't bother with classes for extg and new Windows though I do have a window demo class so that these windows can be shown dashed. Re your query about stories. They are useful for multi floor buildings as they essentially provide a z=0 height reference for each floor. I don't use layer levels myself but I understand that you need to have stories set up in your model to use layer levels. hope that is of some use to you! Cheers
  23. Hmm, script link not working unfortunately...

 

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