Announcement

Collapse
No announcement yet.

MultiSubTex and random node handle doesn't persist

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

  • MultiSubTex and random node handle doesn't persist

    This is a getting pretty nitty gritty, but we had an issue where the "random by node handle" ends up actually randomizes the multisubtex render to render. I went back and checked previous projects where I've used this and can confirm that although I didn't notice it at the time, it indeed does re-randomize at time of rendering (we didn't notice it because I was using it to build up custom masonry walls at the time).

    According to the docs, I had assumed the identity would persist render to render (https://docs.chaosgroup.com/display/...P/MultiSub+Tex) but perhaps I should have been using one of the other random parameters?

    Note:
    The elements the material was applied to in all cases were components within a group that sat at the very top of the model hierarchy (just group parent, then component children, nothing else above that). Nothing was changed or edited regarding the multisubtex material or the geometry it was applied to. Rendering process was our typical vrscene and submission via Deadline (perhaps the SU to vrscene process re-randomizes?)

    Anyways, if we're doing anything wrong or if I misinterpreted the doc, definitely let me know. For what's its worth, we're using the multisubtex to help out with some fairly complex situations (full on custom patterned masonry wall built up in 3d, massive amounts of lights in huge urban context, etc) and its making my life quite a bit easier

  • #2
    Hello,

    This appears to occur when you add/remove object entities in the model.
    When it comes to editing the MultiSub tex, randomization is being performed when additional entries in the texture list are added/removed. Switching between different ID origins, on the other hand, does not cause IDs to be randomized again.

    Our dev team is looking into enhancing the MultiSub tex functionality and making it more predictable. This planned optimization will be included in a future update, but I cannot give any ETA at the moment.

    Let me know if you have any further questions.

    Kind regards,
    Peter Chaushev
    Peter Chaushev
    V-Ray for SketchUp | V-Ray for Rhino | Product Owner
    www.chaos.com

    Comment


    • #3
      Interesting, thanks for the follow up. We intend on using it in a new massive development for some nighttime aerials, so I'll try and be more careful with adding/removing geometry and see how that goes. In the end, its not a huge deal how we are using it right now, but I could imagine persistence of any kind would be helpful to most.

      thanks

      Comment

      Working...
      X