[HOU-2307] URGENT - vrayDirt, packed vs unpacked

[david.anastacio]

Hi, very sorry to push on to you another urgent bug, Gosho.Genchev.

We are having issues with the vrayDirt texture results. When used in combination with packed geometry the vrayDirt considers parts of a geometry that have a different path attribue a different object, so when using the "Consider same Object Only" each primitive with it's own path only sees itself, cool. But when unpacked this does not happen anymore, the paths seem to be ignored and all geo is now cosidered when calculating the dirt. This is extremly problematic because of texture baking, as the bake to texture requires the geometry to be unpacked (this should definitly be chaged), so now we have a a very different result on the baked maps.

Can you guys do something about this on the next days? If not please let me know as we need to take action on our side.

Example:



Best,
David.

[bdancer]

VRayDirt doesn't know anything about attributes.
It knows Node (V-Ray plugin representing an object).
When packed each packed primitive is a different Node; when unpacked - it's a single Node.
So, I'm not sure we have to "fix" anything...

[david.anastacio]

So, I'm not sure we have to "fix" anything...

hmmmm, there needs to be something fixed, if it's because VrayDirt knowing or not about attributes is irrelevant, then it's something else. The matter of the fact is, the result of the packed vs unpacked is different, and that cannot happen.
At this moment we have a HUGE asset in a show, client approved, and we cannot deliver it because the baking result does not match the renders, and this is a BIG problem.

As seen in my example, there was even a test scene attached, the unpacked geo was failing to make use of the "Consider same Object Only" option, so this needs to be fixed. I'm ok if the results between packed and unpacked geometries diverge, but if that's the case, than you need to allow for packed geometry in the bake to texture mode of VRay, but until that day comes all packed and unpacked results need to be a match.

Best,
David.

[bdancer]

> the unpacked geo was failing to make use of the "Consider same Object Only" option, so this needs to be fixed

Actually the "packed" fails, because every packed primitive is represented by a different Node (not same objects) and unpacked is correct (single Node same object).

I could add a mode for how to consider if object is the same. Currently it works by render ID, I could add a mode to work by object ID which you could control with Object Properites + vray_objectID attribute.

[david.anastacio]

>
I could add a mode for how to consider if object is the same. Currently it works by render ID, I could add a mode to work by object ID which you could control with Object Properites + vray_objectID attribute.

Seeing that packed geo is what everyone uses this is what everyone sees as correct, and I would just make the unpack behave exactly as the packed. If you want to make an option all good, as long as it is default and the result of the dirt is the same no matter if the geo is packed or unpacked without any user having to go there and change options. I'm not fond of having to do extra attributes just to make it work as it should in the first place (yes I understand that unpacked is the correct one like you explained) this should be seamless.

After months of using VrayDirts with packed geo, there are lots and lots of assets and shaders setup with "incorrect" VrayDirt, and now that things have to be baked no one wants to go back to the geo and start writing new attributes and add object properties to everything, it's cumbersome and will lead to errors, like I mentioned before when an asset is feed to the baker the result needs to match and having people go through hoops and loops to bake their assets is not gonna work.

Best,
David.

[david.anastacio]

I noticed by the answer of Gosho.Genchev on another thread: https://forums.chaosgroup.com/forum/...34#post1095034 , that the "Multi ID Texture" and by extension the "TriPlanar Texture" suffer from the same issue. This is also a problem, again the result needs to match to ensure the bake to texture result matches the packed assets.

Best,
David.

[bdancer]

> This is also a problem, again the result needs to match to ensure the bake to texture result matches the packed assets.

I'm not sure how is that possible...
Packed primitive could contain different packed sub-objects; unpacked down to polygons is a single object - how bake result could possibly match?
Do you expect every sub-object of packed to be baked separately? To single image or to multiple images?
If pack it's just a pack of some polygons, yes, this is doable to support packed, but otherwise packed could contain multiple sub-objects and I'm not sure how to proceed.
Same with tri-planar; how tri-planar on a single mesh could potentially understand that parts of this mesh are "separate objects"? May be I'm just missing smth...

[david.anastacio]

Hi, we're replying via e-mail to you regarding this now.