Jump to content


  • Posts

  • Joined

  • Last visited


33 Great


Personal Information

  • Occupation
    User Interaction Lead Software Engineer
  • Homepage
  • Hobbies
    classical music
  • Location
    United States

Recent Profile Visitors

1,288 profile views
  1. @zoomer Thanks for this valuable information!! We will discuss internally and see what's the best solution moving forward regarding to their XML format changes.
  2. Hello @zoomer, Please put the configuration file I attached here into your configuration folder in the installation directory. On my machine, it's located here: C:\Program Files\3Dconnexion\3DxWare\3DxWinCore64\Cfg Remember to restart your machine to make sure the config file is loaded correctly. In my understanding, they changed the configuration file format and thus the files written in the old format don't work anymore. Please let me know if this works on your machine. We will look for a more pe rmanent solution to their new configuration format. Thanks!! Chih-Pin Vectorworks2020.xml
  3. Hello @halfcouple 1. Try find the configuration files in your 3DConnexion folder. Mine is located here - C:\Program Files\3Dconnexion\3DxWare\3DxWinCore64\Cfg 2. Copy your existing VW2020 configuration file in the folder to somewhere safe, e.g. your desktop. My file is Vectorworks2020.xml 3. Find the configuration file you wish to copy from, in your example, it should be Vectorworks2019.xml. 4. Copy to your desktop as well, and open it using your favorite text editing program. 5. You should be able to find the signature section like below - <Signature> <Name>Vectorworks 2019</Name> <ExecutableName>Vectorworks2019.exe</ExecutableName> <Transport>S80</Transport> </Signature> 6. Change Vectorworks 2019 to Vectorworks 2020, and Vectorworks2019.exe to Vectorworks2020.exe. 7. Change this file name to Vectorworks2020.xml and copy back to the configuration folder: C:\Program Files\3Dconnexion\3DxWare\3DxWinCore64\Cfg 8. Restart your machine and see if your macro setting is back. Let me know if this helps or not.
  4. JPG files don't have the alpha channel that represents the transparent information. If you want to import an image with a transparent background, you have to import .png images. Also please make sure the "Import Alpha Channel" checkbox is checked under the PNG radio button. If the checkbox is grayed out, the image you are importing does not have an alpha channel attached to it.
  5. Are you using Intel integrated graphics? Do you have a discrete graphics card installed on your machine?
  6. Some people also post some relevant discussions here:
  7. Don't thank me. :-) I only did a small portion of it. It's really an effort from a great team.
  8. @bpsabatier Those Marionette doors are definitely the problem. It is located further than our observable universe (1070 times further!!). We are trying to see how and why these Marionette objects are generated and corrupted. So for now, I would avoid using NanaWall doors. Also, one trick you can do to delete these doors is to select everything you want in the view and do an inverse selection. You will see it selects the doors located further away. Then you can execute "edit>clear" with those doors selected. Then you should be able to get the correct fly over back again.
  9. It's in our pipeline of fixing the bug right now. I will let you know when we have any definite answers 🙂.
  10. Thanks for the reminder @zoomer. @bpsabatier has sent the file to us :-).
  11. Hello @bpsabatier, If possible, could you attach the file here or send me through the message? We could inspect the file carefully and identify the problem. Thanks!! Chih-Pin
  12. You can see more multi-core usages almost anywhere, including those listed above, especially transiting from one view to another, entering/exiting editing modes, turning on hidden layers, changing view render mode, turning on multi-view, and now switching between sheet layers.
  13. I haven't done the experiments on this by myself. But this is another way to reduce motion sickness -- https://www.wired.com/2015/04/reduce-vr-sickness-just-add-virtual-nose/ But no matter what, I believe that motion sickness will still be there unless the headset has some optical magic implemented, something like this -- https://www.theverge.com/2017/12/20/16800474/magic-leap-one-creator-edition-augmented-reality-goggles-announce
  14. @Pat Stanfordis correct. The ViewPane and splitter data are saved with the document. So you are able to save your templates with your preferred view pane configurations. But if you do not load from the template when creating a new file, it will create the default pane and splitter configurations. Chih-Pin
  15. Just for the record before we can provide the fix. If anyone runs into the similar issue in MultiView, please try turning on Unified View. This may solve some navigation issues (e.g. zooming) in perspective view with Unified View off.
  • Create New...