Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by mjm

  1. @JBenghiatHave no shame whatsoever. Savvy Sequencer is hands-down the single best most used plugin I have ever purchased.
  2. Here's the thing: I spent, what? probably ten minutes easy, trying figure out why a glow texture suddenly stopped glowing…was it something I did? Backtrack, fiddle, fix, all to no joy, no warning. Okay start the app, there's another two-ish minutes. Yup, first render right upon opening, there're my glow textures, back again. This kind of stuff (and other rando issues, this forum full of the sightings) happens all the time and sucks the very lifeblood (much less the joy) out of designing. I don't design to fight with software, I design to literally help someone achieve their dreams. And for this experience, for a professional product, I'm just not feeling the "ultimate software" experience. Not trying to bring all you hard-working VW folks down, because I believe that in the trenches y'all are working hard as heck, but hey - charging for the 'ultimate' and not delivering, feels plain wrong.
  3. pardon me for jumping-in here, but to me, your accounting software is equally as parasitic
  4. Neither the Stage Decks nor Spotlight Lighting Fixtures are symbols when placed with their respective tools, they're parametric objects, designed to be operated on with the OIP.
  5. @Dave Donley Wow, fast response Dave. Thanks so much. Uh, which version or both 2022 & 2023? I have to strip the file/s of client info first.
  6. So, after battling the Static Accessory gremlin for the past week, I finally have a printable 2022 file. I first publish it: see pdf v3a. Oops. Hadda try that a few times to make sure I wasn't hallucinating. Well then, I'll simply export the pdf…see pdf 3b. Sigh Oh, hey, export as EPSF! see pdf v3d. Victory. A hollow one however. You're asking about the page set up and printer dialogs, yes I checked em & I think the proof of that pudding is the almost excellent eps export. & I say almost because well, the EPSF converter does not respect transparency, I have added a screen shot of the sheet layer so the difference can be noted. I'm roughly guessing the whole printing debacle took 30 -45 minutes to -well solve wouldn't be true, nor would fix- work around the issue after trying so many other options. Oh, hey, this project has twenty eight publishable Sheet Layers. After rebooting, the issue seems to have subsided, so, only about 45 mins + this forum comment = time lost. 2022-10 OBT MSND+HUSH Light Plot v3a.pdf2022-10 OBT MSND+HUSH Light Plot v3b.pdf2022-10 OBT MSND+HUSH Light Plot v3d.pdf
  7. Huge happy news @Dave Donley. Looking forward to the fix.
  8. Just for fun, I started up both 2022 & 2023 with no files open, first screenshot Then opened the same file in each app, see second screen shot. Following that, I ran the same slightly modified redshift render on each. Oh my, some very interesting things occurred, first and foremost to me was the radical improvement in red shift render speed: 0:45 for 2023 & 1:26 for 2022. Mind you this was extremely unscientifically done, but good to see that particular result. Also ran this scenario several times, closing the apps and opening the same file each time. however, looking like every file brought forward to '23 will need every render re-tweaked, because the one does not look like the other… Memory-wise, it was interesting to watch 2023 immediately hit +17 GB max during the render. The final screenshot shows how much memory was apparently released.
  9. Try clicking the Simple 2D & Simple 3D options in the PIO, pretty far down the way, I remember correctly. Also, lol, I attempted to make a pleat of 0", no joy. Then I tried 0.0001. VWX 2023 has frozen. No skinny rainbow ball, nothing. Not even showing as "not responding" in th e Force Quit pane.
  10. FYI: No idea why that difference is so extreme…
  11. @designedAFI'm guessing you've restarted your machine at least once? Seems to be the universal panacea… On my first render pass on a recent 2022 file, the same modified Redshift Style was employed as in 2022. Render took slightly longer, used about the same overall amt of memory as before, tho this time instead of the task being split between Cineware and Vectorworks, it appears, as mentioned by @Dave Donley (I seem to recall) that it all takes place under the Vectorworks 2023 app. fifty Clay PAky Mini-Bs, eight VL 2600s and four Solaspot 2000 out of sight behind the prosc. I will say the redshift render in it's preview modality is faster & with better results than the Spotlight Styles in 2022 or 2023. I =basiclly haven't needed to turn on denoising in redshift in either 20922 or yet in 2023.
  12. @klinzeyYes, I'd already forgotten that. The prompt is much appreciated. Rendering a different project atm, but can't wait to dive in.
  13. @Pat StanfordThank you as ever for your input Pat. I don't however understand what you are driving at with "If you are trying to Publish multiple sheets all from design layers…" Each design layer uses the same page layout and size.There are three same-dimension SLs; two Portrait, one Landscape. The Portrait sheets get published to pdf as a landscape sheet, ie; the portrait-based layout appears vertically in a Landscape sheet. This does not happen in a new file where the SL layout appears to be respected. Wonder why that is… And, when I choose to create a new blank document (say in order to rebuild the file in a clean document) import my layers with layer objects, why do the Position Names change to what appears to be some default numbering system 1, 2, 3, 4 etc? I find this is reproducible across the first two existing files I try this import with, see screenshots attached. Created a new file, did the DL & SL + objects import, went through and renamed all positions & in happy (?) news, the new file does appear to publish sheets correctly, so I'm loosely guessing the originating file is corrupt in some way.
  14. Hi @MrTemplate—I guess the Autonumbering part, which is first, goes by too quickly. My apologies. The very first action which occurs is the cursor sliding frame R to the Spotlight Auto Numbering tool, the cursor clicks & if you watch closely, you will see the deeply incorrect numbering executed by that tool. That is followed by the menu choice of Savvy sequencer, etc.
  15. Why does SL Auto Numbering seem so uh iffy? AutoNumbering seems to fail regularly with multicell fixture numbering. I have attached a video demonstrating both the SL AutoNumber fail as well as the current workaround— Savvy Sequencer, developed by @JBenghiat. Screen Recording 2022-08-31 at 6.54.40 AM.mov
  16. @mhersland Pretty much think Nemetschek wants you to do this type of work in Vision…
  17. @Pat Stanford @JuanP Pat- thanks for the info above, which works perfectly for exporting a sheet. Unfortunately, publishing the same sheet/s results in Pages not respecting the P/L layout, ie; all pages published seem to be oriented only Landscape, no matter what the Sheet sized and layout is. I note there's no switch in the Publish pane to set the exact parameter you show, by the individual sheet, some may be Landscape, others may be Portrait. Having to go through and export each one individually is a carbuncle. To my recollection, this began after I got the MBP M1 and found no way to install or even locate DesignJet PPDs to set up a fake printer. I'd be thrilled if the issue here is that I am simply missing a tiny toggle somewhere. **couple more notes: A new file does not exhibit this behavior, it produces correctly both in publish mode and export mode, no matter how the design layer is set up. In that new file, the Export Range holds it's toggle on "Export the whole printable area as one page", and even when I change that toggle to"All Pages" in the Export PDF Settings pane, when I publish to PDF, all pages export correctly according to their SL layout dims. whereas in my working file, that value is not held. Super irritating.
  18. Same Question here. Been hand building strips for a while now with IES files but having to duplicate multiple sources to make something resembling RL output.
  19. @JBenghiatStellar. Thanks man.
  20. @JBenghiatSuper. Thanks ever so. Assuming I can do that to the symbol in current use
  21. @JBenghiat, @klinzey I added the MR-16 Altman Z-Strips to my plot today. Numbering issues there as well. Is it possible for me to somehow re-build the multicell fixtures myself so they number correctly?
  • Create New...