Jump to content

Shaded Render fail


mjm

Recommended Posts

Here's something literally stopping me from delivering the goods TODAY. Happened last night out of the blue.

Building a sheet for communicating Lighting Presets (moving lights recorded in a focus position, + color + gobo + etc) as one does, for one's previz operator. So far, so good. Loving the unlimited Shaded Render beams, wows my workflow speeded up because of that, ya…woops.

So: here's the onscreen render:488322226_Screenshot2022-11-08at6_42_19AM.thumb.png.e358333f433b98684ff69fe7076af32a.png

Yay, right? OK. so excited, I exported, published, printed to pdf, and all returned this:

441767527_Screenshot2022-11-08at6_48_46AM.thumb.png.e54f27c661895af47be34c83d2a9933d.png

 

woops. This is stopping me from making my deadlines and pretty much super bad for my mental health. This task should has reached the braindead-rinse-and-repeat cycle of developing the previz shots, exporting to PDF. This ruined dinner & a movie last night and apparently it's gonna continue to be all an kinds if fun VWX-day here.

Here are the render setting for each of those views:

1126343373_Screenshot2022-11-08at6_52_25AM.thumb.png.c2b9ff9040b33e5dcad1c55cb35d7243.png1277589927_Screenshot2022-11-08at6_52_04AM.thumb.png.3b4c69a836310228201fdd6d60d00ed9.png1238347602_Screenshot2022-11-08at6_51_49AM.thumb.png.a34aa68aa291d8f7135e9837aeabfd50.png

 

Same background used for all three as well.

 

Ironically, the speed and overall readability of the 2023 Shaded Render offers so much potential to change my life for the better because it's so much faster than the other options.

 

 

Edited by mjm
spelling
Link to comment

I had a Redhshift render solid black last night.

 

Anyway, for the sake of the deadline, and your sanity, could you juice the SLVPs to 300dpi (or even 150) and use screenshots? Obviously not ideal but you could hand off to the previz programmer, and carry on living your life.

 

Or do what my buddy does which absolutely triggers me: import the same screenshots and then publish… It’s dirty but it gets the job done.

 

Also we need to add the hug emoji the community forum support group.

Link to comment
5 minutes ago, Mark Aceto said:

I had a Redhshift render solid black last night.

 

Anyway, for the sake of the deadline, and your sanity, could you juice the SLVPs to 300dpi (or even 150) and use screenshots? Obviously not ideal but you could hand off to the previz programmer, and carry on living your life.

 

Or do what my buddy does which absolutely triggers me: import the same screenshots and then publish… It’s dirty but it gets the job done.

 

Also we need to add the hug emoji the community forum support group.

Thanks for the hug man, honestly needed that. And yes I have already capitulated to the screenshot idea, in order to GTD.

Triggered, LOL. yup.

Link to comment
16 minutes ago, mjm said:

@Mark Aceto, dang thanks for that. I am sure you can imagine how thrilling it is to have such potentially rapid turnaround on these kinds of things with the revision to Shaded Render, so to have it fail mid-stroke…

 

Literally going through the same thing right now on my gig although its more for client viz than previz.

 

@Dave Donleyany suggestions for @mjm?

Link to comment
9 minutes ago, Andy Broomell said:

Out of curiosity, are the viewports re-rendering during the process of exporting the PDF?

 

I tend to uncheck this box to avoid re-rendering (assuming I've already made sure my viewports 'look' up to date, even if they're technically not):

 

85519284_ScreenShot2022-11-08at8_49_56AM.thumb.png.4ebf3a39bc35572805d1fdab1c84ad02.png

 

Regardless, this bug shouldn't be happening, but curious if this changes anything.

@Andy Broomell: Thanks man, had not thought of that.

& so, just tested your thesis. 

  • Opened file
    • All three render views already "rendered" 
  • Clicked 'Export to…PDF'
  • UNclick Update visible out of date viewports prior to exporting
  • Click render

Result: Same as before.

 

Link to comment

