Jump to content

Kevin McAllister

  • Posts

  • Joined

  • Last visited

Everything posted by Kevin McAllister

  1. I would try extruding each letter separately or in small groups to see if I could find the problem geometry. Fixing the geometry is the most foolproof option. You could also run the Simplify Polys command to see if it deletes any coincident points. Kevin
  2. Matt, I always appreciate these explanations! Thank you for sharing! Kevin
  3. I have one project I've moved over to VW2022. I've seen some anomalies (mostly graphics related) that opening and closing VW solves. I usually start with the expectation that there will be something with any file brought forward from an older version or that has elements in it that have been brought forward through a few different versions. I'm not sure I'd move any further projects over at this point. I may start a clean project though. I'm not sure enough testing happens with moving older files forward even though its a common workflow. Kevin
  4. Wouldn't you just rotate the sheet layer viewport and add the annotation afterwards? I do this on projects all the time. Note that I have discovered a bug where rotating a sheet layer viewport to certain angles increases PDF sizes when publishing. Kevin
  5. An alternate solution might be to place a reference object (custom symbol) on the design layers and use the new Data Tags for the coordinates. The Data Tag will pull them directly from the reference object. Kevin
  6. After some playing with it I think I understand what you are losing (the Ignore Layers with Different Scale checkbox seems to be the key). There is no other way I know of to actively work across Design Layers of different scales that I know of. I'd never really thought to work that way but it really does make sense if you're creating the same base plan at multiple scales. It does feel like the next step would be to phase out the ability to have design layers at different scales.... Kevin PS. I've added my test file in VW2021 format in case anyone wants to toggle unified view on/off in it and see what this is all about. Unified View Test v2021.vwx
  7. I noticed it too. It's definitely new. KM
  8. You're not missing anything. There is a wishlist item about this very issue. You may be able to break it apart using another solid section command or using the Split tool, but those are definitely workarounds. Kevin
  9. @2oaks are you able to use two different view panes with different view options instead? Just curious if its a potential solution you haven't thought of. Kevin
  10. I agree that screen plane is still important for many tasks. Its biggest benefit over working plane or layer plane is that the snaps are reliable and there are no weird non-functional guides that appear in some 3d views (those weird radial red lines for some rotations are an example). For layout work, screen plane objects can't be beat, yet.... (I work entirely in 3d in the design layers and all my 2d work is in the annotations space of sheet layer viewports.) Kevin
  11. I'm curious if you work in 2d or 3d? I remember my old 2d workflow with multiple design layers in different scales for each sheet. I can't imagine working in 3d without sheet layer viewports..... Kevin
  12. Do they look this way in your 3d model or is it only in the sheet layer viewports? If its just on the sheet layers, its most likely the Detail dropdown in the Background Render Settings dialog of your sheet layer viewport. Here's a screen shot.... Kevin
  13. You should be able to Subtract Solids using a sweep. Its hard to know why you couldn't without a file. I'm surprised you could use Subtract Solids with a mesh since a mesh is not a solid. In the future I would convert an object to a generic solid if its giving you trouble. Kevin
  14. Are you able to post an example file? That would help us help you to solve your problem. Kevin
  15. Here's my take which is similar to Pat's. I would make the array in 2d first and then extrude it all together. Much easier to make a change later if needed. Kevin Stem Speaker.vwx
  16. Hello, I was troubleshooting a colour issue where a red looked different on two different sheets of a PDF in Apple's Preview. One sheet had been rasterized to create the PDF and the other had not. The original PDF was created using the publish command in VW2021. I switched to VW2022 to do some further testing and things got weirded. I created a new red swatch with the values R255, G0, B0. When I go back in to edit the swatch the picker defaults to CMYK and shows the values C0, M100, Y100, K0. When I switch the picker mode to RGB the colour values are R205, G10, B32 which are not what I sent originally. Is VW2022 now converting all colours to CMYK? Am I missing something here. Ironically the colours look much more consistent onscreen in VW2022. I know some work was done on the colour engine but I couldn't find any specifics. Apple's Preview still shows a discrepancy between the rasterized and non-rasterized PDF sheets. @JuanP is there any info about how colour management changed in VW2022? Should I always be using CMYK values where possible when matching client colours? Thanks, Kevin Colour Comparison.pdf Colour Comparison.vwx
  17. Bumping this wish again. Today's example, needing slices of a pie with boundary edges. Can't do it with arcs because there's no way to activate the hidden edges. Can't do it with convert to polygons.... yuck, too many points. Ended up doing it by slicing a circle. There should be a Convert to Polyline command (and apparently there is in some localized European versions). Kevin
  18. +1000 I had forgotten about those little corner crop marks! I almost exclusively use the "Fine Tune Camera View" button when working with Renderworks Cameras but they don't get activated with that command. I pretty much guess at my framing through trial and error. It would be great to have one single awesome camera tool that worked like the C4D camera system. Kevin
  19. until

    I was wondering where I might find it..... thanks for the tip @Andy Broomell! Kevin
  20. If the taper is even all the way around, you could use the Tapered Extrude command. Kevin
  21. I think Duplicate Along Path is the best option you'll find. There may also be a Marionette command someone has made to do it too. Vectorworks has a variety of divide commands but none of them have continued to develop or evolve. Arc into Segments for arcs, Line into Segments for lines, Even Divide seems to work on arcs, lines and rectangles. This would make a great wish list item. Kevin
  22. Looks like a good interim solution! Kevin
  • Create New...