Mapping troubles

[John_Do]

Hi,


I'm currently setting up a scene and having several trouble with the texture mapping, I have different result between Modo and Vray with the same settings.

// First case :



The texture appears properly mapped in the Modo viewport, but is stretched on the Vray render. Vray doesn't seem take in acount the Horizontal Wrap parameter.



// Second case :

With a planar mapping or an unwrapped surface, I have an offset between Modo and Vray.

Unwrapped version :



Planar mapping :



With the unwrapping, there is an apparent offset on the Modo version, but the texture is correctly mapped on the Vray render ( and the UV tab shows that it's the case ).
With the planar mapping, there is an offset due to the texture locator position, but it is easily correctable by check "World Coordinates"...in Modo. Vray doesn't recognize this option and I have to manually offset the texture locator ( half the size of the texture in X and Z ).
Could you enable this option in the future builds ? It is really useful, I sometimes don't understand the mapping system of Modo ( see below ).




Any idea of what's happening here ?

[vladimir.nedev]

The "World transforms" and "World coordinates" don't work in V-Ray for MODO at the moment.
Also horizontal/vertical wrap work only when the "Projection Type" is set to "UV Map" (and even in that case there are differences in some cases).
We do plan on improving in this area.

Greetings,
Vladimir Nedev

[vladimir.nedev]

The issues mentioned here should be fixed in the nightly build from 2015-03-20. Also for the 3.00.06 open beta build.

Specifically
- "World Transforms" checkbox now works in V-Ray (previous behaviour was as if it was always checked);
- "World Coordinates" checkbox now works in V-Ray (previous behaviour was as if it was always unchecked);

NOTE that the V-Ray result should match the MODO preview/final render.
The MODO OpenGL view-port doesn't give the same results as the MODO renderer in a lot of cases it seems.

I don't have your test scenes, so when you get a build with the fix, let me know if there are still problems.

Greetings,
Vladimir Nedev

[John_Do]

Good to hear that, when will the next build be available ? ( I don't have access to nightly builds )
I did a fully procedural wood shader, it will be a good candidate for these new functions.

[vladimir.nedev]

Good to hear that, when will the next build be available ? ( I don't have access to nightly builds )
I did a fully procedural wood shader, it will be a good candidate for these new functions.

I am planning to make it next week, probably near the end. It might take some additional time for it to be uploaded to the site as well.

Greetings,
Vladimir Nedev

[John_Do]

Ok, thank you for the answer. Will changelog be the same like in this thread? Also, do you have an idea of when you could implement the Variation Texture ? I suppose it's not an easy thing but this effect is really really powerful, it would be a great addition. But I suppose also that you're already a pretty busy developer

[vladimir.nedev]

Ok, thank you for the answer. Will changelog be the same like in this thread? Also, do you have an idea of when you could implement the Variation Texture ? I suppose it's not an easy thing but this effect is really really powerful, it would be a great addition. But I suppose also that you're already a pretty busy developer

Yes, this will be part of the changelog.

Hopefully I can look at the variation texture for the build after that (3.00.07). The variation texture already works in V-Ray for MODO for Replicators when the "Variation Source" is set to "Particle".
The resulting colors even match the result with MODO's renderer.
I need to do the "Mesh part"/"Item" variation source options, but these won't match the MODO renderer exactly, as we will have to generate the random numbers ourselves.

Greetings,
Vladimir Nedev