Jump to content

dtheory

Member
  • Posts

    153
  • Joined

  • Last visited

Posts posted by dtheory

  1. Hi Ed, David from Seattle (bike group) my bad if this is a different Ed Wachter.. Chiming in on 2022, performance is far better on my M1 mini, invisible object bug seems rare.. I did get some locking or crashing, but that was on early builds, that seems much better with the updates..

  2. @Jesse CogswellThank you for making this available to our community! 

    This is a great tool.. definitely should be core functionality of VW out of the box. Completely non-modal would be even better,

    but I don't think that could be done with scripting, unless I'm mistaken..  but I digress..

    I'm using it in my document context right click, and I've found that when I'm in a viewport annotation

    it'll appear only if an annotation element is selected.. not when simply right clicking in an otherwise "empty" part of the viewport.

    Is this expected behavior?

    Now... how about restoring the snapping tools to a palette.. is that a possible customizaton?

  3. I (probably) agree with you.. but I can't help but hope that the rumor mills are on to something..

    An M1 Max Mini would be a super hot seller.. so there's that..

    4 minutes ago, Gilbert Osmond said:

     Unfortunately that probably won't ever happen as it would severly undercut Apple's high-end price points on the new M1Pro/Max Macbook Pros while also pushing the Mini in the wrong direction (from Apple's perspective) toward the performance tier(s) of forthcoming MX-powered Mac Pros.

  4. I'd snap up a Mini with an M1 Max and 32-64GB RAM in a heartbeat..  my M1 Mini (with Monterey) has been so great, I'd love to see what even more headroom could do..

    • Like 2
  5. 7 hours ago, halfcoupler said:

    Yes, right,  custom selection is more simple to use than select similar, especially if you don't know at least one object that already matches the criteria.

     

    8 hours ago, halfcoupler said:

     I think this has not changed in VW 22: you can still use the select similar tool with "Plane" as Select Similar Preferance Setting to select all objets with the same (screen-)plane .

     

    @halfcoupler, @Kevin K Both of these methods are helpful, true, but what I was getting at was something a bit different, which would be similar to the "purge" function

    and I'm really not sure it could be accomplished given the constraints of how we interact with the library items that are saved within a particular project file, i.e. only being able to show one object at a time with library objects..

    What I was lamenting, proposing, whatever, was the idea of being able to automagically go through an entire project and set all of the screen plane items to layer plane..

    I'm guessing that whatever the method, this might result in a lot of fiddly work with viewports etc. and as I think about it more, not positive what the benefit would be, except to be able to move forward with a legacy project in "layer plane only" mode. Thoughts?

     

    • Like 2
  6. I also am pretty impressed with the stability and snappiness of 2022.. that being said, I’ve had some glitchy behaviors with OpenGL (now “shaded”)’in which materials rendered incorrectly.. also one weird spinning beach ball that I had to eventually force quit to get out of.. it would be nice to have a tool to root out screen plane assets in a file to convert to layer plane..

    in files with many symbols etc.. it’s a bit daunting to think about going through and checking everything which probably ends up being hundreds of small items including library items that were created in previous versions of VW

    • Like 1
  7. I for one, would like to see an option to have snapping as a floating or dockable palette return to the interface.

    I find that with my setup, dual monitors, main monitor 30", the snapping palette is way less usable and much harder target to mouse over to than it was before.

    For me at least, it's a significant decrease in usability.

     

    • Like 1
  8. 8 hours ago, zoomer said:

    I think I have it since 2 (?) weeks.

    Nothing exciting so far.

     

    For Me VW, Bricscad, Modo, Blender, ... runs.

     

    Just OpenIFCViewer will crash when you try to open a file.

    Or a few (outdated) freelancer Apps will crash or not works

    as they should.

    For me Safari has some problems with certain Sites.

    @zoomerAre you testing on the M1?

    Thanks for posting..

  9. 2 hours ago, Sidge said:

    Hi there. I just ordered this mouse. Are you on a Mac?   Have you figured out how to Pan? Without holding down the space bar?

    Hi @Sidge, yes, I'm on a Mac Mini M1.. enjoying it a lot.. migrated from a 2013 Mac Pro.

    Never bothered to find out if I could pan without the space bar.. since that motion is so natural.. mouse in the right hand, left thumb on the space bar..

    I'm guessing what you want is probably possible.. maybe map the middle mouse button or another button to that function...

  10. Opening this file.. obviously I can't comment on why this happened in the first place, and why the various circles and lines cant be "force selected" and why the scale of the circles is so large etc..  lots of idiosyncratic behaviors here..

    This should be addressed by staff.

    The affected class is "paradiso".. this was by process of elimination..

    There is a line type in the file that includes the circles.. (Line Type 2). The giant circles are part of the line type..

    If this line type is deleted, the problem graphics go away..

    When doing the delete.. you'll be prompted to either delete completely, or choose another line type to substitute for the deleted one..

    I chose to substitute a simple solid line (Type 1).. file seemed to display normally from my limited sense of what it should look like..

    Seems like the display of the circles was caused by the use of this line type..

    • Like 2
×
×
  • Create New...