Jump to content

Taproot

Member
  • Content Count

    471
  • Joined

  • Last visited

Community Reputation

209 Spectacular

4 Followers

About Taproot

  • Rank
    Journeyman

Personal Information

  • Occupation
    Architect
  • Homepage
    www.taproot.us
  • Hobbies
    Kundalini Yoga, Photography, Outdoorsy Stuff...
  • Location
    United States

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. @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. 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. 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.
  3. 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.
  4. 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...
  5. 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.
  6. @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.
  7. @Boh That's an interesting approach. I'm investigating using this for managing our keynotes. I'm curious if you also use the worksheets as a defacto library for storing callout text standards for all of your files or if you still use the Notes Manager and then just edit within the worksheet?
  8. 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.
  9. 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.
  10. 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.
  11. 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. 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. This image shows a plan view with clerestory engaged:
  12. We're on the doorstep of August - which means that the 2021 version release is only about a month away. While many of us are just now getting used to v.2020, I still enjoy the anticipation of the coming release. Will the stair tool get an overhaul? Will WinDoor finally make it to the northern hemisphere? Will TwinMotion see some love ... Here's hoping the Teaser Tuesdays are still on the calendar. Yes?
  13. @MartinBlomberg If no colors are changing, then make sure that the fill in your attribute pallet is set to "solid" for the object (not "none"). @Boh I thought that OpenGL rendering was available for non-renderworks users. In which case, you would access the rendering mode via the Menu: View>Rendering>OpenGL ... after assigning a texture to the object.
  14. @zoomer Sorry to hear that ... but hey that's a pretty good run. I'm just amazed that the light source is still good after all of those hours. @line-weight We're using VW2020 Designer (latest service pack). Here's what the primary view pane looks like when it starts to go buggy. Part of the image displays at a different scale. In this example, I had just one other viewpane open.
  15. @jmanganelli Yes, I'm inclined to spend more on the perfect screen up front. My 30" cinema display cost A LOT, but it's been going strong for 14 years and has been a great experience, so I'm inclined to go with high quality and less frequent turnover. The 43-44" size is interesting thought. I hadn't considered it, but will look into it further. Beyond that, I think I would be turning my head too much and would be tempted to sit further away (which would defeat the purpose). I appreciate the feedback.

 

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