Jump to content

mjm

Member
  • Posts

    1,276
  • Joined

  • Last visited

Everything posted by mjm

  1. Thank you @klinzey for fixing this. I wonder if there might be a use for a sub-forum dedicated to VWX Resources which need attending-to? I have found multiple Spotlight fixtures with similar problems (lookin at you all forms of multi-circuit fixtures). I did learn that some of these problems can be relatively straight forward user fixes, such as correct stacking top>bottom of strip light cells so they number correctly. Still; having to stop and wring out why things are not numbering correctly is a definite productivity problem.
  2. I am so sorry to see yet another of these kind of grind-everything-to-a-halt issues.
  3. @Bill Werst I don't have any more time today & but so I've attached my file. Maybe it can help you find a solution. Signage example.vwx
  4. Good job @Dubman, I was just about to write about the loft as solution. Glad you found it.
  5. Thank you @JuanP. After several restarts, the fixture in question is now behaving appropriately predictably.
  6. So I was editing a spotlight fixture thru the OIP and an amazing thing happened and no it was not good. I repeated this several times. I will now shut down and restart everything. You'll see the fixture in question in the appropriate filter color L763. Upon editing the the fixture thru edit spotlight the color changes without my input, while still keeping the correct filter text in OIP. Not cool. Also the Altman R40 3 cir., 7.5' strip is built in reverse order for numbering. Screen Recording 2023-02-20 at 11.03.24 AM.mov yay Mondays
  7. In the sense that every time you have an unwieldy AutoCad file, passing it through Vectorworks reliably creates a smaller, nimbler file.
  8. @gmm18—I'd love to hear more about your Clip Cube sectional workflow. I am not enjoying the slowness of the Section Cut tool nor how much visual annotating I end up doing.
  9. "Layers" and "Sheets" are all I need for clarity
  10. I'm just surprised and happy to hear the round trip thru VWX as the converter actually produced a more usable file! Have you found that to be repeatable?
  11. Don't recall seeing so many graphics issues in 2023 These issues really mess with my workflow. 1086798060_ScreenRecording2023-02-08at12_34_18PM.mov
  12. mjm

    SLLOOWWW

    Seeing very similar VWX slowdowns here. More MBP restarts per day than ever before. Super duper irritating.
  13. MBP M1 Max 32GB Unified Ram. Freshly restarted VWX. Takes about a minute to work thru all the geometry passes, then the render happens quite quickly.
  14. with safari mail, etc in background
  15. Welcome to My Monday Morning Blues: Ouch What exactly were you doing to occasion these series of crashes this morning you ask? Welp, I was cutting and pasting a small number of 2D/3D symbols and attempting to paste them elsewhere, appx -100' from current location. Internal origin is 0,0. Edit: Ok, so: the items to be moved were on a couple different labels. I put em all on same label, no cut/paste, just Shift+Moved to new locale on layer. So far so good. Cmd+Save & immediate Crash Monster Redux. & even deeper than the ouch is the lack of productivity
  16. . OK, just checked the website you mentioned and saw both items rendered above in IRL video from th showreel. Pretty dang cool.
  17. @Kevin K I'd love to see the result without the entourage glow. Also: golly, a lovely construction and render!
  18. Just now posted on my current hourly crashes. Also, of course , on deadline
  19. Happy Sunday😬 Every hour, on the hour (nearly)… In this case these appear to be caused by editing Spotlight beams (shutters, pan/tilt) or, moving Spotlight fixtures. At least I'm getting regular coffee breaks, lolnot
  20. I find this kind of thing seems to happen at the most painfully inopportune moments.
  21. @Kevin K—Sweet. Love me some handy glow texture. Also thanks for the tip on HDRI intensity.
×
×
  • Create New...