Jump to content

Jeremy Best

  • Content Count

  • Joined

  • Last visited

Community Reputation

101 Spectacular


About Jeremy Best

  • Rank

Personal Information

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

Contact Info

  • Skype

Recent Profile Visitors

1,488 profile views
  1. Hi @jtempleton, please forgive the presumptuousness of my reply, but it's intended to help you in the long run: Making your question as succinct - yet specific - as possible It will increase the likelihood of users reading and understanding your post. Use as many Vectorworks terms as you can. Post a file for review Posting your file or a redacted copy of it, or a test file will make it easier for folks to diagnose causes. Go through the Vectorworks University as soon as you can (if you haven't already done so) The structured content will build a crucial foundation of knowledge and successive chapters will provide increasingly technical and industry-specific tools and information. Revisit this every year as you'll forget things you haven't used but may now be applicable to your current workflows. The Vectorworks Help is first place you should go when you're seeking to understand the relationship between results and settings. From Vectorworks, go: Help > 'What's This' > then select the tool, menu item or palette in question. I would have thought the result you're getting is a function of one of your site modifiers, or perhaps some of the site model data, having an elevation of zero. The Site Modifier tool has settings that dictate at what elevation they will be:
  2. Apple has very long-term plans directed by a reasonable objective to make ever-better products. They took some big steps toward their next milestone with changes introduced in Mojave and Catalina which understandably came with significant implications for everyone working in the current paradigm. Change is often uncomfortable, but it's necessary. I think most would agree that Apple's last transition (PowerPC to Intel) was necessary and eventually produced better results than struggling on with Motorola's manufacturing issues. Recent operating system changes have obviously been part of their roadmap to move to their own silicon, so necessary. Context is a powerful thing. My wife will tell you I'm no optimist, but because I've accepted that it's impractical for software to be made bug-free I'm pragmatic about computer problems. I report issues, then work around them. If it's practical to do so bugs will get fixed, but there'll always be more so it pays to accept certain realities. Like @Don Seidel I am super excited to see what performance gains Apple's SoC will make possible for Vectorworks, along with the other changes that will make my computing life easier (overall) and more fun.
  3. I agree, that image props are often not as aesthetic as desired, but they are a trade-off between realism and performance. If you had a 3D model of each plant the load on your computer would become unworkable pretty quickly - although Vectorworks 2020 has introduced much more efficient ways of handling the geometry it displays so maybe they are now more viable to display - the geometrical data (file size and memory consumption) would still be very large. There are 3D plant resources available. Add them to your plant definitions and see how whether they work for you or not. Use the VBvisual Plant Tool in the Visualisation palette. This is because the Image Prop is made up of two identical perpendicular images, and in the screenshot the one of the image prop images is aligned with the light source and the other is perpendicular and creating a shadow from its base up (as it should be). One factor in this result is whether the image prop is set to, "Auto Rotate" towards the viewer. See 'Creating image prop objects' for a full explanation.
  4. I've looked at all the variables I though may be a factor in this behaviour but none are described as nor produce the behaviour you're describing. I suspect a corruption of either: One or more objects that have this behaviour, or The file itself, or A Vectorworks system file. Account for these possibilities by: Post your file (or a test one with suspect objects within) here for someone else to test. Test for this phenomenon in ideal circumstances: Restart your computer -> re-check. Acid test: Go: File > New… > Create blank document (with only new symbols) -> re-check. Acid test: Go: File > New… > Create blank document (introducing your suspect symbols) -> re-check.
  5. Thanks @herbieherb. I wasn't intending to start anything, only provide some perspective and hopefully some soft of relief for those affected by Apple's way of doing things. Hence my final (encouraging) remark:
  6. Check out one of the most confounding, infuriating and nonsensical conditions that keeps me a happy and sane Mac user despite the occasional backwards compatibility issues in macOS. Windows 'got me' today right when I was in a hurry to get something done– No one and nothing is perfect, so work as best you can with what you've got!
  7. I did notice some weirdness when opening your file that my installation of Vectorworks corrected. Even though I didn't save my changes the next time I opened your file the anomalies did not occur. Deleting then downloading your file again presented the anomalies again. - This suggests there is something wrong with your file or one or more objects in it. To rule out your file's apparent issue/s, I've used my own test file to confirm what I asserted in my last comment.
  8. Hi @nwfonseca, I've tested your file. The short answer is to just use 'Hidden Line' rendering. That gets you the result you're after without the lines-between-the-corners. Also, using your file I confirmed there is no difference between Shaded Polygon mode in the Design Layer and a Sheet Layer Viewport. Those lines appear in both and I believe they are a function of displaying 'polygons' - which are actually there and so will be displayed - as opposed to OpenGL or Hidden Line or Dashed Hidden Line because they are used to communicate particular information about form and not what geometry the object is made of / how the object is constructed.
  9. Hi @JLitterio, given the nature of the issue and that it returns some time after a fresh install, I'd consider the following possible factors: When you install Vectorworks ensure: All aftermarket antivirus is turned off Close all other programs during installation Close all other software, restart Vectorworks then see if the issue persists. (A software conflict may be responsible). Disable any aftermarket antivirus you have installed as it may be blocking this action with these files. If none of the above help; It is possible your operating system is compromised in some way, warranting it's own reinstallation. - I say this because: I can imagine one of the operating system's routines (that periodically run in the background) making some change that affects this capability. The issue is particular to your computer. There may be some value in identifying whether this behaviour started after a Windows update or new software or anything else that appears to correlate, but in my experience this is an unreliable way to diagnose.
  10. That's good to hear, but what about 'stray' objects. Even a single line, far enough away, can cause the problems associated with 'far out objects.' Given that I'm not getting any users reporting this, it remains more likely caused by something particular to your computer, installation or file/s. In these circumstances if you rule out 'stray' and far out objects, the following are more likely causes/solutions. In order of ease: Corrupt Workspace: Try one of the default workspaces. If your custom one uses the same name as a default, you'll need to remove the custom one from your User Folder. Corrupt Vectorworks System Files: Perform Resetting Vectorworks Preferences. Corrupt object/s. (Have to use halving-method to identify. Delete half objects by Class or Design Layer, then test. Repeat until symptoms cease. Narrow down causal object/s) Unfortunately as this is occurring on other computers as well, it makes it more likely to be (primarily far out objects, but if you've ruled that out then) due to one or more corrupt objects. Maybe even a resource, which would probably be harder to determine. Maybe you can sense a pattern considering which files have this issue and the ones that don't. I recently encountered a user's file where a corrupt texture was making walls render as solid black if they were repositioned. In order of likelihood, before potentially faffing time away trying to isolate potentially corrupt objects or resources, given that it takes comparatively little time if I were in your shoes, before Resetting or searching for corrupt objects, I would first try: Performing a 'clean' install of my graphics card driver. Just in case. And failing that, - for the same reason - Try using the 'Repair' command in the Vectorworks Updater app. (In 'Advanced Options'). And failing that, - for the same reason - Uninstall then reinstall Vectorworks using the latest installer. (Total of 30 mins on a good computer, once the installer is downloaded).
  11. You're welcome @SLFY. Glad to have helped. The Resetting Vectorworks Preferences page does include at the top, "To maintain a copy of your preferences, follow THESE INSTRUCTIONS" but I do concede, no mention of broader customisations. I'll request it be refined.
  12. Hi @JMR, I see I'm late to the party but you've indicated this is a long-persisting issue for you, so; May I suggest you rule out 'far out objects,' as they cause an extremely broad range of symptoms and seeing as the intensity of the symptoms seems to correlate with the level of computational pressure generated (using 'Best Performance' vs 'Good Performance and Compatibility'), and in light of the other factors you've ruled out, then I'd say it's worth checking. I've encountered users suffering this condition so often I've written a dedicated script to identify and remedy the problem. See here:
  13. All links to the respective driver download pages aren't working for me. They just terminate with "https://forum.vectorworks.net/index.php?lang=en-us " I suspect it is a broader issue with this page or the website (I've tried alternate browser, same result). The solution is to copy the address text (not the embedded link) and paste it into your address bar.
  14. Hey @Sittingducks, care to post your file for examination? If so, please include definitive steps you used to produce the exported image. Eg: In Design Layer 'Cabinet,' in perspective view, render mode, 'OpenGL,' Go: File > Export > Image File…
  15. Hi @RichPiano, when your rulers start displaying alphanumeric characters that often signifies your model is too far away from the Internal Origin (distinct from the User Origin), but this is not a definitive indicator because the rulers represent distance from the User Origin, not the Internal Origin. In my role of supporting Vectorworks I've learnt that 'far out objects' can cause a diverse range of problems/symptoms. I've written and optimised a script with steps to diagnose and correct 'far out objects.' See here:


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