Jump to content

Taproot

Member
  • Posts

    510
  • Joined

  • Last visited

Posts posted by Taproot

  1. @justinekwood  You can set overrides for colors in viewports either by layer or class. 

     

    Option 1:

    1. Move the dimensions to their own layer i.e. "Plan-1-Dimensions".
    2. On the sheet layers, select a viewport of your plan. 
    3. In the OIP, hit the "Layers" button.
    4. The following dialog will pop up. 
    5. Click the colored cube button for the layers you want to override the colors for (example - Main Floor) and then hit the 'Edit' button.

     

     

    17012819_ScreenShot2021-01-18at10_42_20AM.thumb.png.ebba520bc18bdeedc00b9f1cc23263ac.png

     

    The following dialog pops up.

    Override the attributes that you want i.e. pen foreground to red (for the dimensions layer).

    For all of the other displayed layers, you can select them at once and override their attributes to black and white.

     

    2023583363_ScreenShot2021-01-18at10_45_16AM.thumb.png.3ba178155009815ca39d14abf2509ee6.png

     

    Overriding classes can be achieved in the same way in a viewport - select all of the classes, and set their attributes to some version of black and white and then just override the dimension class with red. 

     

    Most of us have MANY classes, so the layer solution is probably easier.  However, if you don't want your dimensions on a separate layer, then that is likely your preferred option.

     

     

    • Like 2
  2. It works fine for me in v.2021.  I even finally managed to get all of my pallets to dock on the left side of the drawing window.

    The solution for me was to dock the pallets one at a time.  I found that if multiple pallets were already linked up they were less likely to dock together.

     

    Once I had the first pallet in the correct position, I was able to add pallets to it (including the attribute pallet).

    • Like 1
  3. On 12/5/2020 at 6:32 AM, Christian Fekete said:

    @Taproot do you create a text file and then a .sta file uploaded in VW or is there a prefered process ?

    great post, thanks for starting this

     

     

    Christian,

     

    I'm not sure exactly what you're asking.... as far as creating an office template, we did that in VW directly (no text file). 

    Our plan was to use the template as a beta for active projects and weave back in refinements to the master standard.

     

    Instead, what we've found is that the "template" is constantly being upgraded with minor tweaks and refinements.  We have a small office, so this is feasible... a larger office would likely not have this level of flexibility.

     

    • Like 2
  4. 13 hours ago, Kevin C said:

     

    How come that to generate the model in Open GL in the design layer, spin it around to my hearts content, zoom in and out, switch classes on and off, take screenshots etc. only takes seconds, but to generate the same level of detail in a sheet layer can take hours??

     

     

    I think Kevin's point is that the 3D working environment is working so fast now, that it's spoiled us for the slower 2D workflows.  Yes, it would be great to have them faster, but in general, we haven't found it to be that much of a nuisance.

     

    I'm not sure why it's taking 20 minutes to update a set of elevations or 'hours' for sheet layers.  I push our system pretty hard (complex models) and it usually only takes a few (≤5) minutes to update a set of elevations. Perhaps it's a multi-story building with a complex DTM and lots of polygons? 

     

    One thought is to review design changes in Open GL (design layer view) utilizing standard views with a clip cube.  Save each elevation as a standard view.  That can allow you to review design changes without needing to render the viewport each time.

     

     

    • Like 1
  5. 1 hour ago, P Retondo said:

    Or is this just a "teaser," and a more capable version is available with "InteriorCAD?

     

    I think that is the situation.

     

    A friend of mine uses InteriorCAD for his cabinet shop and can do pretty much anything with it, but it's a rather expensive add-on.

    This lite version is limited, but still has its uses.

     

    • Like 1
  6. 10 minutes ago, MullinRJ said:

    Yes,

     

    BRB,

    Raymond

     

    Excellent.

     

    I assume that I would need to modify this portion of the script to also limit the selection of objects based upon it's font.

     

    On 1/6/2012 at 12:17 PM, Pat Stanford said:

    Begin if GetType(Hd)= 10 then begin SetTextFont(Hd, 0,len(gettext(Hd)),GetFontID(Font)); end end;

     

    I see that Type 10 = Text Objects, but I don't know how to further limit the selection via font.

    Could you assist me in that regard?

     

  7. @MullinRJ @Pat Stanford 

     

    Is it possible to modify this script to replace a single font - rather than every font in the drawing?

    i.e. if the existing Font = "Arial" then replace it with "xxx" ?

     

    Our office formerly used a font that no longer functions properly. It was everywhere, inside symbols, etc.

    Rather than trying to replace every object one by one, we opted to re-map the font to a new one.  (This was before Text Styles)

     

    This basically solved our problem.  However, exported files revert back to the offending font, so the display goes wonky. It would be better to replace all instances of the corrupt font and scripting looks like the best way to do it.

     

  8. 17 hours ago, Pat Stanford said:

    Unlikely, but have you checked Font Mapping for the file?

     

    Pat you nailed it... I did a deep dive and determined that was the problem.  Inadvertently, a font map had changed - so a simple fix for us and it's great to know that the 2021v. wasn't the issue.

    • Like 2
  9. @Art V Avenir came installed in my Mac system, so in terms of loaded versus installed I would go with the latter.

     

    Here's a snipit from FontBook (apple's built in font-manager).

    The font is listed as both Open Type and True Type.

     

    1229125910_ScreenShot2020-09-26at2_30_59PM.thumb.png.2da416ee593469e1ffe4ad1139fe4af3.png

     

    Here's a few screen shots of just one instance in the file.

    The first screen shot is from our file in v.2020, the second is from the file loaded in v.2021. (sorry different zoom levels)

    The heading font has changed ... this happens everywhere in the file.

     

    330367936_ScreenShot2020-09-26at2_28_38PM.thumb.png.9edb45d9393aaa9bfcfc39f67bb80377.png

    1614289177_ScreenShot2020-09-26at2_28_23PM.thumb.png.0a76f704a94ae476339560d198e9f5b7.png

     

    I can't imagine that it's a system issue - as the font still performs correctly in v.2020 (we have both releases running side by side).  It definitely has to do with the translation to the v.2021 file. I'll send tech support the two files and see if they can determine where the problem lies.

     

     

     

  10. We moved a sample project into v2021.

    I thought the transition was very smooth - this go around.

     

    I'm still a little amused that every year we need to update all of last years files to the new file format, thereby requiring us to 'batch convert' all of our libraries and pre-existing files.

    It would be nice if on the roadmap, the file type could stabilize so that the same format could be used between different releases of the software.

     

    OK - back to the topic - FONTS

     

    We use 'Avenir Next Regular'  as our standard font. 

    I favor a hierarchical look, so headings, titles etc. are in the 'Demi-Bold' version of that font.

     

    In translating the file from v2020 to v2021, all instances of Demi-Bold were wiped out.

    What a nuisance!!  Keynotes, Worksheets, General Notes, Drawing Markers, Text Styles ... you name it.

     

    It took A LONG time to restore everything within that file, and It looks like I'll need to do this manually to my Default Template as well.

    But ... now I worry that any file I convert to the new format is going to lose this aspect of the text formatting and so ... a disincentive to upgrading.

     

    If you use specialty fonts, check them carefully when converting.

     

    • Like 1
  11. I've taken to making my own colored icons as well. 

    Here's how:

     

    On a mac: Select the VW app > Get Info > Select the tiny icon in the top left corner of the "Get Info" window > Copy

    Open Preview: Select "New from Clipboard" > Export as a PNG with the Alpha channel checked

    Open in a photo editor and change the colors  > Save as a PNG

    Open the PNG - copy the image > Open the VW App "Get Info" and paste the image into the same top icon location

     

    Or just borrow the one posted above...

     

    • Like 1
  12. 6 hours ago, PLENZEN said:

    With the CSI Masterspec Division approach, I like the grouping. How do you handle phases? Existing, demo, new?

     

     

    We have the Existing, Demo, etc. classed within Div. 02 - which coincides with the "Existing Conditions" section of CSI.

     

    @Boh 's tips are great. 

     

    One more that I would add is to set up a custom magic wand selection (add your own parameters as makes sense).

    Then when you add a bunch of say Room Names and realize that they are in the NOTES class instead of the ROOM NAME class, you can just grab them all and move them over.

    • Like 1
  13. @Boh We have a similar setup - using keynotes per sheet rather than globally.  I was pleasantly surprised to try out the worksheet idea listing callouts.  It is pretty handy to have the entire list in one location for proofing.  I sorted the list by Keynote Legend, so that I was able to keep all of the notes organized in groups.

     

    I use the Notes Manager for General Note blocks, but typically just create keynotes on the fly to describe general callouts.  In my quest to try and develop more consistent standards, I've been thinking about migrating my callouts to the Notes Manager as well.  But, I have so many custom situations that need to be identified that I suspect that would be more trouble than it's worth.  For a larger office - it would make more sense.

     

    I've had some challenges with the Notes Manager 2020 - namely that my notes database has decoupled from most of my past files.  Tip - don't rename your database...  Or if you do, you'll have to go through the "reconcile notes" process listed elsewhere on this board. 

     

    For now, I think I'll let this one be and see what v.2021 has in store for us.

  14. Yes, you can do that. 

     

    I often modify my schedule worksheets to include complimentary information - for instance, adding skylights to the window schedule.

     

    My recommendation would be to copy your existing database row and paste it into the line beneath the existing one.

     

    The database row reports all of the records that meet it's criteria.  So, for the second (new) database row, change the criteria to that which will limit it to the doors that you want to feature.  That could be via the manufacturer info, or the ID label range or ....

     

    To do this, right click (or control click on mac) on the row # and then select "edit criteria".  See graphic.

     

    If it's just a few doors and a one of a kind situation, you can also just manually add the text to the rows following the database, but I sense that you're looking for a live-linked method.

     

    Good luck.

     

    1712412027_ScreenShot2020-08-31at8_22_24PM.thumb.png.04ca30d15939547e9c029f0df7552efc.png

     

  15. Similar to Boh's approach - instead of a design layer viewport of the DTM, you can also just create a "snapshot" of the DTM which will create a copy that you can move, rotate, etc to put in correct relation to your building.  You can access that setting via the OIP when the DTM is selected. The advantage is that you can adjust the display settings of the snapshot, so you have more control over the result.

     

    The next question that you're probably going to ask is how do you move the DTM to the correct height - given that the building is likely referenced to a Z-height of 0 and the DTM is referenced to something else i.e. 314.25 feet.  The snapshot works well for this situation as well - allowing you to move it in 3D space to the correct registration while also retaining the correct contour numerical display.

     

    This is from memory, so if you have trouble implementing the above and want to use this approach, let us know and I can clarify better how it's done.

    • Like 3
  16. If you click on a keynote marker, it should tell you which legend it is associated with. 

    "Default Legend will typically place the legend on the same sheet / layer.  But if you have other legends in the file, it may associate with one on a different sheet / layer instead.

    I usually place one marker and then option drag it to make copies.  Once you change the text of the copies, it will register as a new #, but all copies will correctly associate with the legend of choice.

     

     

    1201740725_ScreenShot2020-08-06at3_04_43PM.thumb.png.fbf76219425737e73961e980dcdbbb65.png

  17. I can confirm this behavior as well.  It's a bug relative to the "Clerestory" setting.

    In my file, the corner opens up at 4'-6" in height for the window with the Clerestory setting engaged.

    The left window is normal, the right has Clerestory checked. 

     

    455513907_ScreenShot2020-08-06at9_12_39AM.thumb.png.f30a33b9927a50c720df65376cc80d8c.png

     

     

     

    CORNER WINDOW PLAN VIEW BUG

    I found this thread to report a different but related problem.

    All of my corner window plan views are rendering incorrectly. 

     

    The sash / glazing line in 2d extends well past the jamb on the side of the window opposite the corner.

    The following image shows regular corner windows.

     

    1500137381_ScreenShot2020-08-06at9_07_15AM.thumb.png.6addbe3141a1f1f6d57d7bc6a6d425fc.png

     

    This image shows a plan view with clerestory engaged:

     

    1718625621_ScreenShot2020-08-06at9_18_43AM.thumb.png.b1921b7aab177fef678aa5e0f3905a28.png

     

    • Like 1
×
×
  • Create New...