mjm

Another thought on this, after rendering locally a redshift viewport. The render took 29:08. Not too bad for the relative complexity of the scene what with 75+ fixtures turned on with a fog background for the haze. No other apps were open, I even closed safari! OK so; ready to get back to it and then I checked Activity Monitor after the render finished (I never run VWX anymore without this also running); VWX still holding onto 21+GB of memory. So now in order *safely continue to work I need to restart the app. Then reopen the file, etc. *the battle cry of the crashing Vectorworker: "Restart!" or even "Reboot!".

Watch closely; you'll see the truss conversion take place, whilst simultaneously deleting some D60s from that very position, & even cooler, it takes out one of the Seladors on an unrelated position just DS of it, which in it's OIP shows it belonging to the correct unrelated HP. edit: several tries later, success. That time I made sure the layer the truss was onwas activated before running convert command Screen Recording 2022-10-26 at 11.14.26 AM.mov

Perfect.

@inikolova It's high season for me now and I have projects through February passing across my VWX screen every day, with varying needs, but many of them multi viewport SL renders. Waiting for a render to render stops all other VWX forward progress, so the hope is to be able get past the scratch render stage on the desk machine and move the 'for comment' or final renders to the cloud, freeing the desk-based machine to work on the next project or the next act on the same project. Does that make sense? Asking fr a friend.

As the title says. It's happened multiple times today, but not every time. Only change from yesterday is the Ventura install last night. Does not seem to matter whether the MBP M1 has been rebooted or not. Certainly VWX 2023 is, as it crashes to the desktop, so

Thanks for jumping in here@inikolova. I'm gonna suggest where my hopes were in the cloud render regard. Much of the work I do is for multi-work evenings, often 3 different works, generally with little or no overlap. Piece #1 Sheet Layer/s ready for cloud render & sendto Cloud… work on Piece #2, till SLs are ready to Cloud render & sendto Cloud… work on Piece #3, till SLs are ready to Cloud render & sendto Cloud… Grab Piece #1 Cloud Render, markup for changes, etc. I have to say that previewing renders with low DPI only gets one so far, at some point proofing becomes the task, where the fully rendered item is required. And using any render type other than Redshift to build and edit the actual render when Redshift is the final output goal is completely self-defeating.

ditto

@Pat Stanford thanks, think I got it sorted enough to get things done. I deleted the ten corrupted symbols, copied and pasted from the nearest available group and back at work I was. The file was completely stable for the subsequent 3 hours.

There's a machine restart before each crash. My guess is something corrupted the entire bottom row of Mini-Bs, which were acting fine yesterday. & so, between the three crashes and the documenting of those issues = approx 15 mins. Zero productivity Elevated stress No fun YACM.mov

Hello @Emil Kolev!

I have not been able to import a single Sketchup file downloaded today from 3D warehouse into VWX 2023. No problems in 2022. EDIT: Idle curiosity I tried drag n drop, et voila! it worked! Ok, well that was so exciting I then tried the File: Import… Sketchup menu choice again. Cool. I attached a screen cap after trying this several times, several different SKP files. Old 2012 SKP files perform flawlessly. 2019 SKP & on perform as shown. So: I now have both versions of VWX running to shuttle SKP files over to 2023. SKP issue.m4v

OUCH, esp the last sentence, which is a feeling I have often with VWX.

Ouch, that was a little embarrassing to see the answer dead center in my eyeline. Good to hear how the crops can be useful. I'm just glad I now understand where to look / fix for that issue. I do not understand how VW comes up with the size and location of the crop however. Love the idea of an easy keymap.

Anyone understand why the green crop box is still a thing in 2023? Also; in this iteration it seems to self-define it's crop areas. EDIT: Hoo boy I do now. Looks like I inadvertently clicked the Add reference Crop Object…

Very clear & succinct, thanks @Kevin K

@Josh-gsy I will tell you the @JBenghiat's Savvy Sequencer will probably do exactly what you want but far better than you could have imagined. Check out it's window; so many possibilities! I use this so frequently it's earned a spot & a custom keyboard command on every workspace I use. Worth every penny. May I also say this tool directly addresses the need for starting character other than 1.

Always great to be refreshed on that document @TomWhiteLight, thanks

@bcd thanks for that. I have steered away from subdivision for fears it'd take too long to matter even halfway. Your result above is provoking me to give the tool a another go.

Thank you @JBenghiat. Attached is a screen shot of the Spotlight Preferences window showing the Instrument Type & Device Type checked. Not spending much time in this window before, I note the Accessory column is checked on almost every parameter.

Thanks all. I selected via SL find/modify all the fixtures w/ device type static accessory & changed device type to light, thinking I can then just replace them thru the PIO but as you can see they remain a static accessory to VWX. So, deleted all those fixtures & replaced by hand. All these symbols came straight from the RB ETC folder. I am quite stymied, as this has been an irregular occurrence, but seems to happen way too often.

I can't believe this is still a thing. And choosing "Light" as an option in device type keeps the instrument type as C Clamp. Not enjoying my CAD practice today, again.

Here's a quick thing from a very fast model w/ Image-based texture to create a sense of rock walls. In practice, It'd be some armature with chunks of styrofoam & massive ants spray foam and carving and texturing and painting

Not thinking this is VWX's strong suite.Assuming you have some liberty in your recreations, I'd be looking to textures to solve this problem in the short run.

"• Spotlights’ brightness renders the same with either Renderworks or Redshift render settings" Ohboy can't wait to test this

@setdesigner @jcogdell Thank you both. Yes, I finally found it under "All Menus", not under the "Import/Export".