Chih-Pin

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

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

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.

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.

Are you using Intel integrated graphics? Do you have a discrete graphics card installed on your machine?

Some people also post some relevant discussions here:

Don't thank me. :-) I only did a small portion of it. It's really an effort from a great team.

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

It's in our pipeline of fixing the bug right now. I will let you know when we have any definite answers 🙂.

Thanks for the reminder @zoomer. @bpsabatier has sent the file to us :-).

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

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.

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

@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

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.

Hello line-weight, If possible, could you send the file to me so that I can take a look? Thank you so much!! Chih-Pin

Have you tried python -m pip install pillow? If successfully installed, you can see what version of pillow it tried to install.

Suggestion heard, I will raise discussions with my colleagues and bosses.

For instance, this is a fast HL mode on a cylinder - This is a standard HL rendering -- As you can see, the edges on both ends of the cylinder are missing in the fast HL rendering. There are also other similar cases to this. In my opinion, we need to at least make fast HL look the same (or at least similar) in these cases before we can make it as one of the render modes.

Sorry to disappoint you on this. But based on what I, as a software engineer, suffered when adding new features and fixing bugs in this complex system, I believe it's not possible to be that fast.

This is basically correct, except you will also see similar trick when you are flying over the views in design layer HL render mode. Without this trick, it can't achieve real-time interactive HL rendering. But after you finish flying over, it will try to calculate the full and standard HL render mode. I personally agree with these two suggestions. In many cases, the fast HL rendering is good enough, and it's much faster. However, I also see some improvements needed for fast HL rendering. I also suffered the unnecessarily long time HL rendering in my own personal projects. I will create a VE(s) and raise the discussions internally. Hopefully, we can have these features in VW.

There are two kinds of "hidden line" renderings in VW, "normal" hidden line and "fast" hidden line. If you hit "hidden line" rendering, it will give you "normal" hidden line, which goes through calculations line by line, face by face, test the distance between the camera and the actual lines. This produce "real line segments" that will give us many benefits, e.g. sketch rendering, highlight the lines behind objects in different representations, decide whether it needs to show highlight lines or not, and ready to export vector-based drawings. For the "fast" hidden line, you can find them in "Section/Elevation in-Place" editing mode. We are basically using an OpenGL trick to create similar effects. You will find some differences in between these two hidden line modes. This is fast, interactive, and real-time rendering almost without any wait. I guess OnShape uses this technique to render hidden line using WebGL in your browser instead of getting the actual "lines" from the server. You can read some more discussions in this thread - In my opinion, there are rooms for performance improvements in the "normal" hidden line mode in VW. For instance, we can show the "fast" hidden line first, and gradually pull the results from the normal hidden line to the view. I'm not sure how soon this can be done, but I'm sure there are some re-engineering tasks to do prior to it

We do improve the stabilities of Best Performance overtime, even through service packs. This is one of our first priorities in terms of performance improvements.

Hello Dubman, I tried to edit a standard symbol in a floating pane without crashing. So there might be something else that causes the problem. Would it be possible if you are able to attach the file or send it to me with steps to reproduce the problem if you prefer? Thank you so much!! Chih-Pin

Hello RJDG, Could you send me the file if possible so that I can inspect the multiview data? You can choose to send it through the messaging system here on the forum. Thanks!! Chih-Pin