Announcement

Collapse
No announcement yet.

V-Ray 5: Bring back origRGB

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

  • V-Ray 5: Bring back origRGB

    As the title says. Please bring back the origRGB layer, when lens effects or denoiser are used. The docs mention the origRGB in cases like these, but it will not get saved.

    The origRGB is useful for use together with seperate glare pass. Glare pass + origRGB = RGB_Color with glare.

    Right now, there is only a super hacky way of getting the RGB without glare: Activate lens effects, but hide it. This is totally counter-intuitive and feels like a solution that works by accident, and not by design.
    But even that "solution" is flawed: You will only get the RGB without glare, but no saved version with glare.
    This is different to V-Ray Next, where these elements were available: RGB_Color with Glare, origRGB without Glare, and separate Glare pass. This is exactly what we would need, because we built our workflow around this.


    Also, this is nowhere documented in the docs to V-Ray 5.
    https://www.behance.net/Oliver_Kossatz

  • #2
    +1 on what Oliver said
    Kind Regards,
    Morne

    Comment


    • #3
      1. In Next this was necessary, because the mechanism of calculating lens effects required an extra channel. Now it's not.
      2. IF we add it back, there will be another RE costing more memory and disk space (imagine 8K image * x 1000 frames). That means thousands of users having this negative effect on their machines.
      3. There are two ways to mix RGB and Glare now: RGB(with 100% Glare) - XX% Glare = whatever you want ; and the "hacky" way

      Having those 3 points above in mind - it seems that you can still do everything that was possible before and also get less memory/diskspace usage.
      If it was that easy, it would have already been done

      Peter Matanov
      Chaos

      Comment


      • #4
        Still: To get the RGB without lens effects, activating lens effects and then hiding it just does not feel right. If this is the recommended way of doing it, get this info into the docs, because this question will come up over and over again.
        https://www.behance.net/Oliver_Kossatz

        Comment


        • #5
          is using VRayLightSelect with nothing excluded an option?
          Marcin Piotrowski
          youtube

          Comment


          • #6
            Originally posted by piotrus3333 View Post
            is using VRayLightSelect with nothing excluded an option?
            I'm afraid not, GI from the Env slot and self illumination materials will not appear in the element, so it will only work if you use "legit" lights only.

            kosso_olli the docs are changed, thanks!
            If it was that easy, it would have already been done

            Peter Matanov
            Chaos

            Comment


            • #7
              Originally posted by slizer View Post
              1. In Next this was necessary, because the mechanism of calculating lens effects required an extra channel. Now it's not.
              2. IF we add it back, there will be another RE costing more memory and disk space (imagine 8K image * x 1000 frames). That means thousands of users having this negative effect on their machines.
              3. There are two ways to mix RGB and Glare now: RGB(with 100% Glare) - XX% Glare = whatever you want ; and the "hacky" way

              Having those 3 points above in mind - it seems that you can still do everything that was possible before and also get less memory/diskspace usage.
              Understand this thinking, but does it need to be a yes/no principle? Is there a way to add the option to save as an extra RE if wanted by the user? I guess how the denoiser setting works in the RE tab ( so that you have the extra info to use the vdenoise tool). So a check box under lens effects to save separate rgb with glare. Its pretty much how we do it manually now for stills so I'm assuming it can be programmed.
              Last edited by dean_dmoo; 29-08-2021, 01:42 AM.

              Comment

              Working...
              X