Chih-Pin

Vectorworks, Inc Employee
  • Content count

    65
  • Joined

  • Last visited

Everything posted by Chih-Pin

  1. 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.
  2. 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
  3. Have you tried python -m pip install pillow? If successfully installed, you can see what version of pillow it tried to install.
  4. Suggestion heard, I will raise discussions with my colleagues and bosses.
  5. 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.
  6. 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.
  7. 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.
  8. 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
  9. 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.
  10. 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
  11. 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
  12. Thank you!! This issue is addressed in the internal build and should be able to make it to the public later. Chih-Pin
  13. Hello lgoodkind, If it's not under NDA, could you attach the file or send the file to me? Thank you so much!! Chih-Pin
  14. Hello lgoodkind, I just tested it with SP1 from a blank file with two panes, one is top/plan with rotated plan and the other is perspective view. I'm able to turn that perspective view into OpenGL rendering. Could you describe more about the problem you are seeing? Thanks!! Chih-Pin
  15. Hello line-weight: Could you also post this on the wishlist board so that other users can discuss the wish in the same thread? I am also collecting the multiview feedback on the wishlist board. Thanks!! Chih-Pin
  16. Hello Dubman, If you are talking about changing the visibility settings using the dropdown in the Navigation Palette, we are currently addressing the issue. Here are some previous discussions - Also, if the "Use Same Visibilities in All Panes" is checked, the changes to the active design layers will apply to all the panes with design layers. Hope my explanation helps, and let me know if you have further questions. Best, Chih-Pin
  17. Hello Tom, I'm sorry that this issue causes some inconvenience to you. There is a problem with the visibility drop-down menu in the layer/class palette when the floating pane is active. We are addressing this issue now and hopefully, the fix can be push to the public sooner or later. Before that, you may need to click on the empty area on the palette to notify the palette to be activated before clicking on the drop down. The floating pane will still be active unless you click on other panes in the main window. And the visibility modifications will still be applied to the floating pane. Chih-Pin
  18. Hello@Jeremiah Russell, Thanks for reporting the issue you are seeing. If you don't mind, could you attach the file here or send it to any place where you think safe and I can reach. I will take a look and see if there is anything we can do here. Thanks!! Chih-Pin
  19. Thanks line-weight for your input!! Currently, the interaction logic is as follows: If the user uses purely mouse interactions, e.g. left, middle, right mouse clicks and mouse wheel, the system will activate the pane under the mouse cursor. Otherwise, the system will apply the current interactions to the currently active pane (pane with blue border). The main reason is that VW is not sure whether the user's attention is in the pane under the cursor or not. Let's think about the following scenarios: When the user clicks on OIP and tries to modify some parameters on the selected objects with the mouse cursor on a pane, we don't want that pane to be activated because there might be other selection sets in those panes. In a scenario of using 3D mouse, the 2D mouse cursor may also be moved away from the pane where the user's attention is, e.g. on other panes or in tool palettes. The best way, for now, is to apply the navigation to the active pane (blue border). While I understand that sometimes the user would like to automatically activate the pane under the mouse cursor, there are also side effects here and we need to make the tradeoff. I've submitted this as a bug. So hopeuflly we will be able to push the fix to the public sooner or later.
  20. Just for the record.. I attached a video that demonstrates the "drag an edge to move window" behavior. There are also some discussions here that may help: https://apple.stackexchange.com/questions/71112/how-do-i-move-a-window-whose-title-bar-is-off-screen DragWindow.mov
  21. Which version of MAC do you have? If you are able to grab any edges, you should be able to move the pane by dragging the edge without resizing it. For instance, if you grab a vertical edge, you should be able to drag it horizontally to move the pane, and vice versa. This OS level trick should work for all the applications windows on Mac, at least Sierra and high Sierra. But I don't remember whether it supports older versions of Mac OS X. Let me know if it's still not working for you. :-)
  22. I'm sorry the crash caused a mess for you. There are some OS level limitations that we need to work around for the floating pane being too large problem in your case. In this case, if you are on windows, you can use the OS level hot key -- Windows + left/right/up/down, to move the pane. If you are on mac, you should be able to grab the edge of the floating pane to move the pane and resize it. In addition, I think there is no "Close Floating View Pane" command, but there is a "Create Floating View Pane" command. It basically will duplicate the current active pane, including a floating pane, to another floating pane.
  23. Interesting. If I create a simple hybrid symbol with 3D cubes and 2D rectangle in it, I'm still able to highlight automatic working plane without entering the symbol in VW 2018. There might be some additional settings in the file or the symbol?
  24. Thank you so much for the information, When you move the objects in a 2D Top/Plan pane, it will not be showing the real-time feedback in other 3D panes. There are some more discussions here:
  25. Hello Nikihoops, Could you elaborate more on the issue you see? Do you mean it's not showing the real-time feedback in other 3D panes? Or after you finish moving, it's not showing updated location in other panes? Thanks!!