Jump to content

Jeremy Best

Member
  • Content Count

    90
  • Joined

  • Last visited

Community Reputation

10 Good

2 Followers

About Jeremy Best

  • Rank
    Apprentice

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

690 profile views
  1. Jeremy Best

    VW 2019 PDF Ref's Dissappear on conversion

    Hi @Samuel Derenboim, @assemblyarchitecture & @gmm18, I provide Tech Support for users in the New Zealand market and have had one report of this but I have not been able reproduce it nor has the user [been able to] find and supply the original PDF yet. Perhaps if you can provide me the necessary files to test and verify these issues I can help forward the bug submission, verification and resolution process. I've had one firm report multiple files with referenced PDFs not displaying in Vectorworks 2017, but not all files are affected. If you're experiencing issues with all PDFs, then: As not all users are experiencing this, then it's likely something particular to your circumstances is responsible. Some of the variables mentioned below might still be of use to you, but it might be warranted to try: Resetting Vectorworks Preferences, or Uninstall then Reinstall Vectorworks with antivirus temporarily disabled. If you're experiencing issues with some PDFs but not all, then: See if the problem ones are a different file version than the ones that do work. Please note these as-you-go. To determine PDF Version: On Mac: Open PDF in Preview and 'Get Info' On Win: Open in Adobe Acrobat Reader DC and go: File > Properties... Other variables to consider: Are the PDF files kept on a server? - Is the server functioning normally? Are Read/Write permissions/privileges blocking access for Vectorworks? Does the file or any parent folder (directory) have really long names or unusual characters in them? Is the reference file path: Relative to the position of the document, or Absolute (specifically defined). May I suggest you try to identify the offending condition using the following tests/processes: Perform an acid test: File > New > 'Create blank document' File > Import PDF > choose PDF and check 'Reference' if that's what was used before. Otherwise leave it unchecked to import it into your document. If the issue does not occur, then the issue is likely conditional of your original file. Try the following remedies with your file: Check for 'far out objects' and move/delete any you find. See the following article: If this isn't relevant or removing 'far out objects' doesn't work, then... Export your document to a prior Vectorworks version (File > Export > Vectorworks 20XX) then reopen it in the version you're experiencing this issue with. If the issue persists and the PDF is on a server: Put the PDF on your local hard drive and try the above acid test again. If the issues occurs again, then it's likely a Vectorworks bug, regardless of whether the PDF version is a factor, but it will be important to determine what versions (if any) are affected. Please let me know what you encounter and I'll see how I can progress this matter.
  2. Jeremy Best

    Page Based Symbols Not Scaling in Worksheets

    Hi @I will I, does this issue current persist for you? If so, what version and Service Pack are you using?
  3. Jeremy Best

    Update Service Pack

    When updating any software it must first be closed. It's kind of like changing a car wheel with a flat tyre; The car must be stationery and the wheel off the ground to swap it out. It sounds like you've already downloaded the SP1 updater (on Mac) in which case just: Quit Vectorworks Double-click the updater and follow your nose. Note that an updater is distinct from an installer. If you've downloaded the SP1 installer it's not intended to be run 'over the top' of an existing installation of Vectorworks. You should always access your updaters from within Vectorworks. For Mac users go to the Vectorworks menu > 'Check for Updates' then follow through as above.
  4. This is a PSA for all Vectorworks users experiencing reoccurrences of any of the following symptoms: Total corruption of one or more Vectorworks files (.vwx) - Meaning they can't even be opened. Total corruption of backup files Very slow saving files or autosaving [backup files] in Vectorworks Attempts to use Vectorworks during a slow save or autosave crashes Vectorworks (no crash reports got generated despite reporting set to 'verbose'). One user who was repeatedly experiencing all the above symptoms in both Vectorworks 2016 and Vectorworks 2018 reported to me a direct correlation with the presence of both the following programs on his PC running Windows 10: Seagate Dashboard - Software that comes with external drives for managing backups. Adobe Acrobat - An old/legacy version of. I think his was version 9 but I can't verify as it's already been deleted. He uninstalled both of the above programs at the same time after which all the above symptoms ceased and have not returned in the weeks since. He never used the Seagate Dashboard software but Windows Reliability History featured crash reports for it indicating it had been running. It also featured crashes of Acrobat as well, but given the nature of the Seagate Dashboard software I think it's the more likely cause of his saving/autosaving and file corruption issues. Specifically, the user reported: If [saving/autosaving] is taking a long time and he tries to carry on working then the whole thing freezes (the green progress bar is going really slowly, and if he tries to do anything in Vectorworks at this time it will likely crash). Success is achieved by not touching anything on the computer including other programs. It can take 30s to 1m to come right. I would like to stress that this situation and the apparent cause has not been reproduced and therefore has not been verified so I'm only posting this so anyone else experiencing these symptoms can draw upon this to inform their consideration of potential causes and solutions. i.e. Check any software that relates to the backing up or movement or management of files. Western Digital and Seagate external storage drives come with programs of this sort and - as was the case for this user - may periodically open themselves.
  5. Jeremy Best

    Vectorworks 2018 Hogs Application Memory

    You will find current status and subsequent updates in the dedicated article for this matter here:
  6. Jeremy Best

    Eyedropper Tool with Callouts

    Hi @Andy Broomell, Did you try submitting your above sentiment in the Wishlist Forum? I came across your post while researching and verifying a bug with the Eyedropper tool in VW2018 SP4 (23.0.4) & VW2019 SP0 (24.0.0): EDIT: Of bug description: Attributes copied from any object and applied to a Callout using the Eyedropper tool effectively get applied - according to the resultant settings shown in the Attributes palette - BUT none of those attributes render onscreen except for the Fill Style. The most recent version I've found to be free from this condition is VW2017 SP5 (22.0.5). VW2018 SP4 & VW2019 SP0 feature this bug/behaviour. NOTE: As one might expect based on @Andy Broomell's comment, turning ON the Eyedropper tools preference 'Plug-in Parameters' results in all attributes transferring, but then so does the text/content as the leader line position/geometry. Bug report submitted: VB-154901
  7. Hi @Lawrence Gaetano, and welcome! I think it's important to note that there are at least two similar but distinct symptoms that can be mis-associated. This thread was started by someone experiencing [only] Viewports going solid black once they'd rendered. If your entire drawing area is going black, or different again, your entire screen, then this is not the same issue. Clarifying your symptoms both here in this discussion and when working with Tech Support will make a difference because they are likely to have different causes and therefore different solutions. Is it your entire screen or drawing area going black temporarily, OR one or more Viewports ending up permanently solid black at the end of the rendering? If your Viewports end up black, then for the moment [as far as I know] restarting Vectorworks or failing that restarting your computer are the only reliable remedies for the moment. If your drawing area goes black while rendering is occurring then this might be in the hands of software engineers to address but the Resetting Vectorworks Preferences process might help. If it's your entire screen's going black then I'd broaden my view of potential causes. - Is your macOS up-to-date?
  8. Jeremy Best

    How to : Create a Workgroup Folder

    Now that the Resource Browser of Vectorworks 2016 has been enhanced and renamed as the Resource Manager for Vectorworks 2017 onward, I'd like to reinvigorate this thread and see what you think of the following... When using a tool's 'Resource Selector' - which will only show resources that can be used with the tool - to find content kept within a Workgroup folder, one must still navigate/expand the various sub-directories to where the source file is located. - This is a workflow/productivity bummer, especially when... You could instead have ONE Vectorworks resource file kept in the Workgroup 'Favourites' subfolder. Then it's the only location one must go regardless of the tool/resource-needed, and you don't have to drill down into sub-folders to access content. You can still have a unique Workgroup folder per project (if that's how you're using it) and have another Favourites file within (with a differentiated name of course). Does anyone see problems with my proposed setup above? Here's a depiction of why I think a single 'Favourite' file is better for productivity. It will also make updating a resource easier and faster too. Here it took 5 clicks to access the pertinent resource file stored in the mandatory location in a Workgroup folder. Because any Resource Selector will show only resources pertinent to the tool selected it makes using a single resource file MUCH more viable.
  9. Jeremy Best

    iMac advice for 2019

    I recall seeing a comment by @jimw that the system requirements for Vectorworks will remain stable for the next [few] versions so that should increase the longevity of existing hardware - depending on OS compatibility and support too though.
  10. Jeremy Best

    Titleblock - Issues / Revisions !?!

    The Vectorworks 2018 online Help Manual says the 'Apply Issues Data To:' dropdown is used to specify whether the issue is applied to "All Active Sheets" or a specified one. There is another factor though relating to an OIP setting of the titleblock/s on the Sheet Layers concerned. See: http://app-help.vectorworks.net/2018/eng/VW2018_Guide/Setup/Adding_and_Editing_Drawing_Issues.htm
  11. Jeremy Best

    Vectorworks keeps crashing

    Hi @Joe-SA, I have two users from seperate companies making this claim too, so I'd like to know what more you've learnt about it or how you might have resolved it. Has this issue persisted or happened again since? Did you notice what might have caused it or any correlation with other factors? If it has occurred again for you have you found a remedy that works for you? - Did saving the file with a different name resolve it like it did for@skeyshubber?
  12. Currently Line Types can only be applied to 2D line objects, and not 3D polygons. I've had a couple of users tell me that this is needed and subsequently found a few very old Forum posts requesting this capability too. I'm creating a new post/submission for this capability as I'm not sure if new comments in old threads would get equal promotion. Use Cases Include: Architects using the WinDoor tool can't display door and window ‘arrows’ (‘Hinge Markers’) with a dashed line because they are constructed using 3D Polygons. Interior Designers using InteriorCAD/InteriorXS can’t apply dashed lines to the doors and drawers of cabinets. Draughts-people of utility schematics need 3D Line Types so they can clearly differentiate between various pipes, cables, drains, ducting... etc. Old posts requesting this capability:
  13. Jeremy Best

    Rendering Viewport turns everything black

    Just a thought @SeanOSkea; Maybe you won't need to restart Vectorworks twice if you wait a bit longer before relaunching it. When I prescribe users to restart Vectorworks I usually stipulate that they wait at least 10 seconds before relaunching it. It's not a computer-science-degree validated strategy, but is derived from observation and experience. If you watch the memory consumption in Task Manager (Windows) or Activity Monitor (Mac) when quitting Vectorworks; You'll see the memory it consumed takes a few seconds to get released. I get uneasy when I see users click to re-launch Vectorworks as soon as the application window has disappeared because my history with computers suggests this is less-okay than being patient and allowing the computer to complete [certain types of] tasks before starting another. How I think this might relate to your need to restart Vectorworks twice; If you relaunch Vectorworks before it's finished releasing the memory it consumed some of it may remain intact, possibly retaining whatever issue you're seeking to clear out. I just did a simple test to which appears to validate at least half my reasoning: On a Windows 10 laptop with an HDD, using Vectorworks 2018 SP4 Restarted computer Launched Vectorworks (1:36 to load) Once fully loaded, quit Vectorworks Immediately launched Vectorworks again (0:37 to load) Once fully loaded, quit Vectorworks Waited 37 seconds (memory level for 32 seconds) Launched Vectorworks again (0:46 to load) These time differences seem to indicate less data is being loaded if Vectorworks is relaunched before it's finished releasing the memory it consumed. I'm keen to hear if this bears out. Comments, corroborative or alternative results anyone?
  14. Hi @abcdefgarin, as per your comment above, have you by chance had occasion to test whether using the Render Bitmap tool also fixes Viewports that have rendered black?
  15. When Landscape Area objects over a [large, high detail] site model are modified, they can easily take 15 minutes to recalculate, and often longer. When even something as simple as moving the Label causes the Landscape Area to recalculate this creates massive delays to workflow. Also, during testing (using a Xeon processor) the Task Manager indicated all the processing was all done by a single-core, when NINE other cores were available, exacerbating the wait times. WISHES: Please limit the Landscape Area objects to recalculate only when factors are altered that change the output values relevant to surface area etc. Please make the recalculating processes multi-core capable.

 

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.

×