Jump to content

PVA - Admin

Vectorworks, Inc Employee
  • Posts

    12,808
  • Joined

  • Last visited

Posts posted by PVA - Admin

  1. Most likely, there may be a way to disable it there, also it may sound odd, but check the laptops documentation and make sure there isnt a hardware toggle for it, i've seen some come with physical switches or fn key combos that can change that setting as well.

    Dont try to disable the integrated GPU in Windows device manager though, that causes a bunch of other problems (I know from experience)

  2. No flat size rating that determines it, speed and memory use also have to do with what KINDS of geometry you have. Meshes and some other 3d polygonal geometry types are particularly important to keep an eye on, but theres no strict regimen to stick to.

    • Like 1
  3. That GPU is only the minimum spec for what should run so that isn't too surprising. Vectorworks is a very demanding high powered application and it will use all system resources it possibly can. You MIGHT be able to reduce energy use by using Tools > Options > Vectorworks Preferences > Display > Navigation Graphics and setting it to Best Compatibility, that will reduce GPU usage, but performance will suffer.

  4. If you're on a Mac, you should be able to get at them directly, the "2x" ones are the ones for high res displays:

    Macintosh HD⁩ ▸ ⁨Applications⁩ ▸ ⁨Vectorworks 2019⁩ ▸ (Show Package Contents on 2019 app)⁩ ▸ ⁨Contents⁩ ▸ ⁨Resources⁩ ▸ ⁨Vectorworks.vwr⁩ ▸ ⁨Images⁩

     

    However I've attached a zip of that folder in case any Windows users need them, as I think its harder to get at them from that OS. The naming and folder structure wasn't meant to be user friendly, but searching for a tool name within this zip should find what you need.

    Images.zip

    • Like 2
  5. Memory usage can also be dramatically affected by how large your file is in conjunction with how many Undo operations you have set in Vectorworks Preferences. I believe he default is 20 operations, but many people increase this to 100 which can spike memory use significantly.

    We are also tracking our RAM and VRAM usage footprints and have some upgrades planned that should reduce how much memory Vectorworks and the VGM need to perform the same amount of work.

    • Like 3
  6. You may need to select the Section Viewport, and then under Advanced Properties > Attributes, make sure that Sepearate Cross Sections is selected and that  "Use Attributes of Original Objects" is checked, I think it will default to a solid grey or red section plane color.

    Screenshot included in case the German version has dramatically different names for the settings:

    image.png

    • Like 2
  7. If you resize the palette by grabbing and stretching the bottom right corner of that palette, do the tools appear, or flicker, or stay grey? This is 2019 Service Pack 3 you've installed? (I can tell this from the name of the installer download you used if you arent sure.)

  8. 1 hour ago, Matster said:

    So how do it edit my shutters quickly without a way to reference what it's doing? is there faster render than "Fast Renderworks" that will work?

    You can create a custom Renderworks style for this that is faster than the default modes. I cover this for a different reason here, but the same knowledge applies:
     


     

  9. This is now working again for me on 2019 SP3 on macOS 10.14, I am able to scroll by dragging to the edge not only in single view but also multiview, both were broken for me in prior releases and I had been able to reproduce it there. Does this happen in all files for you? Does it behave the same when drawing as well as drag/dropping objects?

     

  10. 15 hours ago, Mark Aceto said:

    OK, so what's the recommendation here? Is the high setting a decoy? All things considered, should we all just use the middle setting? Would we really notice a hit to graphics performance if the tradeoff is improved stability? How much of my time drawing is really taking advantage of that high setting? 20%?

     

    I dream of a VW with a single unified workspace for all disciplines (with Menus for each modality) and no GPU settings to fiddle with (just minimum/recommended GPU requirements), and it all just works.


    This is only half to help people workaround the issue. The other half of myself and a lot of other employees asking about this setting is that in Best Performance, pretty much all graphical glitches would be the fault of the VGM and significantly narrow down what the core problem is and what team needs to work on it. If the issue happens in Best Compatibility but NOT Best Performance, it means its a bug of the old graphic system and not as much of a priority. If it happens in ALL modes, it means that the issue will likely be much harder to track down, but that it is much more urgent that we do so than in the previous example.

    Eventually users won't have control over this and it'll only kick in the Compatibility modes when launched on weak hardware and the user will be alerted to this fact. Kind of like a Safe Mode, but that could be awhile off as we are still transitioning systems into the VGM.

    • Like 4
×
×
  • Create New...