Mapping - viewport and rendering are different

[Micha_cg]

... here the rendering is better than the viewport mapping



... and here the rendering show more artefacts and distortion than the viewport


What's the reason for both effects?

[dalomar_cg]

Re: Mapping - viewport and rendering are different

well I can tell you that the poor viewport display is probably due to a mesh with some long thin triangles along the bottom. UV space looks to be pretty constant, but the viewport feedback doesn't deal with those odd triangles as well.

as for the second one, I would say that its a result of trying to keep U and V space continuous as opposed to allowing there to be sharp breaks in the mapping. Chances are there's one face (or a row of faces) where the UV space goes crazy from the opposing orientations. The odd streaks are trying to interpolate between very different sections of texture coordinates.

those are my guesses at the moment...thats also without seeing you're model so...

also, what are the results of those when you render with the Rhino Renderer

[Micha_cg]

Re: Mapping - viewport and rendering are different

I tested it now - Rhino renderer and Maxwell render it the same like at the viewport. For the cylinder, the Vray method is great, but for the cube it's a problem, because the texture interpolation is extrem visible. In the past I thought it's caused by the Rhino mapping, but I see now, it's a Vray effect. The problem is, that at finer mesh settings the interpolation is still visible.

Doe's Vray support an own cube/cylinde/spherical projection, that could be used, a mesh independend projection like the environment mapping or the camera mapping (Vlado says some months befor, that's available at the SDK ..)?

[ALTO]

Just a question is this bug fixed in the next release?

Thanks

[fpedrogo]

We are still working in the new build, but I made some test and seem that we still having this issue. I hope we could find a solution.

Best

[ALTO]

Ok thanks, i've noticed that exporting to obj and reimporting the mesh fix the problem (not really a good solution if you need only nurbs) so it's how vray export the mapping parameters...

Anyway there is also a Rhino bug when you apply a Box Mapping wich is smaller than BoundingBox, but i'll ask to Andy.

Thanks

[fpedrogo]

Ok thanks, i've noticed that exporting to obj and reimporting the mesh fix the problem (not really a good solution if you need only nurbs) so it's how vray export the mapping parameters...

I agree with you that this is not the perfect solution, but could save our render. I hope we can do something to find a better solution.

Best