Jump to content

Josh Loy

Vectorworks, Inc Employee
  • Posts

    282
  • Joined

  • Last visited

Everything posted by Josh Loy

  1. Are snaps enabled for other layers and classes?
  2. @Bryden Scott I have not seen this issue. Does it happen with every file, all of the time? What if you open a Saved View in a new pane?
  3. @Bruce Kieffer Happy New Year! I'm having a little difficulty understanding what's not working; next time you have the issue would you mind doing a quick screen recording and sending it to me?
  4. @michaelk thanks for pointing this out and bringing this up! We've been trying to find a reproducible case that causes this, would it be possible for you to DM me a file and the steps required to get Unified View to automatically turn off? Thanks and any help is very much appreciated!
  5. It's also a little hidden since you have to double click it to "Create Subdivision Primitive."
  6. Thanks @Tom Klaber for the feedback. The gray appearance is related to the style that we chose for the new interface, unfortunately we can't easily change it for the button selection and will need to make bigger style change which we are looking at for the next release.
  7. I believe it's related to your accent color...
  8. There is a command called "Align working plane with current view" which might be able to help with some of those alignment concerns along with the "Snap to working plane."
  9. @BNeilson thanks for pointing this out, it should be fixed in the next major release, VW 2024.
  10. Thanks all, we are looking into this! To be completely honest the performance I see is great on both my Windows and Mac computers; even after copying the GLs several times. I'll pass this off to our QA department and will report back what they find.
  11. @Matt Leak it definitely shouldn't be that slow; did you happen to disable "Accelerate graphics" under the Display tab of the Vectorworks Preferences? Disabling "Unified View" in the Document Preferences can also lead to those kind of redraw hangs. If that doesn't work can you DM me the file so we can take a look? Thanks for pointing this out and helping us address it.
  12. @Tom Klaber and @Dan Hoffman, as noted above the preview swatch on Windows was a bit larger than the one on Mac, we will update the size of the Windows swatch to match in the next service pack. Please let us know if anything else isn't working as expected. Thanks again for pointing this out!
  13. @Tom Klaber and @Dan Hoffman thanks for the feedback and I'm sorry to hear about the frustration. We'll look into options for the next release but you really just want a way to turn off the swatch zooming code?
  14. @Sylvia sorry you're having an issue updating the HL viewport. We've made a lot of optimizations with HL rendering for VW2023 which should have helped prevent this. Would you mind letting me know what build of Vectorworks you're using and direct message me the file so we can take a look? Regards, Josh Loy
  15. Sounds good, we'll add an enhancement request for that. With the eyedropper and color export we didn't see a need for this, Apple may not offer an API for it either, I'd need to check. We'll also add an enhancement request for this. That's a bit subjective but was chosen to save palette space. The new "Standard Vectorworks Colors" now have primary colors, I asked our content team about the order... The far left column is the pure hue of the color family and is based on HSV color theory which uses a full 360° circle to cover the pure hue spectrum using digital color mixing so the standard RGB that monitors use as opposed to the Red, Yellow, Blue of pigments. Each hue is 15° of arc on the circle starting at pure red which is 0° going all the way around to 345° which is why there are 24 hue families. Once the pure hue was established to create a color family row we then created the three color scales for that family. Starting at the pure hue and working across the row there are 5 tints using a 12% scale that goes towards a pure white. Essentially the Saturation decreases which is the equivalent of adding white to the pure pigment. The second column is the tone scale with 5 tones and it is the same 12% and this alters the saturation and value which is just like adding grey to the pure hue. The final 5 colors are the shades and this uses the same 12% scale which decreases the value which is the same as adding black to the pure color. We chose the pure hue and groups of 5 because we were limited by code to a fixed width of 16 colors and that was the easiest breakdown. Also remember that this palette was designed using scientific color theory to give a good base group of colors and to include pure yellow and a better separation of the greys and very dark colors which were the issues with the old color palette which is still included. https://en.wikipedia.org/wiki/Grid_illusion This is subjective and we tried to find the color that best contrasts the selection and doesn't get lost in the grid. Again, Apple uses a non-standard CMYK formula in their color palette which has resulted in inconsistent colors since we introduced CMYK a long ago, we have no way of working around it. Pick a color and go through the different sliders and you'll notice the values change from what you initially selected (the API only returns RGB). Sometimes the conversion gives different rounding results. In this video I was trying to modify the MacOS cursor color in the system settings... CursorColorPicker.mov
  16. Hey Christiaan, thanks for great feedback and pointing this out. We initially thought the color spectrum would be used in this case but I can definitely see the benefit of anticipating the color with the preview in the slider. With the eyedropper and document colors we didn't think this would be worth bringing along. Unfortunately Apple's color picker has a very limited API and we are no longer able to work around its issues. This is why most, if not all, professional graphic programs will create their own color picker. If you've ever tried to use CMYK with Apple's color picker you'll quickly realize something isn't quite right, because Apple has their own CMYK format which no one else uses and no one can correct. Windows' color picker, need I say more?
  17. @GarrettBurleson thanks for pointing this out and I'm unfortunately not able to reproduce the problem you describe. Just a couple of question and feel free to DM me; is this happening on Mac or Windows? If you reset the key mappings or choose a different workspace does that help?
  18. @Mike Wood this sounds like a bug but I was not able to reproduce it with the steps you mentioned. Would you mind sending me the file that shows the issue? Very much appreciated and thanks for pointing this out.
  19. @MaltbyDesign the by-class fill style of "image" on the "Millwork-Main" class is causing the extrude to become transparent. VW does not normally allow extrudes to take an image fill and applying via class override was missed. This will be fixed in the VW2022 SP4 release, thanks again for pointing this out.
  20. @Andy Broomell Just so we're clear, the shaded/opaque move preview is not being changed; just the bug that caused groups to incorrectly use their bounding box has been fixed. Let me know if moving anything else causes an issue and if you think a way to revert back to the old wireframe preview is necessary. Thanks!
  21. This should be fixed in the upcoming VW2022 SP4. In the meantime, pressing the 'b' key while dragging the group will activate x-ray mode, working around the problem until SP4 is released.
  22. @Daniel M71 Have Vectorworks Tech Support been able to help you resolve this issue? Do make sure you get the driver directly from NVIDIA, in the past we have seen problems with vender versions of graphic drivers like Microsoft, Dell, PNY, etc. it's better to get them straight from the manufacturer if possible. https://www.nvidia.com/Download/driverResults.aspx/186958/en-us
  23. Hey all, great conversation! If I understand correctly the issue is if I draw planar objects in top, copy them, and them paste them in a front view I only see a sliver because they're pasting to a plane parallel to the layer plane. Screen plane didn't have this problem since those objects are always perpendicular to the view. The "Screen Aligned Plane" is active in front, back, left, and right views even when modifying components; if we modified the paste code to switch layer plane objects to use the screen aligned plane instead would that address the issue? Thanks again for all of your feedback and suggestions, screen plane shouldn't be a workaround. 🙂
  24. @Christiaan I'm not sure why we've never had an Unshaded Polygon No Lines option (probably some historical reason) and it seems like it would be pretty easy to add one moving forward. When you talk about efficiency are you mostly talking about update time or file size? Does it ever matter that RW and Shaded(OpenGL) create raster images whilst the Polygon modes create polygons? I guess I'm just asking if the images ever get in the way and if users just want only geometry. We might be able to get the desired effect by adding a unshaded option to RW and/or Shaded(OpenGL.) All of this said it would probably be easy to add an Unshaded Polygon No Lines if that would be helpful to users. The polygon modes have definitely received the least amount of love as we've been focusing on the others and I'll definitely look into your polygon performance concerns.
×
×
  • Create New...