Announcement

Collapse
No announcement yet.

Override Function for External Reference Material Not Working Properly

Collapse
This topic has been answered.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Override Function for External Reference Material Not Working Properly

    "I’m using a referenced object in 3ds Max, and I’ve applied an external reference material to it. I modified the override material in the reference, and when I previewed it using V-Ray IPR, it showed the updated material. However, during the final render, the override material didn’t apply, and it used the original external reference material instead. What could be causing this issue, and how can I properly use the override function with external reference materials?"
  • Answer selected by hermit.crab at 19-09-2024, 12:52 AM.

    Thanks for clarifying. It turns out we already have this issue logged (internal bug-tracker id: VMAX-8420). The current workaround is to render via Standalone (Main toolbar > V-Ray > .vrscene exporter > Export and Render) instead. Otherwise, I'll mention this to the project manager.
    Last edited by hermit.crab; 19-09-2024, 12:50 AM.

    Comment


    • #2
      Can you be more specific? How are you doing the referencing? Through the .vrscene snippet?
      Aleksandar Hadzhiev | chaos.com
      Chaos Support Representative | contact us

      Comment


      • #3
        Originally posted by hermit.crab View Post
        Can you be more specific? How are you doing the referencing? Through the .vrscene snippet?
        I am using the built-in reference object feature in 3ds Max.
        Attached Files

        Comment


        • #4
          Thanks for clarifying. It turns out we already have this issue logged (internal bug-tracker id: VMAX-8420). The current workaround is to render via Standalone (Main toolbar > V-Ray > .vrscene exporter > Export and Render) instead. Otherwise, I'll mention this to the project manager.
          Last edited by hermit.crab; 19-09-2024, 12:50 AM.
          Aleksandar Hadzhiev | chaos.com
          Chaos Support Representative | contact us

          Comment


          • #5
            Originally posted by hermit.crab View Post
            Thanks for clarifying. It turns out we already have this issue logged (internal bug-tracker id: VMAX-8420). The current workaround is to render via Standalone (Main toolbar > V-Ray > .vrscene exporter > Export and Render) instead. Otherwise, I'll mention this to the project manager.
            Thank you for your reply. I look forward to resolving this issue soon, as reference objects are a crucial part of my workflow.

            Comment


            • #6
              Another workaround may be to export .vrscenes from the reference scenes and use VRayVRMatMtl instead. Basically, analogical to the xRefs, but with .vrscenes.​
              Aleksandar Hadzhiev | chaos.com
              Chaos Support Representative | contact us

              Comment

              Working...
              X