Jump to content

Jeremy Best

Member
  • Content Count

    162
  • Joined

  • Last visited

Community Reputation

44 Great

2 Followers

About Jeremy Best

  • Rank
    Journeyman

Personal Information

  • Occupation
    Customer Support
  • Homepage
    megabits.co.nz
  • Hobbies
    Mountain biking. Designing - both processes, tools and products.
  • Location
    New Zealand

Contact Info

  • Skype
    mrjmbest

Recent Profile Visitors

858 profile views
  1. Jeremy Best

    Error loading Vision Library

    Hi @DomC, Did you mean to post this here?
  2. Jeremy Best

    Error loading Vision Library

    Hello everyone! Tech Support USA have provided me with a fix for this issue that worked for me and a user I worked with on this. 1. Quit Vectorworks 2019 2. Go to: Macintosh HD/Library/Application Support/Vectorworks 2019 3. Select and copy these three folders: ⁃ Gobos ⁃ Library ⁃ textures 4. Go to: Macintosh HD/Applications/Vectorworks 2019/Vision and paste them in. 5. Reopen Vectorworks.
  3. Jeremy Best

    Mojave thinks 2019 is 32 bit

    I'm curious to know; What procedure did you use to do this? macOS Recovery > Restore From Time Machine Backup (Alternative) macOS Recovery (Shift-Option-⌘-R) > 'Install the macOS that came with your Mac, or the closest version still available' > then (IF you chose to erase your disk) use Time Machine Backup to reinstate your login/account data.
  4. Jeremy Best

    Polygons with Hatches are un-selectable

    Thanks @Andy Broomell, I've added this info to the bug report.
  5. Yes this is interesting. Can you expand on this a bit, please? Do you mean that beach balling occurs whenever you connect a USB-C peripheral while other USB-C ports already have devices connected to them? So connecting the same peripheral does not cause beach balling if no other USB-C devices are already plugged in? What are the devices that do cause beach balling when/after they are plugged in?
  6. Jeremy Best

    Polygons with Hatches are un-selectable

    Bug report submitted: VB-158101
  7. Jeremy Best

    Polygons with Hatches are un-selectable

    Hi @Patrick West, I work for the New Zealand distributor of Vectorworks providing Tech Support for our users. While investigating a different issue involving Hatches in a users's file, I experienced this same situation. After verifying it was only affected certain Classes my expectation was that this behaviour was due to a random corruption, but because of your report (and despite my inability to reproduce the problem from scratch) I will submit this to engineering. I expect Engineering will face a similar challenge recreating the conditions that cause this problem. So if you are aware of how to recreate this issue it would be extremely helpful. If you have a file you're happy to contribute that would be great (message me privately) or post your proven sequent/conditions here. Thanks!
  8. Jeremy Best

    Object info palette flashing / blinking

    That's great news Laura. If/When you make the move to Vectorworks 2019 it should be better still.
  9. Jeremy Best

    Object info palette flashing / blinking

    For the benefit of anyone searching this forum for issues encountered while using Vectorworks on a Microsoft Surface: This issue is likely due to Vectorworks being run on a tablet instead of an industrial grade computer, which is warranted to run industrial grade software... Because the Object Info Palette is visually built on-screen every time its content must change, I expect this behaviour occurs on all Windows computers but it just occurs fast enough for this to not be so noticeable. Having said that, the efficiency of the Object Info Palette has been reengineered and drastically improved in the Windows version of Vectorworks 2019.
  10. Jeremy Best

    macOS Mojave (10.14) Compatibility

    Hi @brentf and for the attention of anyone else who is experiencing beach-balling with Vectorworks 2019 on macOS Mojave. I provide Tech Support for customers of the New Zealand distributor, Megabits and have encountered one user with very similar symptoms. (Click something or place something on the drawing area causing beach balling for a long time). The solution in that case was the widely prescribed process Resetting Vectorworks Preferences. In an earlier attempt to help this user I experimented somewhat by only retiring their Vectorworks User Folder only and not the complete process above. I tried this because it had been migrated from the previous version which sometimes goes awry in some way that can result in one or more symptoms of differing variety, but as it turned out the full process is what's proven to be necessary. (Creating an additional Mac login/user account effectively creates this same result). There are a few different items within the Vectorworks User Folder (and hidden Vectorworks system files) that can become corrupt/problematic at random and are responsible for a variety of symptoms. The Resetting Vectorworks Preferences process is commonly prescribed because it quickly deals with all components at once that could be the cause. While there seems to be an apparent correlation with the adoption of macOS Mojave and Vectorworks 2019 take note that I have encountered these symptoms on prior operating systems and they have often been remedied using the Resetting Vectorworks Preferences process. I'm just pointing out correlation does not equal causation, so Mojave may not be the cause in this instance. But it might... 😜
  11. I note that the missing text/record items are different colours (which I thought denoted different line weights in DWG native software). Which makes me wonder if your Saved View just has the Classes of these items 'invisible,' while in your Sheet Layer Viewport those same classes might be visible. If these Classes are visible in both your Sheet Layer Viewports and the Saved View, then this might be a bug in which case I suggest you submit it to Vectorworks or run it by Tech Support for your region. At the moment I can't warrant the time to get my head around the layer scale results you're getting (but it sounds like it might be working as intended considering DXF/DWGs only support one scale at a time) so I suggest you run this one by Tech Support too.
  12. Exporting the content visible in a Saved View will always be smaller than a Sheet Layer Viewport showing the same view because (as per my earlier post) when you export a Sheet Layer with Viewports, it exports the Sheet Layer content but also exports - separately - all the content present in the Design Layers shown in the Viewport. Please see the explanation above for why this is the expected result.
  13. Jeremy Best

    Save on Dropbox, Publish in Cloud = FAIL

    As per these instructions, have you first done the steps to activate the Dropbox integration specifically?
  14. Jeremy Best

    Back Referencing

    Time to stoke this fire… I reckon good will still goes a long way because we are still [stuck] being human. To this end I assert that we can improve Vectorworks presence and regard in the world by supporting not just users of the software but those who must work with its output. i.e. Builders or construction managers or council workers etc who must work with plans produced in Vectorworks. Imagine what effort could be saved, what ease could be enabled and what good will could be conveyed if back referencing was made available for those at the end of the line who would benefit from well-designed documentation facilities in Vectorworks. Conversely, imagine what resentment might exist in the industry towards Vectorworks if it is the only software producing documentation without these benefits. (I've read all major competitors have this facility). I think the potential benefits of back-referencing to anyone producing or using architectural documentation are obvious. And even those in the USA who are used to the absence of this facility would surely be pleasantly surprised by the ease offered by back-referencing if implemented. After all, going beyond what is expected is what creates excellent user and customer experiences. I've been told 50% of an architect's time is spent on documentation. Surely any feature that can significantly assist with hastening documentation is a no-brainer worth implementing, let alone the ensuing benefits to all who use the documentation thereafter. (Yes, this is a repeat of my comment elsewhere as it should be more effective here).
  15. Time to stoke this fire… I reckon good will still goes a long way because we are still [stuck] being human. To this end I assert that we can improve Vectorworks presence and regard in the world by supporting not just users of the software but those who must work with its output. i.e. Builders or construction managers or council workers etc who must work with plans produced in Vectorworks. Imagine what effort could be saved, what ease could be enabled and what good will could be conveyed if back referencing was made available for those at the end of the line who would benefit from well-designed documentation facilities in Vectorworks. Conversely, imagine what resentment might exist in the industry towards Vectorworks if it is the only software producing documentation without these benefits. (I've read all major competitors have this facility). I think the potential benefits of back-referencing to anyone producing or using architectural documentation are obvious. And even those in the USA who are used to the absence of this facility would surely be pleasantly surprised by the ease offered by back-referencing if implemented. After all, going beyond what is expected is what creates excellent user and customer experiences. I've been told 50% of an architect's time is spent on documentation. Surely any feature that can significantly assist with hastening documentation is a no-brainer worth implementing, let alone the ensuing benefits to all who use the documentation thereafter.

 

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.

×