Jump to content

mjm

Member
  • Posts

    1,278
  • Joined

  • Last visited

Posts posted by mjm

  1. I have to say that I find it a mood, when I can render caustics in several render modes except Redshift, not that Redshift can't do caustics, that feature just seems to be locked away from us, which stirs the same internal reaction like the BMW seat warmer nonsense. Closest I have come to get to where I want is to render the redshift, then render only the caustics lighting in an appropriate render mode (for me, preview spotlight gets me there), then composite them in PS. It's a bit fiddly, getting the right lighting intensities…

    Oy1578240483_Screenshot2022-11-28at1_18_19PM.thumb.png.25deea522b8834578c30b8102a8332aa.png1397251011_Screenshot2022-11-28at1_18_11PM.thumb.png.e865b1f8a5ca334e1e6960a0d342134d.png749449007_Screenshot2022-11-28at1_18_26PM.thumb.png.eb835b74d17f9c6da343d2eb3e4fd6dd.png 

  2. 3 hours ago, Bertadesign said:

    @AlanW I'd love what you've done with the ribbon there. I'm trying to build the same at the moment, a ribbon around a cube with a bow at the top. But I cannot do it from the explanation alone in this thread. Have you got a more detailed step by step explanantion on how this can be achieved. I'm using VW 2022. Thank you!

    Hi @Bertadesign: did you download the file @AlanW attached to his comment above? That might be informational.

  3. 5 hours ago, Tom W. said:

    @mjm I agree. The few times I've used them the results were great in the end but I didn't feel entirely in control of the operation or confident of the outcome. Also a couple of times the decal has disappeared after I'd set it up then I'd have to shake things around to try + coax it to reappear. The fact you're having to use a render style as well each time to see the thing slows the process down further. Actually @MGuilfoile that's another thing to bear in mind: Decals don't work in OpenGL/Shaded...

    @Tom W. wow yes totally forgot about that render style limitation

  4. On 11/14/2022 at 12:46 PM, Tom W. said:

    I've only used Decals a handful of times but every occasion it took a bit of searching to find them on the object (offset H + V in OIP)... It looked like nothing had happened but the decal was way off the side of the object + needed reeling in...

    Decals seem pretty counter-intuitive as-built to me. User wise, Want to select a resource and click on a face to place it, then drag/scale/etc till done. Applying a decal and then hunting for it hasn't made sense to me yet, but it's just as likely I'm missing whatever crucial step in the decal workflow…

     

  5. 2 hours ago, JuanP said:

    @mjm While we get to the bottom of this issue - try the following:

    and please let me know if that fixes the issue.

     

    Thanks

    @JuanP @Dave Donley; gents, thanks as ever for your attention to this matter. I have executed the steps as outlined in JimW's video and appear to achieved success. 2x in a row VWX has not crashed when editing the Page Setup pane. Thank you both for your input.

     

    • Like 3
    • Love 1
  6. 5 hours ago, cberg said:

    Thanks Fabrica.  So at least I don't have to search around the file for corrupted objects or something.  Seems to have fixed for now. 

    yeah saving that time and energy is worth the re-start every time.

    I've come to learn that the 🔨 way

    • Like 1
  7. 1 hour ago, beanus said:

    VW just totally crashed while trying to zoom out in a sheet layer, why is it that whenever a new version of VW comes out there are so many bugs, I'm sick of being one of the many guinea pigs that are used to test new versions of VW which none of us have signed up for.

    It is often a painful experience to come to grips with how fragile VWX tends to be in its earliest iterations -.0, .1, etc. I often feel used.

    Having said that, in another thread I enthusiastically offered whatever support I could to help move along a particular facet of the app which is crucial to my workflow.

    Aaand, having said ^that, I'd prefer to participate in a true beta, rather than sending in complaints after the official versions come out.

     

  8. 14 minutes ago, Dave Donley said:

    Hello:

     

    We may be able to enable receive shadows for lit fog in Shaded, but it is not certain.  This was implemented but then disabled due to crashing on some computers.  The team will revisit this limitation.  We totally understand the need for it, so that your renderings look correct.

     

    @Dave Donley—how can I help in this process? It's of vital interest to me

  9. 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. 

  10. 24 minutes ago, Mark Aceto said:

     

    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.

    @Mark Aceto—woo-eee, thanks man!

  11. 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.

  12. @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.

  13. 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
  14. 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.

     

×
×
  • Create New...