Announcement

Collapse
No announcement yet.

next - raw channels wrong exposure value?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • next - raw channels wrong exposure value?

    Not entirely sure if this is a bug, but something we are trying to work around right now. By default, we render to 16bit exr's and save out a bunch of render channels, including lots of the raw passes. We have noticed in Next that the channels are coming in with the wrong exposure value and are across the board super white. That is not to say they are different - when clocked down to about -6 Ev in photoshop, they match up with what was rendered in 3.6. My question is: is this by design? I like having 16b channels as they give a bit more lateral movement to adjust things, however, having to manually adjust all raw channels in 32bit mode, save, and place into our 16b working pshop docs is a bit of a pain. I'm going to test other file formats and bit depths, but wanted to make a note of this before I forgot.

    Thanks all

  • #2
    update - its the denoiser. trying to try variations now, but the denoiser is the culprit. will update with my journey


    updated2 - ehh, no. its one of the other render channels I have selected. Still trying to figure out which....
    Last edited by delineator; 29-03-2019, 01:26 PM.

    Comment


    • #3
      Well, as far as I can tell, this just relates to models that are being upgraded from vray 3.6. Once I reset the render settings and removed existing render channels, and reloaded that info, I THINK it sorted the issue. We are going to test a bit more internally, though I'd be curious if anyone else has run across this problem.

      Comment


      • #4
        Hello,
        The way render elements are created has been modified in V-Ray Next. I think we've caught all discrepancies already, but if there are others left, we would like to investigate further.
        Could you please provide some additional info?
        • Which engine did you use to produce the render channels - CPU or GPU?
        • Does the beauty pass remain the same despite the difference in some channels' output?
        • Which channels are affected?
        • What is your workflow (step-by-step) when importing the channels' output into PS.
        Kind regards,
        Peter
        Peter Chaushev
        V-Ray for SketchUp | V-Ray for Rhino | Product Owner
        www.chaos.com

        Comment


        • #5
          Yeah, I saw that bit on the 3ds Max side, which gave me the idea to start eliminating denoiser and other channels. The one file I had the issue on stopped giving me issues when I reset the channels and render settings, so that one I think is OK for now.

          CPU render. Beauty pass is fine, it seems to be mostly/only the raw channels (in my case the raw total light was the one I was most focused on). For our workflow, we save the output as 16bit exr's from vray. We have a premade PSB template that is 16bits RGB that we open first, and then import the channels as linked smart objects (hold down alt and drag file in). We're going to be rendering quite a bit more this week so I'll update when we run into a new issue BUT for now we are resetting the render channels and render settings and loading those fresh and that seems to have solved the issue.

          Comment


          • #6
            Thank you for your reply! We will look into this further.

            Kind regards,
            Peter
            Peter Chaushev
            V-Ray for SketchUp | V-Ray for Rhino | Product Owner
            www.chaos.com

            Comment

            Working...
            X