VRay distancetex and tyflow

Hi,

I have a problem with distance tex. In one of my scene I want to use distance tex on a plane and set object as tymesher. In my test scene it works but in my final scene max give me a note its a circular reference and I cant do that. But dont know where is a problem, I do exactly what I did in test scene. Put one material on tymesher and another on a plane with distancetex on it. Can you help me, should I send a scene for that?

Thank you.

Hello,

It would be helpful if you could send a scene to take a closer look. You can send it over to philip.shounev@chaosgroup.com

Best,
Philip

I created a similar setup just a week or so ago and it works fine - is your tyflow object meshing a cache or a flow? Is the distance tex referencing the cache/flow or the mesher?
The flows themselves should be completely disabled - I have taken to keeping the simulation in a separate scene to the cache loader/mesher, keeps things clean.

A total guess, but it sounds to me like you have an active flow that is referencing the plane (maybe for a collision), which the material of is trying to reference a mesher which references the flow. They dont actually affect each other but it’s still a circular reference.

When I use tyCache and mesher tyCache, its working. When I mesher tyFlow object, its not working. But its weird, because other scene working ok. I will send those scenes to Chaos Group. Thank you.

Scenes sent to philip.shounev@chaosgroup.com.
Thank you.

Hi again,

The reason for getting that circular reference is because the surface object is added as a birth surface event for TyFlow. That’s why a dependency loop is created and TyFlow can’t measure the distance from “itself”. A simple solution would be if you copy the surface geometry and hide the original one.Thus the original (hidden) geometry would be used by TyFlow as a birth surface and the copied one - by VRayDistanceTex.

Best,
Philip

Oh, ok. So the problem is that tyflow has birth on a same plane as distancetex? Even when distancetex object is mesher, which is different object then tyflow itself?

Ok, I will keep that in mind, thank you.

That is expected - always cache your tyflow for final render. Dont render the tyflow objects directly.

Sure, but in one scene it worked, so this is why I was confused a little bit.

Did your test scene include the geometry reference in the tyflow graph?
Presumably you’d have skipped that when making a rough test scene for a material.

Sure, I know that too now. I dont know it has any affect when it nothing to do with distancetex. But now I know, so its ok.