Jeremy Best

Member
  • Content count

    40
  • Joined

  • Last visited

Community Reputation

1 Neutral

1 Follower

About Jeremy Best

  • Rank
    Greenhorn

Personal Information

  • Occupation
    Product Designer
  • Hobbies
    Counting. I like to count. Von, dtoo, thlee, vhorl,..
  • Location
    Auckland, New Zealand

Recent Profile Visitors

320 profile views
  1. Hey @Marissa Farrell, I'm trying to repurpose Alan's script but am experiencing behavioural issues that might relate to the 'jumps around' phenomenon, despite now using 2017 SP4. I'm using Alan's script to enable multiple straight extrusions that all use the one symbol as the profile, so that when I alter (not exchange) the symbol, all extrusions will receive the altered profile. The symptoms I'm getting are: The position of the extrusion path 'Control Geometry' doesn't reflect the placement/position of the resultant Marionette part either. If I move the resultant Marionette part - no matter whether in an 3D view or a 2D/elevation view and no matter whether with the mouse or using 2D Align or 3D Align commands - it jumps to a completely unrelated location. See attached video for this symptom. EDIT: The Marionette part also changes location when I change the Symbol profile, but it doesn't move again if I change it a second time. The 'control geometry' however stays where the Marionette part was before I change the profile the first time. Are you able to confirm if the 'jumpy' geometry/Nurbs received any amendments since the aforementioned post? Or what could or will be done to overcome this? (I just can't position the object). Shifty_Marionette_Object.mov
  2. @Chad Hamilton HAarchs has expressed the importance of this matter also, including specific needs and considerations here:
  3. I'm trying to help a user with these issues. I'm making this post to gather more information to either inform my bug report or provide an informed solution to the user. Primarily, I would like to establish if anyone else has experienced the following symptoms/issues when using Callout Notes and Keynote Legends, with a Notes Database. Issue 1: Notes previously in the database no longer being there. (As evidenced by inspecting a copy of the backed database file). Issue 2: Keynotes and their respective listing in a Keynote Legend disappearing. From what I understand, these issues occurred under the following conditions: New Vectorworks document created from template. Previous Notes Database file duplicated for use with this project only. (Database is stored on a local network server, but the Vectorworks file is on the computer being used). Callout Tool Preferences used to select the duplicated database file. Notes placed as Keynotes, on Sheet Layers in Viewport annotations. (Notes Manager 'Prefs...' set to save changes when dialogue is closed, 'OK') Keynote Legend/s created on Sheet Layers (not in Viewport annotations). File saved, then closed. File later reopened. Some Keynotes and the respective items in the Keynotes Legend are missing, but other instances of these Keynotes are still present on one other Sheet Layer and listed in the Keynote Legend on that Sheet Layer. The Keynotes that disappeared were not present in the original database before it was duplicated for use with this project. They were created during this project. When using 'Reconcile Notes' the following error comes up for some notes: "Cannot find the selected note in the Database". - All the notes in this instance start with the same prefix / naming convention, 'GF-PF' and are found in varying quantities in Keynote Legends on several Sheet Layers. I see potential for this discussion to start a torrent of contribution, so please note I am not the user so getting more info from them or testing every remedy offered might be limited. The conditions supplied above are intended to inform what variables might be involved for others with these issues to consider, and to help inform the scope of these issues. The most important factor for me is to establish if anyone else has experienced the following symptoms/issues. Thanks! Jeremy
  4. Hi @Josh NZ, By my reckoning this is a bug. IF this is still occurring after updating to SP4, please either submit this as a bug or send me the file exhibiting this problem (saved with the Keynote Legend in-view) and if I can recreate the symptoms I'll submit it as a bug. Or You could post this on the Troubleshooting forum... (where it might get more attention) or Use the Bug Submit page - to submit directly to Vectorworks software engineers.
  5. Hi @JimW! I am adding my voice to the chorus of people calling for the functionality AND workflow of the Callout Notes and Keynote Legend and Database facilities to be completely reimagined and redesigned.
  6. I should add to my above post, that in the 2017 SP3 update - released after this discussion was started - the release notes mentions several (non-specific) fixes to Keynotes.
  7. Hi @iBagwan, can you please define the setting you change to 'default'? The only setting I can identify offering 'default' is under the 'Keynote Display' dropdown, but changing this will alter what data is shown, and is surely not a desirable outcome. Are you suggesting that after changing it to 'Numbers (1, 2, 3, ...) [default]' the user can then change it back again to the preferred option without the notes loosing their connection to the database? EDIT: Never mind. I confused the Callout object with the Keynote Legend object.
  8. Hi @Mattheng. In my experience, when set up correctly and running on adequate hardware Vectorworks 2017 performs well. (Following best-practice always helps too). If you're experiencing performance issues with Vectorworks 2017 please know that it is not typical and that if you're running it on hardware appropriate to the increased demands of 2017 and the complexity of your documents, then you can expect to achieve normal performance as well. The non-specific symptoms you've described leave many possible causes, but here are some common ones: Vectorworks 2017 requires more hardware performance than 2016 because it has enhanced capabilities. Make sure you Mac meets the Vectorworks 2017 System Requirements. One aspect in particular is the Navigation Graphics: Go > Vectorworks preferences > Display > Navigation Graphics - and set this to 'Good Performance and Compatibility' or 'Best Compatibility.' This will improve responsiveness and stability. Check for stray objects in your Design Layers. If objects or the 'User Origin' are ~8 km / ~5 miles or more away from the "Internal Origin" this will weigh heavily on computation and can cause a broad range of seemingly unrelated symptoms. Centre your drawing over the Internal Origin and pull in your User Origin unless it has to be where it is for georeferencing. See: Vectorworks Help for related info. Legacy stuff: Symbols, Plug-in objects or other resources. Nothing lasts forever, this includes the compatibility/suitability/usability of resources created years ago in older versions of Vectorworks. While targeted testing demonstrates that Vectorworks is reliably backwards-compatible, the longer resources are around the more opportunity they have to become defunct and this it seems is the most likely explanation for corrupt resources. - Identifying culprits can take a bit of work, but fixing them is relatively easy. Just 'Edit' them to get their guts (images/2D/3D parts) and reassemble them as a new resource. If the above isn't applicable or doesn't resolve performance to your satisfaction, please contact your local Vectorworks agent to get the Tech Support needed to get your Vectorworks running normally.
  9. @FBernardoI provide Technical Support for Vectorworks customers in New Zealand. Before I say this, to be fair I must concede that I don't have current knowledge of the proportions of Mac vs Windows users in our customer-base, but a few years ago it was regularly proclaimed in our office that it was 50/50. Since September 2016 I have had: 49 Mac users submit a 'problem' 86 Windows users submit a 'problem' I would like to add: Many of the Windows users that have problems require a fix or intervention done to an aspect of their operating system to enable Vectorworks to function normally. Most of these would be updating graphics card drivers, sometimes reinstalling them. Whereas this type of thing is never required for Mac users because all that finicky time-consuming tech stuff is handled by Apple for you in their updates. Windows does have Automatic updates, but is obviously unreliable. I'm struggling to recall a job across the above period that required any intervention with a Mac operating system. IBM released a study showing that Apple computers cost less over their lifetime because they require less I.T. intervention or repairs: "just 5 percent of IBM’s Mac users needed to call the help desk; In contrast, an astonishing 40 percent of PC staff request tech support help." I've watched many YouTube channels where the computer geek presenter/s concede that Apple is largely equally priced now, if not better when you consider the free productivity software etc they come with. See: http://www.pcgamer.com/apples-new-imac-pro-costs-5000-but-is-it-overpriced/ As for the proportion of actual bugs in the Mac vs Windows implementation of the software, I'm not sure about that, but it might be helpful to consider that while there are bugs that affect both platforms, there are those that affect one and not the other, but these proportions could vary between updates let alone between versions. As a qualified Product Designer I appreciate the importance of producing well-researched design solutions that work and are intuitive for the greatest number of people at once. - That's what Apple does. I don't know if they still do, but I heard that their operating system designers used to be guided by the mantra "three clicks to anywhere" when navigating your computer. It still works for everything I just tested.
  10. I've heard a few YouTube tech geeks say that Apple is fairly competitive nowadays, and on top of the actual cost for the hardware you get a load of beautiful and functional software and of course, one year of awesome (by my experience) customer service - which I continue to get years after my AppleCare expired. This article actually neatly quantifies why the new iMac Pro is a good deal: http://www.pcgamer.com/apples-new-imac-pro-costs-5000-but-is-it-overpriced/
  11. An interesting result Kevin. Perhaps your circle sizes are too large to witness skewing even at 25DPI. If I'm wrong, that's a good outcome for users but let's rule this out: Look at my PDF again. The circles in the smallest scale Viewports (1:1200) demonstrate perfect vector circles being skewed in PDF @72DPI that improve when the DPI is raised. The video I posted communicates it best.
  12. I think the takeaway from this is simply to keep your DPI as high as you need it to be to achieve the level of detail needed. I'm not sure changing the way Vectorworks communicates/formats graphics will make any difference because the constraint here is the 'invisible grid' that the PDF format enforces. Because even vector curves get affected (skewed) when the DPI is too low, the solution is to just keep DPI high enough. 300 DPI or higher when needed.
  13. @Kevin McAllister Perhaps your page size is large, in which case you might just need to zoom in further to see the effect. Certainly! "Here's one I prepared earlier." ;-D I've provided: The source Vectorworks file A Published PDF (A3 pages) A video demo of the results I've verified this results show up using Adobe Reader DC as well. Testing Publish DPI settings.vwx Demonstrating Publish DPI settings.pdf PDF_Publish_and_PDF_Export_DPI_settings.mov
  14. I'm supporting a user who also has this issue and would like to get some insight into how the investigation is going (to avoid a double-up of effort). @Markus Barrera-Kolb what have you heard?
  15. @Kevin McAllisterWhen it comes to vector graphics / geometry the Sheet Layer DPI is irrelevant. That DPI only affects renderings or images. However, the Publish/Export 'Resolution' DPI setting will have the final say on both. NOTE: I haven't tested to determine whether having the Publish/Export DPI setting higher than the Sheet Layer DPI would cause it to regenerate Viewport renderings to match the higher figure, but I doubt it would. EDIT: In fact because users might want low DPI images/renderings (perhaps to keep the PDF file size low) but retain high-accuracy vectors, I'm quite sure having a Publish/Export DPI setting higher than the Sheet Layer would not cause it to reprocess Viewports to match.