Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. I'm trying to coordinate my drawing using the Drawing Label Tool. I start with the detail, wanting to coordinate to the Layer, but it is not coordinating. I have checked off Use the automatic drawing coordination from Document Preferences. Obviously I'm doing something wrong. I've read Vectorworks help and forums to no avail. How does this tool work?
  3. Michael Gilbert

    PDF to VW

    We are often asked to redraw supplied architects PDF plans to create marketing materials. If the PDF is a vector drawing then we can do this by opening PDF in illustrator, export as DXF and then import into VW. Any advice on simplest most efficient way would be appreciated. Especially pertaining to page sizes, scaling and duplicate lines from illustrator. Thanks Michael
  4. Michael Gilbert

    Clicking Palette Button

    Just for interest. I have figured out how to use Keyboard Maestro to click buttons. Using If statements, if X axis > Y axis, etc. This can also work for other objects but in each case only for 90 & 180 degrees but does the job for what we needed.
  5. Benson Shaw

    Best way to create roof by NURBS curves or Curved Lines

    Really interesting design and daunting constructibility. Super interesting vwx modeling challenge. Attached find my basic setup. It's not perfect, but really close. A look at the fabrication & construction photos of the golf clubhouse, shows use of short sections (and some really long sections) and assembled into modules for shipping & install. This allows trim and shape at each crossing to accommodate the twists and joins where flat faced lumber crosses curved. Looks like they are kind of set up for it now and using same tech on several buildings. I wonder how many trees hit the dirt for that tee time enjoyment! I tried to array stars or portions of stars on a funnel shape. Maybe others can make that work. A parametric network would really help with the basic grid layout, beam spacing, beam section dims, etc, but I think adjusting for twist anomalies where it flows around complex surface would be hard to program. File's 49mb, so too big to post. But I put v2019 version in Dbox at least for a while: https://www.dropbox.com/s/gaiud7rt5rwq97e/StarLattice.vwx?dl=0 -B
  6. Today
  7. mike m oz

    Custom Surface Hatch

    LRe, provide an image of what you want and I'm sure someone will create the hatch for you or tell you how to do it. Your word description of "one row of 12x24 pieces and second row of 8x30 and have that repeat over and over again" doesn't provide enough information. To create your hatch it sounds like you need just 4 layers. - Layer 1 is the base of the 12x24 pieces. - Layer 2 is the first vertical of the 12x24 pieces. - Layer 3 is the base of the 8x30 pieces. - Layer 4 is the first vertical of the 8x30 pieces. The spacing of each horizontal line is straightforward. Its dash factor will be 1 and its offset the distance it repeats at vertically. The spacing for the vertical lines is also straightforward. Calculate its dash factor vertically and then its width becomes its offset distance horizontally. The start point for each element is critical and you need to work out the relationship of the two at a particular point. Once you know the geometric relationship of the two elements at the start point the rest is straightforward and just simple maths.
  8. Mik

    Vectorworks is REALLY SLOW lately!

    I recently upgraded my PC (details at end) and have seen no noticeable improvement in VW2019 speed over VW2015. (I am on the subscription, tried VW2017 and had so much trouble I stayed on VW2015 as it was at least stable. But alas, Windows 7 & VW2015 are no longer supported.) A file created in VW2015 with a fair amount of single-family home detail (corbels, curves, etc.) was miserably slow for any of the "fleshed out" renderings. With VW2019 upgrading the file to 2019, not much difference. BUT - I notice when in Hidden Line mode, grabbing the model and spinning it shows the hidden line view move around as fast as you can move it but when you let go of the mouse, it asks if you want it to be rendered and then have to wait the usual delay for hidden line rendering. If the reason for this extra delay is the final hidden line rendering quality is better than the real-time spinning it around, okay but I'll take the "quickie" version of hidden line any day! That would save a huge amount of time and it appears the program already has that ability. Why won't VW let us opt for that use of hidden line? Anyway, after thousands of dollars in upgrading I feel like I just wasted a bunch of money "to get current." OLD: VW2015 SP5 Build 290108 Windows 7 Pro SP1 HP Z1 Intel Xeon E3-1245 V2 @ 3.40ghz 8mb cache 4-core RAM: 16gb NVIDIA Quadro K3000M 2gb GFX NEW: Fresh install of VW2019 SP2 Build 463397. Windows 10 Pro for WS v1809, Build 17763.195 HP Z4 G4 Intel Xeon W-2133 CPU @ 3.60GHz 8.25mb cache 6-core RAM: 32gb NVIDIA Quadro P4000 8GB GDDR5 HPZ38c display
  9. Yesterday
  10. Sky

    ID Label Tool

    @Nikolay Zhelyazkov I used the wall style report, but it had this: =IF(GETIFCPROPERTY('IfcWallStandardCase.Description')<>'', GETIFCPROPERTY('IfcWallStandardCase.Description'), GETIFCPROPERTY('IfcCurtainWall.Description')) which generated a description that was different than the on in that box. I actually have no idea where that description is coming from. Anyway, I finally figured it out. It is =WALLSTYLENAME. I can't believe how difficult this was!
  11. Boh

    Details Library

    If you want to be able to reuse details in other/future projects then the details in the annotation VP can simply be turned into a symbol definition and placed in your library. From there they can be imported into other project files.. Note the detail VP itself can't be made into a symbol but the annotation info in it can. As mentioned before you can copy & paste VP's from one file to another - you just need to group them first.
  12. cberg

    Details Library

    Boh I like your approach for details which are specific to project or model geometry. That said, you can also extract the detail from the annotation viewport and put them into a 2d design layer of some sort so that they can be reused from project to project. I'm thinking of generic roof details, millwork details that are typically used from project to project.
  13. Boh

    Details Library

    That's an interesting way to go which I think can work very well. I've have been experimenting with a slightly different way: Since we generally create a 3d model all our elevations and sections are live section viewports. From these we create detail viewports on our sheet layers. The design layer info in the VP's is just used as a template over which, in the annotation space of the VP, we overdraw our 2d details (or possibly place a detail symbol) . Once the detail is completed the design layer's visibilities can usually just be turned completely off. So we end up with detail VP's with only annotation info in them. The advantage of this is: No additional design layers are required for 2d details. Design layer scale is irrelevant - all text/page based info is scaled to the sheet layer (informed by the detail VP scale). Sheet formatting is simple, as all info is in the annotation space there is no tedious cropping of viewports and/or moving design layer info around to fit into a VP crop. Each detail has it's own viewport which can be moved around like a group to suit your sheet. Each detail viewports automatically update their number/sheet directly to the detail markers on the plans/sections. Note that: Details are typically only used in one viewport so why not put it into an annotation space? If repetitive detail info is required then this could be via a symbol definition. Detail info is not generally required to export to dwg - so far we haven't had any issues there. So far so good - the only downside I've come across so far is that live details still need updating before publish even when there is no DL info in them. Usually this is pretty quick though.
  14. Robert Anderson

    Wall Area

    You can do this with Marionette, but the only functions available are criteria-based functions, which makes the Marionette approach somewhat more complicated (compared to, say, handle-based functions).
  15. cberg

    Details Library

    This is something I've been experimenting with the past few months. Not sure if this makes sense, but I've set up design layers at various scales that can be imported into our model for use in detailing. The benefit in keeping the details in model space is that they are viewported onto sheets, and thus you can use automatic drawing coordination to link them to detail markers. The detail sheet is set up as a template. And the Model area is next to the Detail Zone (although I haven't included it in this screenshot. Oh and I also make sure to display objects set at other scales in the Unified View Options, so you can see all the details at once. It makes for slightly messy design workspace, but I try to keep 3d information in one area and the 2d details in another area. The grids are still a work in progress, but they are increments of our sheet size. I would be interested in seeing examples of how others do this since I'm not sure this is the best solution.
  16. tekbench

    Add Leader Crashed VW 2019

    Running High Sierra 10.13.6 VW 2019 SP1 (Build 456974) (64-Bit) Like I said, can't repro at this time, but seemed odd. use a floating OIP, so it's never docked.
  17. Robert Anderson

    Wall Area

    Look at the following worksheet functions: WALLAREA_GROSS (area of walls not subtracting openings) WALLAREA_NET (area of walls subtracting openings)
  18. Boh

    Details Library

    You won't be able to easily set up detail symbols with details drawn in a design layer but annotated in VP annotations. All the info really needs to be either on a single design layer or in the VP annotations - not a combination. If they are all on a design layer you can then create symbols of each detail and file them in your library for later re-use. You are correct that text formatting/page based info will need reformatting when the scale is changed. I have found however that 'generic' details are best set up for one scale and simply pasted into your drawing. They are at a certain scale because that best suits the info it represents. For example a window sill detail which shows all the weatherproofing info like seals and flashings etc needs to be at a small scale certainly no bigger than 1:5. So a suggestion may be for your office to standardize the scaling of your details so symbols can efficiently be inserted with no reformatting required. There was a recent thread on this however where I came up with a workflow to use page based symbols for detail symbols so that text formatting can be retained and different scales. Hasn't been road tested yet tho...: Re transferring viewports: You can't copy & paste a VP from one file to another but a neat trick to transfer those details to a different file is if you group the VP first you can then copy & paste it to another file.
  19. MSLD

    Add Leader Crashed VW 2019

    What OS are you running? There seems to be a lot of conflicts with Mojave and VWX2019. I had similar issues, and the work-around was to undock and resize the OIP
  20. I use the VS-4 Projection tool to set up LED screens quickly when I'm laying out a show. I find it easier than dealing with module counts and all of that. But I think it would be very helpful if one could spec the module depth in this tool. Right now I'm faking it by setting the frame dimensions to 0 and putting in a depth. It would also be great to be able to make supports, either hanging bumpers, ground support ladders, or skids on the fly as well.
  21. Yes that was the issue for Wireframe, but I am still seeing the issue where they disappear in Hidden Line and OpenGL.
  22. It works fine in screen plane, but all the other ones don't work. I tried turning those settings on and off and it still doesn't work.
  23. BJRobinson

    3D plants

    Thanks Bob. I bought VW through Ozcad. So I assume I have all they have as there are some in my resources. However I need a lot more.
  24. Have you tried adjusting the setting to adjust the level of "grayness" when you publish?:
  25. Ok. Thanks Matt, I appreciate your time looking at this. I'm glad this little issue is sorted on 2019. We are holding off using 2019 for now as it looks like it has too many other bugs and will effect our productivity. Perhaps when the next service pack is issued we may start using it.
  26. Anyone have VW2009 or later they can sell with license
  27. tekbench

    Add Leader Crashed VW 2019

    Hey all. Strange thing this morning. I'm on a Sheet Layer, detailing a Viewport. One of three Viewports on the Sheet Layer. I have double clicked the viewport in question, and have selected "Edit Viewport: Annotations". I select the Call Out tool. I create a Call Out. Type in some text. In the OIP, I select "Add Leader". I drag the new leader around, put it where I want it, click once, then hit the 'enter' key (for no real reason, just happened to tap it.). Vectorworks quit unexpectedly, and instantly. No beachball, just hard stop. I can NOT repro this crash at this time. I re-opened the 'backup' version of the file and kept working. I have not touched the original file that crashed. Possible bug? I also grabbed the Apple Crash Report if that is useful. Didn't see anything in the known issue forum. Kelly.
  28. You might be even more profitable if you would work in DWG as you would get to write more hours on the projects because it probably will take you more time to get the project done. ūüėČ That being said, using VW has made it possible to meet project deadlines that would not have been possible when using AutoCAD because VW was (and is) so much more efficient for certain things than AutoCAD. However, I do fully agree that the DWG compatibility needs further improvement as I too still need to "fix" DWG files too often to make them comply with client's or other (inter)national standards or to simply make them usable in AutoCAD as you have noticed. Some basic things are still missing in the import/export that simply makes VW a no go for certain projects even though from a drafting perspective VW can do the job but the DWG conversion is simply lacking too much on those basic missing things. But... given the differences between VW and DWG there will always be things that will need fixing by opening the DWG file in a DWG based program (AutoCAD/BricsCAD/Draftsight etc) and fix those things in there. The better the conversion is the easier it may be to fix those remaining things that cannot be easily translated and less time we have to spend on that. I don't expect perfect translations to DWG because after all there will be a point where VW will have to consider whether it is worth the investment in time and money to get those rare things translated 100% correctly, especially if there is no real equivalent in DWG. If you have ever seen a DGN to DWG conversion you'll know what I mean, as e.g. those are rarely usable from a layer management perspective even though Bentley and Autodesk have an agreement on using each others API's/code for importing/exporting into each other's file format.
  1. Load more activity

 

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.

√ó