Jump to content

Mark Aceto

Member
  • Posts

    3,799
  • Joined

Posts posted by Mark Aceto

  1. 18 hours ago, Andy Broomell said:

    Nah. Many years ago I got tired of my most-used tools having the least simple shortcuts.

     

    So now it's:

     

    W = Wand (Select Similar)

    E = Eyedropper

    R = Rotate

    T = Tape Measure

    O = Offset

    P = Push/Pull

    A = Attribute Mapping

    S = Scissors (Trim)

    K = Knife (Split)

    L = Connect/Combine

    M = Move by Points

     

    Plus some others...

     

    So this is where i get a little stuck because there are 2 ways to go with this:

    1. Mnemonic (as in your example)
    2. Arrangement (WASD, UIOP)

    I've been down a numpad / macropad / Streamdeck rabbit hole for months trying to figure out how to remap all the right-handed shortcuts I never use because my hand has a kung fu death grip on the mouse.

     

     

    This is the current numpad challenge:

     

    IMG_7669.thumb.jpg.3c60cb216b7bd08b0d1ff001e7ca9a86.jpg

     

    IMG_7670.thumb.JPG.3c5eaaff0033338001b8e9328c8daf4e.JPG

  2. 18 hours ago, Andy Broomell said:

    I made mine Opt+N

     

    And I can double-press N for unconstrained tool modes! Need to assign missing hotkeys to all tools now... 

     

    Seriously thinking about third party plugins too... 

  3. better yet, what is the damn shortcut for unconstrained mode?

     

    i desperately want to Option+N or something similar

     

    then again, i would also love to not accidentally fat-finger multiple views when trying to dimension... 

  4. as a test, i left some VW 2022 files open overnight to see how much memory they leaked

     

    right before i saved files, and quit VW:

    1963746078_ScreenShot2022-08-31at4_19_07PM.png.c144f8ada54231b95c8ce5e7ccafbcf9.png

     

    a few minutes after quitting VW:

    1540351705_ScreenShot2022-08-31at4_22_26PM.png.19b49390d5dc6c8620e9aa370725e3b4.png

     

    after reopening one of the files:

    1971654488_ScreenShot2022-08-31at4_24_00PM.png.cc6ed1c5a11c939732764e3072a39362.png

     

    total elapsed time was about 5 min from the first to last screenshot

     

    this is probably about to be obsolete in a few weeks but it's a data point nonetheless

     

    will retest on VW 2023 at some point

     

    in the meantime, mac users shopping for a new mac should probably plan on paying for a little more unified memory than they anticipate they'll need (based on past performance) during the transition from intel to arm

    • Like 1
  5. 23 hours ago, Andrew Pollock said:

    I always wondered if a multi core machine could be developed that had instead of additional "efficiency cores" it had an overclocked or hi speed core.

     

    On Windows, yes. It's up to Apple if they want to do that for us (along with a hardware accelerated GPU for realtime ray tracing in UE/TM).

     

    The other thing I'm trying to wrap my head around is I can bring these same high poly / heavy geometry models I receive into Rhino, and it handles them with ease (even on an Intel MacBook Pro). So, yeah, the bottleneck is single core but... 

    • Like 1
  6. On 8/7/2022 at 9:05 AM, Tom W. said:

    Is it because I am using layer import referencing rather than referenced design layer viewports? Would using the latter result in smaller files?

     

    Yes and yes.

     

    Just looked up a recent project: 85mb file referencing 2.89gb combined file size.

     

    All caching is disabled in all documents because:

    • I'm not an architect with a 400-sheet drawing set, so I don't feel that pain when opening files
    • I have severe PTSD from a handful of corrupted viewports over the years
    • I'm a weight weenie when it comes to file size, especially when project sharing heavy files from Dropbox
    • Like 1
  7. Been fighting all day with high geometry files provided by vendors. GPU is at 2%. RAM is roughly 20%. A single CPU core is pegged, and the other 19 are idling, so this is just further evidence that the additional cores mostly benefit rendering because there are still so many operations that are, and will continue to be, limited to single core.


    This isn't a dig at VW. I just wouldn't want anyone to feel buyer's remorse about spending the extra dough on more cores if they don't need em for rendering. Real world context is everything.

     

    Will be interesting to see how M2 and the mythical Mac Pro can possibly help with this but it's gonna have to be in the form of faster single core clock speed, so... not sure how much Apple can move the needle (not that Windows would necessarily be much better at single core performance).


    The constraint I see with single core is like that quote from The Mythical Man Month, "A woman can deliver a baby in 9 months but 9 women can't deliver a baby in 1 month." You just gotta sit there and wait for that one core from start to finish regardless of how much money you throw at multiple cores.

     

    • Like 3
  8. On 3/13/2022 at 4:44 AM, line-weight said:

    On Friday I tried unticking "Use VectorCaching for faster drawing" in VW preferences but it didn't make much difference.

     

    Just did a quick test of what you suggested - I had "save viewport cache" and "save VGM graphics cache" both ticked, but unticked them, saved doc, closed VW and restarted.

     

    This is in VW2021:

    - File reduced from >2GB to 1.2GB

    - Opening the file in VW immediately occupies 14.9GB of memory according to Activity Monitor

    - By cycling through a few saved views, without editing anything, I could get it up to 21GB quite quickly

    - closing the file left VW occupying 6GB of memory (no other files open except for an empty "Untitled 1" file).

     

    So my impression is it doesn't improve things.

     

    I see there's also a box "save site model cache". I've not tried unticking that yet, might try that later/tomorrow.

     

    Just set a new record over here: disabling graphics caching (shortly after enabling it) reduced file size from 727mb to 254mb.

     

    Considering I had to Force Quit VW after it stopped responding, I still see no value in caching graphics to disk if you have a decent GPU. It's not worth tripling the file size (and associated memory) for whatever "gains" there presumable are... Unless you're on a 2012 MacBook Air with an integrated GPU.

     

    537435115_ScreenShot2022-08-25at1_48_54PM.png.9e13d72b1fa66cbb64d0bbbce59d797c.png345525931_ScreenShot2022-08-25at1_49_27PM.png.41ef295fe3f57b6eaa0afa33eb812615.png
     

    • Like 1
  9. 9 minutes ago, trashcan said:

    I can click the cells, format them, etc, but I can't modify the content in the cells.

     

    That sounds like a database vs a spreadsheet.

     

    10 minutes ago, trashcan said:

    I can modify cells and then it'll update the cells on my original, locked report.

     

    That sounds like a referenced worksheet.

     

    10 minutes ago, trashcan said:

    Content is NDA

     

    How about a screenshot of just the row headers (no data)?

     

    Is there any Project Sharing with this file?

  10. 1 hour ago, hollister design Studio said:

    Mark - I was looking at the scripts and wondering what are they showing and how would the info be useful?

     

     

    @michaelk wrote a bunch of scripts to format cells etc without having to constantly disrupt your workflow by right-clicking, clicking Format Cells, clicking on a tab, yada, yada, yada... more clicking... Enter... 

     

    They're the next best thing to having the Excel / Sheets editing interface we all dream of (not holding my breath).

    • Like 2
  11. i think this may get complicated by object type (these are just simple extrudes), referenced layers, etc

     

    also this may work for your clip cube section viewport as well

     

    and you can bring the opacity way down when you export / publish (i'm convinced a former employee is having a laugh at the default value)

     

    259249302_ScreenShot2022-08-21at8_58_11AM.thumb.png.db6ad9e4cb4d6548c79a2acae7e332d2.png

×
×
  • Create New...