Announcement

Collapse
No announcement yet.

VRay color - issue

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

  • VRay color - issue

    Hello everyone,


    I have come across an issue that came to my attention after my resent update to Vray Next 3.1 (4.30.01 build 00001).

    To use RGB colours in 3ds max I use the "Vray color" node.
    I input the colors using the "Color Selector" that pops up when you double click the color slot in the "Vray color".

    I use to add an RGB colour just like they are in photoshop, like this: 128, 128, 128 for mid grey.
    Then I changed the "color gamma" in the "Vray color" to "2,2". This what the colour was previewed the right way.

    Now after I updated the process is no longer working that way.

    My issue is that whenever I put my rgb color values into the "Color Selector" it gets translated in the "Vray color" node and as a result the primary values are now to bright as is the preview colour.

    Is there a fix to this?

    I have also red this tread:
    https://forums.chaosgroup.com/forum/...lor-fix-please
    But I am not sure my issue is the same.

    I have attached an image to illustrate my issue.


    Any help will appreciated!

  • #2
    Could you try the solution from the following post and see if that fixes the issue?
    https://forums.chaosgroup.com/forum/...78#post1032378
    Aleksandar Hadzhiev | chaos.com
    Chaos Support Representative | contact us

    Comment


    • #3
      Hello Aleksandar,


      Thank you for your reply.
      This is the fix to my problem. The Vray color now behaves as it should!

      But this fix only helps during one max session. Every time you restart max the VRay Color is back to the wrong settings and functioning.

      Can I do something to fix this? To make the fix you suggested stick?

      "To return the value to its defaults, type these lines in the MaxScript listener:"
      m=VRayColor()
      m.gamma_correction=0


      Some of my colleagues have this issue as well, but others don't.
      What is the reason that this setting can get disrupted?

      Comment


      • #4
        I suppose you're opening scenes saved with older versions of V-Ray in which your VRayColor textures' gamma correction options are active. Saving the scene after running the script commands should save the newly set options. Or does this happen on a fresh scene?
        Aleksandar Hadzhiev | chaos.com
        Chaos Support Representative | contact us

        Comment


        • #5
          1. I open a new scene

          2. open the slate editor

          3. create a new Vray color

          5. assign a new rgb color via the color selector

          6. the Vray color is wrong

          7. I run your script

          8. assign a new rgb color via the color selector

          9. the Vray color is now right

          10. save the scene

          11. close max

          12. open max

          13. open previously saved (and fixed) scene.

          14. open the slate editor again

          15. assign a new rgb color via the color selector

          16. the (previously fixed) Vray color is wrong again.



          What should I be doing?

          Comment


          • #6
            Is there a way to make the above mentioned fix stick, when you restart max?

            Comment


            • #7
              Could you try renaming your ENU folder (C:\Users\<username>\AppData\Local\Autodesk\3dsMax \20XX - 64bit)? This would reset your 3ds Max user preference settings back to default (Max will create a new ENU folder; we rename the old one to save the preferences). Also, make sure you start 3ds max vanilla and not with any company launchers or similar applications. See if that works out and report back.
              Aleksandar Hadzhiev | chaos.com
              Chaos Support Representative | contact us

              Comment


              • #8
                Thank you sir, That solved the issue! To bad that I now have to redo al my preferences en toolbar items. But that is something that I can manage

                This issue is now solved!

                Comment

                Working...