Jump to content

mjm

Member
  • Posts

    948
  • Joined

  • Last visited

Everything posted by mjm

  1. Here's how the morning started @ work: open VWX file from Finder w/ VWX not running. File opens normally, @ sheet layer to be worked on today. select only VP on SL open viz palette, select then batch-edit a number of lights to boost intensity click update to update the sheet layer VWX immediately became unresponsive. What happened? Do I wait a while? Should I force-quit immediately? Wait, when's the last backup, compared to working file? Productivity = 0.00 So—restart… While it's restarting I start thinking: Oh right, gonna either have to keep what ever the last Perpetual Lic I own -and the machine it's running on (both in perfect health), for as we know, OSes move on cruelly abandoning all who came before- to access archived files, or spend time / money converting everything to DXF + PDF, so at least something is preserved in usable states. Just trying to imagine losing all access to all my files. Profoundly disturbing thought. A disempowering feeling. As long as I pay you, I can continue to access my intellectual property, do I have that right? Wonder how long VWX Viewer will remain free? How's the community feeling about Viewer as a useful tool? Asking for a friend.
  2. @Mark AcetoJust VW. A reboot fixed that yesterday. Today I report that VW has ceased rendering in all render formats other than shaded. On any file. Even a new, blank file. Just checked Activity Monitor and Cineware.app is nowhere to be found. Wonder why that died. Time to reboot again
  3. Just have to say at this moment: It's 6:05pm where I sit, waiting for VWX 2022 to do…something. Attempting to edit RT texture, clicked on "edit reflectivity shader…" and boom—nothing. VWX froze like the carrot in Olaf's face. No spinning wheel of death (!), the app is locked tight. MBP M1 Pro Max 32 gb. Hard to rationalize spending what I already spend on this product to relentlessly have these experiences. Edit—I also cannot stress enough how detrimental to creative flow it is to have to stop in the middle of those moments to (hopefully) solve a software problem, whose most minimal effects likely to be a reboot & just as likely a convoluted process of analyzing, seeking counsel, finding solution/workaround and THEN getting back to that magic moment, ha. Hard to come to VWX with joy any more.
  4. like @zoomer, every time I have run Repair, it finds _something to repair, for ex; I ran it 3x in a row without opening VWX 2022. First time it reported 56 files repaired, second time 1 file repaired, third time it reported yet another file repaired. Also—just re-booted the M1 MBP, ran the updater/repair again & it repaired 1 file yet again. Curiouser & curiouser
  5. Yep, this has bitten me a few times. And I have had to deploy the exact strategy @TomWhiteLight suggests above.
  6. I'm unsurprised and definitely disheartened. It truly was that cringey moment reading @rDesign 's take on QC above.
  7. Super, Thank you @markdd, I'll check it out immediately
  8. I have attempted to use the schematic tool for booms for the first time. Yays: It's an easy tool to deploy Boos: having to make an array of fixtures sans c-clamp & moved up to accommodate new hang point on fixture (entire ETC Source Four catalogs for ex) (do I really need to do this? or am I missing something, as I am wont to do) Having the Schematic render a fixture such that it requires much fiddling to make it align with all it's other position sibs [see attached pdfs & vwx file - what is that red band which I cannot make go away, unless I restore the default rotation of th3 schematic) I feel reasonably confident I am missing something fundamental here. Any assistance gratefully accepted. Included is the vwx file as well s some output pdfs and screenshots. My profile shows my M1 MBP stats, I am updated to latest VWX svc pack 5 Schematics Test exp.pdf Schematics Test pub.pdf Schematics Test.vwx
  9. Renders out on my MBP M1 32GB ram
  10. @KenH https://app-help.vectorworks.net/2022/eng/assets/docs/VWKeyboardShortcuts.pdf
  11. I had many similar issues with prior intel 2019 MBP. W/ the M1 MBP, so far none of that has occurred. Not to say there haven't been other rando display issues from time to time
  12. Coincidentally, six days ago I received my 32gB M1 MBP Max (two months late, yet 1.5 months ahead of revised shipping info from APPLE). I've just been opening a small slew of larger VWX 20>VWX 21 files, mostly to see how much render times have improved: Anecdotally—not-so-much, however it does so extremely quietly and hardly warms up. While files were open, VWX released no memory. As I closed files, small amounts of memory were released. After last file closed, VWX's memory footprint shrank down to 6.80gB. (it opened with 4.18gB). Sidebar: Bizarrely (or is this normie?) when I activated Accessibility : Keyboard : Navigation… within VWX the service interuppts the spacebar insertion of a space and does…nothing. No other apps, excepting Adobe Photoshop & VWX 2022 exhibit this behavior. I'm guessing I'm missing something simple but have yet to find it…If you've conquered this issue, I'd be grateful for the knowledge.
  13. @Christiaan @Mark Aceto I never ever use the recent files menu for every reason y'all listed above.
  14. wow. Even tho I make blurry gobos all the time , it never occurred to me to have it emulate the beam edge dynamics. I've been attempting that through Beam Field differentiation.
  15. Sounds like maybe the menu item View: Show ACTIVE Layer Only… might have got clicked on. Also check your layer and Classes panes to see if everything got turned off by accident.
  16. @trashcanright there with ya
  17. As one who can barely type, much less program, it's literally a thrill here on the sidelines watching you folks build these incredibly useful mini-machines of code Thanks to you all
×
×
  • Create New...