Announcement

Collapse
No announcement yet.

Possible VrayBitmap bug in Compact Material Editor

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

  • Possible VrayBitmap bug in Compact Material Editor

    When editing and browsing VRayBitmaps in a VRayMtl in the Compact ME (using the "Go forward to sibling" button), the displayed values in the "RGB color space" & "Time" rollouts carry over from one VRayBitmap to the next.

    To reproduce:
    Assign a new VRayBitmap in the diffuse slot, leaving its "RGB color space" as "Default"
    Click "Go to parent".
    Assign a new VRayBitmap in any other slot, change its "RGB color space" to "Raw".
    Click the "Go forward to sibling" button to view the map in the diffuse slot and you will notice its "RGB color space" is now shown as "Raw".
    However this just appears to be a visual bug, as if you click "Go to parent" and then back into the VRayBitmap in the diffuse slot, you will see its "RGB color space" is still "Default", which is as expected.

    The above behaviour does not seem to happen with the Slate ME.

    I'm working through converting our pipeline to ACES and it confused me for a while there!

    Cheers
    Olly
    Set V-Ray class properties en masse with the VMC script
    Follow me for script updates: @ollyspolys

  • #2
    We'll check what can be done on our side.
    If it was that easy, it would have already been done

    Peter Matanov
    Chaos

    Comment


    • #3
      Thank you Peter.

      Just to confirm the same behaviour also happens when changing values from the "Time" rollout and then clicking "Go forward to sibling"...
      Set V-Ray class properties en masse with the VMC script
      Follow me for script updates: @ollyspolys

      Comment


      • #4
        With a little luck it will be fixed for the next hotfix.
        If it was that easy, it would have already been done

        Peter Matanov
        Chaos

        Comment

        Working...
        X