Jump to content

shorter

Member
  • Posts

    3,100
  • Joined

  • Last visited

Posts posted by shorter

  1. I would like to see the wall hole component AT THE SAME TIME as the other geometry in a symbol, perhaps highlighted as a red translucent solid whilst editing a symbol.

     

    When creating the symbol and the object that will become the 'Wall Hole Component' a 'right click' and assign as 'wall hole component', in a similar way we can assign 2d elements to screen plane, would be very useful.

    • Like 1
  2. I think it is important to note that the use of BS1192 class naming does extend to BIM.

    In the CPix Post-Contract BEP, you will note, in section 5.4, it says:

    "Each discipline should provide the Design Manager and the CAD manager with a full list of all layer names to be used on the project. This list should be published to all members of the project team for information.

    Table 25 Layer naming convention

    Discipline - Classification - Presentation - Description

    e.g.

    A-G23-M_Stairs

    [using Uniclass 1.4, I should add]

    Some software solutions suggest that layer names are not necessary but it has been found that the convention shall be used when sharing or exchanging information."

    Whether you include this section in your BEP is of course up to you.

    The work Martyn Horne and I have been doing as part of the AEC UK CAD and BIM Standards initiative, and in order to assist Vectorworks users, in Vectorworks 2015 and 2016 you will find Class Standards Libraries containing AEC UK CAD Standards classes. Object libraries for Walls, Slabs, Roofs, Doors and Windows using Uniclass 2015 could also be provided. Uniclass 1.4 could also be provided if that was of interest.

    Anyone viewing an IFC file will note that 'layers' can be used for viewing

    the model.

    And, of course, you probably still export DWG...

    Classes and other Library content should adopt BS1192 naming conventions.

    The question of adding Uniclass classification to IFC fields, is separate, and should be done when creating your own content, in a similar fashion to inserting 'T-Sheet' or NBS references. Hopefully Vectorworks, Inc. will work on ways to make it easier to add information to IFC fields, and custom property sets in future releases.

    Let us know if you have any (useful) comments on the content provided with Vectorworks, by the way.

    Regards

    Steven

  3. If it has not already been confirmed, 2014 definitely has a problem after upgrading to 10.11.

    If you edit a viewport, and try to change the layers attached to the viewport you cannot see their names. The list is blank, although they do appear if you hover over where their names should be.

    Haven't had a chance to test on a fresh 10.11 install or new Mac running 10.11.

  4. I have had a recent report of VW2012 being slow and am trying to get to the bottom of it and wonder, to those who are claiming VW2012 is slow on recent (less than a year old) and new iMacs, what graphics cards do you have?

    At the moment, the issue we are seeing affects the base model iMac with the Radeon HD 6750M card. The slow speed of drawing a line, for example, only affect one Mac of this specification. All others tested are absolutely fine.

  5. And not just a drawing issue sheet, but a cad data issue sheet...if one is issuing just DWG modelspace data.

    see http://aecuk.files.wordpress.com/2009/05/aecukdrawingmanagementhandbook-v2-4.pdf

    Often wished for some sort of publishing function, or something like 'collect for output' in InDesign.

    Being able to export DWGs of design layers or design layer viewports is good, but we often wish to export many files, and not the design layers from which they are composed, i.e. a batch DWG export.

    If we had some sort of publishing system like Mike suggests then we might make more of the batch printing function. If batch printing or batch dwg export were linked to an automated document transmittal sheet, this would be fantastic.

  6. Is anyone aware of problems using the 'space' in enclosing folder names on the MacOS and VW2011 Architect?

    I have a client that has just called me complaining of Vectorworks not saving because of spaces in the enclosing folder name.

    Never seen it before myself, and nothing comes up if I do a search on the Community Board so I suspect it specific to his server setup.

  7. I have a 'loadfile' script but it has to run from a white background.

    The problem is, if the user likes a black background, then I want the script to first change to a white background (which I am guessing is setpref(16,FALSE);), and return to the black background after running the script.

    However, if the user is on a white background, then I don't want the script to do anything.

    Any tips?

  8. There is a VS on NNA Support site, entitled 'Set Object to Class Attributes'. The script runs as follows:

    PROCEDURE UseClassAttribs;

    VAR

    h : HANDLE;

    BEGIN

    { get a handle to the object }

    h:= FSActLayer;

    { set the object to use the class settings for }

    { its display attributes }

    SetFillColorByClass(h);

    SetPenColorByClass(h);

    SetFPatByClass(h);

    SetLWByClass(h);

    SetLSByClass(h);

    END;

    Run(UseClassAttribs);

    Works fine for one object.

    I have been trying without success, to expand this to all objects in a file, irrespective of layer, class, group, symbol or PIO, ideally without having to select them first.

    Any suggestions gratefully received.

    Regards

    Steven

  9. Dear AutoCAD user...

    Can you export your DWG as an eTransmit? This way the Vectorworks user can see, and reference, if required, your model files to the drawing. As you correctly assume, VW does not see your XRefs if they are not bound. This is probably due to the fact that the XRefs rely on a filepath to your server (or is this stating the obvious?).

    The only way to resolve this is to bind the XRefs before sending the DWG (Vectorworks does this automatically). This is a bit of a pain to both you and the Vectorworks user as the file sizes tend to be much bigger.

    I have found eTransmit much more useful because a, the file sizes are much smaller making it easier to import and b, I am not usually interested in the DWG printfile but the data in it, i.e. the Model file, but for some reason I can never get ACAD users to send their Model data. Don't know why not.

    And Nemetschek, can you do something about the way AutoCAD line styles are imported, or rather please sort it so that Vectorworks line styles are not overwritten by ACAD line styles on import?

×
×
  • Create New...