I assume when you say "click render" you mean "click export."

 

But regardless, that's very strange; it means that the process of exporting the PDF is not delivering what's already on the page, because if you uncheck the "Update visible out-of-date viewports" checkbox, then no rendering processes should happen as you save the PDF. It should save what's there.

 

Next thing I'd try is to see whether there's a difference between File > Export PDF, vs File > Publish, vs Printing to PDF driver if you have that on your machine.

 

At the end of they day I'd maybe resort to Mark's suggestion of screengrabs (or maybe File > Export > Export Image File > Each page as separate page?)

 

Good luck!

  • Like 1
Link to comment
13 minutes ago, Andy Broomell said:

I assume when you say "click render" you mean "click export."

 

But regardless, that's very strange; it means that the process of exporting the PDF is not delivering what's already on the page, because if you uncheck the "Update visible out-of-date viewports" checkbox, then no rendering processes should happen as you save the PDF. It should save what's there.

 

Next thing I'd try is to see whether there's a difference between File > Export PDF, vs File > Publish, vs Printing to PDF driver if you have that on your machine.

 

At the end of they day I'd maybe resort to Mark's suggestion of screengrabs (or maybe File > Export > Export Image File > Each page as separate page?)

 

Good luck!

Lol @Andy Broomell, yup,  did ALL you suggested above, no joy and your sense of the issue is the same as mine. I did get all three to print by copy/pasting the three viewports into a blank file & exported without updating. THAT worked. Of course you can imagine what happened when those three viewports were then updated.

  • Sad 1
Link to comment
  • Vectorworks, Inc Employee

I am able to get a rendered PDF out of that viewport if I uncheck "Project screen objects".  Perhaps there is a screen plane object that is covering the rendering here.  There is a black rectangle (layer plane) and if I delete it I get a good PDF.  That rectangle is layer plane though, it isn't a screen plane object.

 

 

  • Like 2
Link to comment

@Dave Donley: Huzzah Dave—that solved that problem for me, thank you very much. However: what black rectangle? The only black rectangle I know of in that file is on the Auditorium Layer, there for unwanted light leaks during render, as my actual building data is very slim. That rectangle is I think it's 6'9" below 0,0. It is definitely on the 3D plane.

Also: it appears Shaded Render on DL does not have any 'Project Screen Objects' options, so the issue does not seem to be visible there.

And, of course changing that rect to an extrude seems to obviate the issue entirely.

Link to comment
1 hour ago, mjm said:

Lol @Andy Broomell, yup,  did ALL you suggested above, no joy and your sense of the issue is the same as mine. I did get all three to print by copy/pasting the three viewports into a blank file & exported without updating. THAT worked. Of course you can imagine what happened when those three viewports were then updated.


As much as a I hate to say this, you can reference the screenshots. As long as you rename them with the same name (replacing the old one and the same location) your drawing will auto import. Gotta love Vectorworkflows.

  • Like 1
Link to comment
34 minutes ago, Mark Aceto said:


In the SLVP OIP

yep — the point being that rendering in DL does not seem to offer that PSO option, so this issue never raised it's ugly head while actually creating the looks in Shaded on DL, so no warning beforehand, if you will.

Link to comment
57 minutes ago, mjm said:

2063320830_Screenshot2022-11-08at11_35_32AM.thumb.png.5ce0da2fb48ca9a9bffbbeafbb2c5e4f.pngAlright; I seem to be back on track, I want to thank all y'all (esp looking @Dave Donley) for your assistance and support.

Back to having fun again, doing what I do!

 

Love the data tags. It looks like they're mirrored on the right side. You can uncheck "mirror something something flippity flew" in the data tag settings to not do that. Unless that's by design, in which case, keep it as is.

Link to comment
2 hours ago, EAlexander said:

Looking cool in here!

Thanks man. Shaded has come a long way in '23. That specifically was why I've been willing to go thru all the pain of the dot zero release this year. For the first time I can move with so much more speed in generating reasonable visual ideas. 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...