Jump to content

Jeremy Best

  • Posts

  • Joined

  • Last visited


197 Spectacular


Personal Information

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

Contact Info

  • Skype

Recent Profile Visitors

2,973 profile views
  1. Hi @ryanesson, As this is not typical behaviour and as you have moved from a previous version to this one, the most likely cause are corrupt files in your Vectorworks User Folder. Run through the Resetting Vectorworks Preferences process. - Make sure you read the instructions carefully including how to "maintain a copy of your preferences" if you want to.
  2. Hi @gvictoria1, run through all the possibilities in my previous comment then report your findings here. If the advice you get here is not effective or fast enough for your needs, contact Tech Support for your region. If you're in the US, UK, Australia or Canada, then that's Vectorworks Inc. If elsewhere contact your local distributor.
  3. Hi @Scott Lebsack and thank your helpful reply. I'll pass your suggested workflow on to the user. I've realised I should have worded my final sentence/question differently. The user - and surely others - would like Looped Mains supported, so my final question should have been, 'Can this be added to the official Wishlist of desired functionalities?' Thanks! Jeremy
  4. Submitted on behalf of a user: A 'ring main' is a circular section of pipe. It enables water to flow in both directions from the entry point around the ring to any outlet pipes it feeds. The Pipe Tool does not support the creation of ring mains. Currently, if you finish a shape by clicking on the starting point with the Pipe Tool, the last section is made invisible. You cannot create a closed shape. This means that the total length of pipe shown in the OIP excludes this last section. This means that this closed shape… Becomes this open shape… Can closed shapes be enabled with the Pipe Tool? Cheers, Jeremy
  5. The following information will probably resolve this problem on any Dell or Alienware branded computers, or any others that employ NahimicOSD: In Summary: Add 'vectorworks2022.exe' to an 'exception list' in a file 'BlackApps.dat.' This will prevent NahimicOSD from being used with Vectorworks. Instructions: Copy this to your clipboard: C:\ProgramData\A-Volute Click on (⊞) / Open the Start Menu and type 'Notepad' into the search bar. Right-click on the Notepad app now showing in the Start Menu and choose, 'Run as administrator.' When asked by the User Account Control window if you want to allow Notepad to make changes to your device, choose 'Yes.' When Notepad opens, choose 'Open' from the File menu and paste C:\ProgramData\A-Volute into the address bar. From here things may look different depending on the make and model of your computer, but the idea is to look (or search) within the folders inside until you find the 'BlackApps.dat' file, then open it. The article linked by @Anthony Neary in his previous comment says it is here: C:\ProgramData\A-Volute\A-Volute.Nahimic\Modules\Scheduled\Configurator\BlackApps.dat Whereas on my computer, a Dell / Alienware m17 R4 laptop, it was in a similar location: C:\ProgramData\A-Volute\DellInc.AlienwareSoundCenter\Modules\ScheduledModules\Configurator\BlackApps.dat Other makes or models may have other software installed that includes the NahimicOSD frameworks which apparently relate to audio processing on certain computers. Knowing this may help you identify pertinent folders to look inside. When the file opens, make a new line, then add 'vectorworks2022.exe' (without the quote marks). Save and close the file. That's it.
  6. Thank you for that valuable insight @Anthony Neary. A modified version of the instructions you have linked to worked for me. I've been able to reinstall Alienware Command Center and Vectorworks 2022 now allows me to adjust docked palettes without crashing or the applicable warning coming up (added in Service Pack 3). I'll post verbose instructions below for those who require more specific guidance.
  7. You can produce photorealistic renders using these other options right in Vectorworks: Renderworks modes. It is comparatively very slow, but can produce some excellent effects and I suspect better results. Redshift. Much faster than Renderworks, probably slower than Twinmotion, but without the polish of Renderworks effects (as I recall).
  8. Yes, I watched those too. If a program or function used to work (on a specific computer) and then ceases to work, the first thing you question is, 'what has changed about the computer, operating system, software or the setup of these, since it was working?' - But as in your case, if it's never worked on a specific computer but does on other computers of the same model and operating system, then it's a matter of identifying disparities: Jonathan said he is using: Twinmotion 2021.4, on a "MacBook Pro with M1 Pro," on "macOS Monterey 12" As you're using Twinmotion 2022, see if you can access/download/install the same (previous) version Jonathan Reeves used in his demo. If that doesn't resolve it, check for other disparities.
  9. Hi Idris, Zoomer has made a good suggestion, to ensure your operating system is up-to-date. This will help rule out issues that can sometimes arise when operating system and software have some incongruity. To me, the nature of the problem suggests the following are likely causes: Accidentally Disabling snapping… by double-tapping the ` key (backquote key) perhaps whilst tapping the Esc key which is right above it. See 'Setting snapping parameters' in Vectorworks Help. Defunct Vectorworks preference file… The other probable cause (and seeing as you've checked the Snapping buttons are on, the most likely) is that one of Vectorworks preference files may contain a corruption. If you're satisfied the first possibility does not apply, try the following: (Specific for Mac users with Vectorworks 2022) Quit Vectorworks. Open Finder and do Shift-Command-G (or choose 'Go to Folder…' from the Go menu). Paste in '~/Library/Application Support/Vectorworks/2022/Settings' (without the single quote marks). Rename file 'Vectorworks Preferences.xml' to 'xVectorworks Preferences.xml' to hide it from Vectorworks. Reopen Vectorworks. If the issue is gone: Go through Vectorworks Preferences and set them up again. If the issue persists: Quit Vectorworks. Delete the newly created Vectorworks Preferences.xml file. Remove the 'x' from the original one. Seek further assistance.
  10. Hey @Tom Klaber, I've just been re-digesting your comments here and thought I'd restate what I think is likely going on in this case and what will likely help. First, an anecdote (not a prediction of what's going on for you): I had a case recently where a user was working on a massive development. It consisted mostly of efficiently drawn polylines and polygons - so no problem there - but they had applied Hatches and Line Types to almost every single object, and the complexity of those patterns induced a lot of processing that was somewhat noticeable when zooming/panning, but was more of a problem when rendering in Hidden Line and the like which incurred massive memory consumption - maxed out my 32 GB of memory. Regarding speed/performance: As you've not confirmed having Reset Vectorworks Preferences yet, this is definitely the most sensible next step. I've seen both corrupt Workspace files and Vectorworks Settings files and/or Windows Registry data cause Vectorworks to become very slow. The Resetting Vectorworks Preferences process will rule these likely causes out so I suggest you do this first. You can restore your customisations, notes database, libraries etc into the new User Folder after verifying if performance (not memory consumption) is improved when using this same file. Be sure to backup your Vectorworks User Folder and grab your Vectorworks serial number before you begin this process. Regarding memory consumption: Certain conditions in a file –alone– can cause performance issues and high memory consumption. If your drawing has a lot of geometry in it, or if Viewports –or the objects in them– are set to display Hatches or Line Types or anything that results in lots of geometry being displayed, you can expect: Vectorworks to use more memory during the Update process. Vectorworks to continue to use a lot of memory after the Update process as it keeps all the resultant geometry 'in mind,' and perhaps as part of the 'Undo' history. As others have shared you can regain some of the memory consumed as a result of the process (or the Undo history) by saving the file, closing the file (or perhaps Vectorworks), then reopening. I suggest you: Appreciate and adjust (if necessary) the quantity of geometry displayed by Hatches and Line Types in the Design Layer or in Sheet Layer Viewports: Check their complexity. Check if their scale results in mass geometry. Check if Viewports have any Class overrides that cause Hatches or Line Types to display high levels of geometry. You can appreciate how much geometry Viewports will produce, by exporting Sheet Layers as individual PDFs and examining the file size. PDFs don't support the efficiency of 'Symbols' and so every line is stored as an individual object (or as two individual points). There are other settings and conditions that can impact Vectorworks' responsiveness, like 'Detail' level of the 'Shaded' render mode or the new-ish '2D Components' feature of symbols, etc, etc. I recommend keeping Task Manager open on another display to observe and learn how certain operations and conditions impact your computer. (Ctrl-Shift-Esc, and select 'Always on top' in the Options menu). I hope that helps!
  11. Hi @inilegnam, I provide Tech Support for Vectorworks users in New Zealand. I've been thinking about this thread and others like it for a while. In my work I've encountered many performance issues like the one you've described. The vast majority I encounter are not due to bugs or inefficient code and I'm concerned issues are often being misattributed to the Vectorworks software. So I've reviewed some of my historical cases to test my beliefs and will humbly contribute the following: The symptoms you describe remind me of an issue that was due to a bug, long since fixed. As it was a software bug, I received reports from multiple users and the problem was reproducible in a default/fresh installation of Vectorworks. As I have not received any reports of the issue you're experiencing from our users, this suggests the issue is not a software bug. Your case reminds me of another issue I helped resolve involving a site model that was incurring a great deal of processing with little to show for it. Evidently it was fixed by a process that will correct corrupt data/objects in the file. See this discussion. I've encountered imported SketchUp objects that induced similar problems and various other conditions too, such as 'far out objects' - a condition that can overburden even the most powerful computers and induce a variety of symptoms so broad I'm no longer surprised by any of them. It is quite often the cause of document-specific issues submitted to us. While the issue you're facing could indeed be due to a bug in the software, experience, symptoms presented and lack of other reports make me suspect something specific to your file (more likely) or perhaps something specific to your system (much less likely). Check out the first discussion I linked to above. Maybe it will lead you to a solution. Cheers, Jeremy
  12. Here is the current solution for this: https://forum.vectorworks.net/index.php?/topic/90360-vw-2022-sp2-menu-bar-not-working/&do=findComment&comment=420466
  13. Hi Stephi, This is not a comprehensive list but here some things that can cause Vectorworks (or the computer in general) to perform slower than it used to: Corrupted .plist files or other components in your operating system folders. This happens sometimes when updating the operating system. Slowdowns after updating have happened to me but as I recall this corrected itself. This is also one example why superusers perform fresh ('clean') installations of their operating system instead of just upgrading. Hard drive not having enough free space. The traditional advice was to always have at least 10% free. Memory Pressure (found in the Memory tab of the Activity Monitor app) being too high. Slowdowns are usually only apparent on computers that have a HDD (hard disk drive) and not an SSD (solid state drive). Vectorworks Workspace or Settings files becoming corrupt. Slowdowns are more likely due to Workspace files than Settings files though. Solution: Resetting Vectorworks Preferences. - Make sure to back up your User Folder as part of this process. If slowdowns are only apparent with certain files then I would expect performance is a function of how much geometry is present in the file, perhaps PDFs or images/textures, or corrupt objects. It depends under what circumstances Vectorworks is running slower. More information would be necessary but the fastest way to diagnose it is to have someone schooled in this stuff to remote in and observe performance and circumstances as they occur.
  14. Sorry to say, Twinmotion do not yet endorse M1 Macs for use with Twinmotion. From the Mac section of the Twinmotion System Requirements page: Given that the M1 Max was only released this year, I suppose you were using an Intel Mac when it was working for you.
  15. Renderings in the Design Layer can be stopped by either double-tapping the Esc key on your keyboard or the Command-. (period) key.
  • Create New...