Announcement

Collapse
No announcement yet.

RT vs Production Renderer Bug

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

  • RT vs Production Renderer Bug

    If we have the production renderer set to Irrandiance map and change to RT, the result in VFB is wrong.
    If we have the production renderer set to brute force and then change to RT the VFB is correct.
    When we render with the full production rendered (using either irrandiance or brute force) this matches the RT mode ONLY when the production renderer is set to brute force.
    I hope that makes sense please see attached.
    I think this is a bug, I didnt think that selecting different engines in the production renderer affected the RT renderer, but it seems to be happening here.

    Last edited by bob-cat; 20-09-2017, 12:58 AM.

  • #2
    Hello,

    If you mean ActiveShade RT - it uses the GI settings from the production renderer. Also it supports Irradiance Map only from file.
    So if you've set IrMap as your primary GI engine and start ActiveShade - it will fallback to Brute Force GI.

    Best regards,
    Yavor
    Yavor Rubenov
    V-Ray for 3ds Max developer

    Comment


    • #3
      Thanks Yavor,


      Yes I mean Activeshade RT, I didnt know it defaults back to brute force.
      I will have a look at it, and it could be we have a from file map in the IR slot.

      Comment

      Working...
      X