Jump to content

Jeremy Best

Distributor
  • Content Count

    217
  • Joined

  • Last visited

Community Reputation

78 Excellent

5 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

1,157 profile views
  1. If it helps, you can save the webpage of the guide to your local drive. If you save it as an HTML format you can send/share it so any desktop web browser can open it.
  2. Hi @Bas Vellekoop, I've just re-tested Allan's original v2017 file in Vectorworks 2020 SP1 and the issue seems to have been fixed. I found: The marionette object didn't jump to a different location when moving it in orthogonal 3D view (the way I did in my 'Shifty Marionette' video posted above). The profile's position relative to the path also remained as it was, after specifying my own symbol/profile in the OIP - which I believe is due to the customised code Allan put in the 'Path Extrude' node.
  3. I've confirmed your finding through testing. I suspect this is something that can't be implemented, because in all prior versions of Vectorworks, to edit any other operations applied in the creation of a 3D object, fillets and chamfers had to be removed before prior operations could be accessed… But it's worth asking. I'll submit this to engineering. .
  4. It is very strange that a clean installation doesn't deliver the Basic Tools palette, although your installation is SP4, when the current Service Pack for Vectorworks is SP5.3. Ideally, you'd be on the latest Service Pack before starting troubleshooting. If you haven't already done so, restart your computer. Regardless of whether this resolves the issue: Run the dedicated Vectorworks 2019 Updater app in the Vectorworks 2019 application folder. If that doesn't resolve this issue, proceed as follows: If you want to devote 5 to 20 minutes to determine if other software is causing inference with Vectorworks: Restart your Mac in 'Safe Mode': Restart your computer and hold down the Shift key before you see the Apple logo. (It will take longer to boot up than normal). Ensure no other programs are open when you open Vectorworks and see if the palette now appears. If the palette now displays you'll have to deduce what app is causing the conflict. Contact your local Vectorworks distributor if you need assistance. If Safe Mode doesn't enable Vectorworks to display the Basic Tool palette OR if you skip doing it, proceed as follows: Restart your Mac. If you have antivirus software I would disable that and keep it disabled until you have completed the following: Re-downloaded the installer from Vectorworks Service Select. (Perhaps you current download/installer has been corrupted). Uninstall Vectorworks (again). Close all other apps. Run through the installation. If asked, don't migrate data from prior version. If you've noticed other oddities in the behaviour of your Mac outside of Vectorworks I'd consider something else is likely responsible.
  5. I think being able to seperate the Layers and Classes Navigation tabs into their distinct palettes would greatly help the efficiency of user's with workflows such as the above. It would be good to hear from other users to gauge how beneficial this would be for how many. @kyleinvert720, I have one small contribution that will half the number of clicks to effect 'Force Select' and hopefully hasten your workflow. I just tested this myself and was able to make a Forced Selection using a single (Middle) click on my Magic Mouse although there are plenty of other ways and mice that can effect the same result: In Vectorworks, use the Workspace Editor to add the 'Force Select' command to a menu bar menu. (I chose the 'Edit' menu). Apply a unique keyboard command to the command. (I chose, '⇧⌥⌘F') Set up the 'Middle Click' function of your mouse to activate that command: Depending on the method/software you use to do this, you might be able to isolate this to only occur when Vectorworks is active. I used the app Multitouch for macOS and set up the Middle click option to execute this command. Now with a single (middle) click, I can Force Select any greyed/visible object in another Class or Design Layer.
  6. I'd like to know whether you mean you just clicked the 'Reset Preferences' button on the Vectorworks Preferences window, or if you executed the process referred to as, 'Resetting Vectorworks Preferences.' - If you did the latter, then my post to you on the other discussion about removing a migrated Workspace folder would be moot because the Resetting Vectorworks Preferences process accounts for this.
  7. Hi @Julia79, the full prescription delivered by @Adam Robinson above is also what I recommend. I've noticed what seems to be a trend of issues for users of Vectorworks 2019 who have opted to migrate Workspaces from a previous version of Vectorworks and I suspect this will be the case for you also. I'd be interested to hear if this works for you.
  8. Seeing as you're (also) getting functional issues unrelated to files ("settings are reverting without being manually input") then I'd consider the following likely contenders, in order of likelihood: You've migrated your Workspace and/or Settings from a prior version of Vectorworks. (Usually okay, but I've encountered a few users for whom this has caused issues). Your installation is compromised. If this is the case: If you have antivirus installed and if it was active during installation this could be cause. Conflicting software (when concurrently open). Historically Sketchup has caused interference with keyboard hotkeys and commands but I've encountered one or two others that do this as well. 💊 If you want an almost certain fix for this, skip to the third option. If you want to try the easier ones first I've listed them in order of ease. Try using an alternate workspace - preferably a default one (Tools > Workspaces). If you can't discern if it's a default one or not, quit Vectorworks and delete the Workspace folder. If this doesn't resolve the issues; Quit Vectorworks, delete the entire Vectorworks User Folder, reopen Vectorworks. If that doesn't work, perform the Resetting Vectorworks Preferences process.
  9. Vectorworks 2017 was no longer supported when macOS Mojave was released, hence it has not been updated to work on subsequent operating systems. This is almost certainly the cause of this behaviour, especially because it occurs on all other Mac in the lab. Contact your local distributor to instigate receiving the latest version of Vectorworks which will circumvent this issue and likely include free technical support. (The conditions may differ between markets/distributorships). I realise this is a very late reply, but I'm posting also for the benefit of other users researching this symptom.
  10. Vectorworks was loaded (ready to respond to my input) at about 22 seconds. (I have nothing in my Resource Manager and no default file loading) and Vectorworks-related CPU activity died right down at about 25 seconds. I despise activities that needlessly consume time or effort. If they can be eliminated by better/alternative workflows by utilising capabilities on offer, then that's what I do. If you know the even part of the name of the resource you seek using just the search function the resource you seek is just a single click-and-type away. This brings everything from 'Everywhere' for you to browse in one place instead of going in and out of multiple folders or files. If you don't know the name and have just one library file (and it's currently selected) using the resource-type menu can be used to show only the type you want to choose from. Add a search term to further narrow the search results. Creating and sticking to naming conventions could also save a lot of time, over time.
  11. A bigger library file will make opening the Vectorworks program slower as it will have more content to load into memory for the Resource Manager to be able to access quickly. But this shouldn't take longer than multiple Resource Manager files with a combined size that's the same. I would however expect it to take slightly longer to open and browse the content of a big, single library file, but if you have enough RAM to support the demands you're creating then this would probably be imperceptible or negligible. If you find otherwise, you could see if dividing the content up into subfolders improves things (yuck! IMO), or organise your library into multiple library files (instead of subfolders) or upgrade your hardware spec - which will have other benefits.
  12. I said 'not necessarily' meaning that's not always the case: Vectorworks has had the same hardware requirements for versions 2018, 2019 and 2020. (This doesn't mean compatibility of hardware or drivers won't become an issue when the hardware falls out of the support period). Apple's mobile operating system iOS was partially re-written in version 12 and achieved massive speed/efficiency gains. (40% faster loading apps, 50% faster revealing the keyboard) The demands of the operating system you came from might indeed contrast with that of macOS Mojave as there is definitely an upward trend in the demands of software releases over time. Based on your current signature it looks like you might be running either an old MacPro with an aftermarket graphics card or a Hackintosh. If that's the case that's a big caveat regarding compatibility between your graphics card, the drivers and your software.
  13. Newer software including operating systems do not necessarily demand more of your hardware than prior versions did. This is because engineers can find more efficient ways of getting a computer to do the things it does. For example Vectorworks 2020 has been programmed to display 3D geometry in varying levels of detail, factored by the users zoom level. This change has made Vectorworks 2020 way more snappy when moving your view around in 3D than prior versions. However - I gather - other changes have put new or different types of demands on graphics cards too. If you're your graphics card - or the newest driver available for it - can't process/handle modern conventions employed in current software, then that warrants a new card/computer.
  14. You can change the brightness of the Heliodon used in the Object Info Palette. That or Image Effects are the current most likely causes in my opinion. Other possibilities include, in rough order of probability: Image Effects might be turned on and imbalanced (bottom of the Object Info Palette) Textures with very high levels of colour brightness Textures with high levels of reflectivity or glow The file is corrupt or has a corruption in it. - Verify by mocking up a quick test-file using the same light/render settings. Your installation is misbehaving: Try restarting Vectorworks. Failing that: Try restarting your computer. Failithing that: Reset Vectorworks Preferences.

 

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