Announcement

Collapse
No announcement yet.

3ds max 2017 + vray 3.40.02 = instance bug?

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

  • 3ds max 2017 + vray 3.40.02 = instance bug?

    I just upgraded to 3ds max 2017 (SP2) and vray 3.40.02.

    I created some instanced teapots. Rendered them. Changed the number of segments and suddenly they looked damaged.
    They looked the same when rendering. Screenshot attached.
    Click image for larger version

Name:	3dsmax2017_instances.JPG
Views:	1
Size:	99.9 KB
ID:	885256

    It's the same with other instanced objects.

    Is there a solution for this bug?

    Thanks in advance.

    Regards
    Olaf Bendfeldt
    3D-Artist
    dimension3+

  • #2
    It's a problem of the 3d platform (3DS Max).
    There are more users complaining about the same thing here:
    http://forums.chaosgroup.com/showthr...=2017+segments
    Tashko Zashev | chaos.com
    Chaos Support Representative | contact us

    Comment


    • #3
      Saving and reloading the scene should make the problem go away. I'm still not sure what causes it.

      Best regards,
      Vlado
      I only act like I know everything, Rogers.

      Comment


      • #4
        Thanks for your reply!

        I tested the same thing with the classic scanline renderer and the new ART renderer and everything is OK. The problem does only occur when rendering with VRAY. Yes, after saving and reloading all is normal but it reappears every time I create a new object hit render and change the segments.

        Have a nice weekend!

        Regards
        Olaf Bendfeldt
        3D-Artist
        dimension3+

        Comment


        • #5
          Yes, I'm aware of that. I haven't figured out what particular change in 3ds Max causes it or how to fix it yet.

          Best regards,
          Vlado
          I only act like I know everything, Rogers.

          Comment

          Working...
          X