Is this a known bug?? I have always thought it was a rhino issue, but from current tests, it seems it is a Vray issue. Vray doesn’t read the texture coordinates in blocks well. (tested in both Rhino 4 as in Rhino 5)
See also here:
http://news2.mcneel.com/scripts/dnewsweb.exe?cmd=article&group=rhino&item=335217&utag=
Cheers,
Gijs
Re: Texture mapping problem inside blocks
Do you use a planar mapping?
My experience is, that the mapping widget inside blocks isn’t stick at the objects. So, if you place a block object several times in a scene, all objects use the widget fixed to the coordinate system, not to the objects. It should help to use surface mapping only or extract the render mesh at the block, , delete the original NURBSexport and import as OBJ - so the mapping is burned in the mesh (works for a single mapping channel only). I thought it’s a Rhino issue.
Re: Texture mapping problem inside blocks
I have avoided blocks just for this reason for a long time !! But right now, I just can’t get around using blocks, otherwise I will get lost in my scenes pretty quickly
indeed I am using planar mapping. It’s a pity that this doesn’t work, since it’s such an important one.
Micha, your workaround is a good one, but tedious and counter productive.
please, AGSVis, please fix this one, rather sooner than later. Thanks
Re: Texture mapping problem inside blocks
if you copy-paste geometry a hundred times, your files get ridiculously large.
but hey…
here’s the extract rendermesh workaround procedure once more!
brilliant, I thought about this just a few days ago and finally start to use blocks…
cheers!
Re: Texture mapping problem inside blocks
… in the past there was the problem, that the widget was not sticky at the objects. Today I found, that the mapping is ignored and this is a Rhino bug, because the viewport dosn’t show the mapping of the block too.
Re: Texture mapping problem inside blocks
… and this Rhino bug is a refresh problem. The workaround is - start in place block edit, select the object, edit the mapping, cancel in place block edit → ready, the mapping is refreshed. (during in place block edit a message popup that the block link will be destroyed, but the later Cancel avoid it)
Re: Texture mapping problem inside blocks
Good one!
But, if you’re using the same geometry over and over in different scenes, I’d go for option one.
Re: Texture mapping problem inside blocks
I am wondering if ASGVIS is reading this thread?
The workarounds are good, but still workarounds. The whole idea of using blocks is that updating is fast. With the workaround this is completely destroyed. Or have you scripted the export? Also, it requires to export each and every object as an OBJ separately
Cheers,
Gijs
Re: Texture mapping problem inside blocks
I used the block OBJ export-import workaround not so often, only if fixed mapping is needed. In the last months it is a seat for a train interior only. So, it’s not so much work for me.
Here an other block bug. I have an interior with seats. The seat is a block. I changed the material of the block at the interior scene. If I load the interior scene, VfR ask me should the exist scene material used or overwriten. I choose scene material, but at the viewport and at the rendering the block material is used. Workaround: it only helps to edit the scene block material, than the material is refreshed.