Ok, not sure if problem isn’t coming from Rhino tho.
Activating render view from _Set object shading attributes I can see the texture properly only if the Mapping widget is equal or bigger than my model. If my widget is smaller, it does not appear repetitive as it should. Any thoughts? Thanks so much
Ok, the problem comes from Vray.
I have assigned simple Rhino material and render mode shows of texture perfectly with smaller than the object size mapping widget. Wonder how more people didn’t complain about this BUG.
_Set object shading attributes in Render mode is essential for determining the texture size for design and manufacturing purposes.
And the texture placement from vray is different from texture placement from rhino with same mapping widget! Totally unreliable. Mission impossible. I failed again
I posted this problem 6 days ago- no answer and it takes 5 clicks to reproduce the problem..
We were not able to reproduce the issue you are having. Please provide some additional info which could shed more light on its cause:
- Is the texture placement type in V-Ray set to, Environment?
- Is the problem fixed once placement type is set back to 2D (UV Chanenl)?
Furthermore:
- Full Rhino version number
- Full V-Ray for Rhino version number and date (can be found in V-Ray > Help > About)
- Is this reproducible if the V-Ray plugin is disabled?
- Is it reproducible reliably (on every attempt)?
The V-Ray and Rhino texture mapping controls can be used simultaneously but they are not synchronized together, e.g. changing a UV repeat value in V-Ray modifies the texture itself and does not update the UVW repeat in Rhino. Changing the Rhino UVW repeat, on the other hand, further changes the mapping using the already modified texture provided by V-Ray. An illustration of what you are struggling to achieve would be helpful in order to provide you with proper explanation.
I have a similar problem so I thought I would post it here rather than starting a new thread. I apologize if this was not a good idea.
I have an ocean material whith a difuse layer for the color, bump map for the water waves and second diffuse white layer with an opacity map for the ship’s wake foam on a different mapping channel.
The problem is the inconsistency between the viewport display, the rendered image and the vray tiling parameters.
On the first image, in order to achieve a correct render, tiling needs to be enabled (which shouldn’t) but then the viewport displays tiled.
On the second image, disabling tiling displays correctly in the viewport (as expected) but the rendering doesn’t.
So although couter intuitive, I must leave tiling on to render correctly and put up with a tiled viewport …
I recall a similar problem years back with vray 2.0 which it was fixed after i reported it to Chaosgroup support. It was fixed in version 2.0.26400 in Oct 2015.
By the way I tried also reverting the vray settings to defaults with the same results.
GPU with Tiling on: Viewport and rendering, both display tiling (expected since tiling is on) but note that with CPU rendering (above) tiling needed to be on to get the proper result with only one tile and whole ocean blue.
I don’t know if this would be considered the same bug:
At our office we have an issue where the displayed UVW mapping within the viewport is static.
Unless we activate the mapping widget.
By unselecting the mapping widget again, the uvw mapping returns to the prior static display, as if nothing was changed.
The render does however change.
(It’s just not visible within the viewport)
If a fix or guide for this issue has been made, we would deeply appreciate it!
We are using the newest Rhino SR release.
We have also tried the the newest SRC (6.6.18168.12081) without any luck.
Indeed, as you mention, the mapping does not occur in the viewport until forced via object transformation.
And you are also right, we did not have this issue with Rhino 5.