Jump to content

Andy Broomell

Member
  • Posts

    3,169
  • Joined

  • Last visited

Posts posted by Andy Broomell

  1. I didn't realize until I re-read the original post, and tried it for myself in VWX just now, that changing the Marker Scale for one instance also changes the Marker Scale for all other instances generated from the same Section Viewport. That doesn't seem right...

     

    Changing the line length per-instance would indeed be new functionality as discussed elsewhere, but I'm surprised we can't change the Marker Scale individually. Seems like a bug IMO.

  2. Some objects import from Rhino just fine. Anything rectilinear comes in as Generic Solids which is great.

     

    But then other things come in as hundreds or thousands of NURBS surfaces, which often slow down responsiveness.

     

    At the very least, having the option to automatically import those objects as Meshes instead of NURBS would be welcomed, since I find Meshes don't reduce responsiveness as badly. This option would need a conversion resolution setting, of course.

  3. But let's not gaslight him...

     

    Vectorworks is NOT great in this respect. It's not possible to lock an axis of 3D movement in the same easy way that any other modern 3D program does such as SketchUp or Blender. 

     

    The "T" thing sometimes works if you happen to be able to reliably move on that axis for a bit without other snaps getting in the way. But any sort of complex scene and this isn't really helpful and rarely works. (By the way, Mike, I'm guessing you're using a customized workspace which is why T is Trim for you. To see what key you should use instead or to set one up, go to Tools > Workspaces > Edit Current Workspace, go to "Keys" tab and enter a key for "Set Smart Point, Edge, or Vector Snap Lock.")

     

    That being said, Vectorworks desperately needs to add:

    1) a 3D dragger for basic moving of objects in 3D space (I've heard talk of this happening in the future), and also

    2) hotkeys to lock the movement to an axis without having to click on said dragger (like the arrow keys in SketchUp, or x y z keys in Blender). Sadly I haven't heard talk of this happening, but it's been often requested, and will be the only way Vectorworks will ever be taken seriously as a 3D app.

     

     

    • Like 3
    • Love 1
  4. Correct - I'd say any "functional" classes that are actually controlling sub-parts of Plug-In Objects (such as Ceiling-Main being used by the Door PIO) are understandable and should be kept. Another example is that the Plant tool seems to always come with a bunch of "Plants-XXX" classes which are controlling sub-parts of the plant graphics.

     

    So for me, the spirit of this thread is more about non-functional top-level classes that aren't necessarily controlling attributes of anything. But others might have differing opinions. That's always the hardest part with software design: finding a middle ground default that pleases everyone 😅

     

     

     

    • Like 3
  5. 5 hours ago, Tom W. said:

    Isn't that what this does?:

     

    I've never gotten that to do what it sounds like it should do. But if someone else has made it work I'd love to hear about it.

     

     

    For me, auto-generated classes are typically coming in from symbol libraries via the Resource Manager.

    • Like 2
  6. Agreed. Note that in the meantime you can employ the Eyedropper tool to pick up and place attributes from one Callout to another (make sure "Plug-in parameters" is checked). However, this doesn't let you pick and choose specific attributes the way Style-based objects do. Updating Callouts to be Style-based would be a nice improvement, along with bringing them up to speed in other ways such as the ability to have character Tracking.

    • Like 2
  7. I'm guessing you're in 2023 Service Pack 4, which has an issue where curved 3D geometry is getting faceted to a lower level of detail in viewports.

     

    Do you have a different version you could try rendering in to see if the problem goes away?

     

    You can also try going into the symbol to play around with different object types, such as converting an extrude to a generic solid (some users have reported similar workarounds but I can't guarantee anything).

    • Like 1
  8. That's only useful for applying prefixes or suffixes or replacing text. It doesn't re-number or do any actual sequencing.

     

    For example if you're wanting to renumber a range of sheets in order to insert a new sheet into the list, that's currently NOT possible except to do it manually. (It's oft been wished for on here though.)

     

    But it you wanted to change 1, 2, 3, 4 to 101, 102, 103, 104, that's possible with Batch Rename.

  9. 6 minutes ago, Tom W. said:

    I have the Visualisation palette in all my files but collapsed until I need it.

     

    You would still be able to pull the Lights tab off into its own 'palette' - this ability was added a few versions ago. It could still feel like a separate palette if you want it to.

     

    And yes, there's also some complication with the fact that selected viewports interact differently with the Lights tab, but this could be improved as well since it's currently a bit esoteric. I like your line of thinking where this functionality would be transferred to the OIP to better align with how Class & Layer visibilities work.

    • Like 1
×
×
  • Create New...