[polynurb]

so here are some observations i wanted to share, to see if others encountered that issue, because if then this might help...
(just to clear things a the start, this is not a plugIn related issue; IMHO)

below you see the following:
Pic1:
in the first screenshot (rhino GL renderpreview) there is the initial object;
as you can see there is a problem with the welding (it is a mesh object imported). That is often the case with LQ poly models..
Pic2:
I used unweld 0 to correct the bad welding; looks good.
Pic3&Pic4:
reapplied welding 20 to it; result: garbage texture coordinates
To check I rendered it, and if you look closely you can see that it renders wrong, too.

But why?
I only have a suspicion: it looks like projection is not "updated" after new welding is applied (this can not happen with nurbs objects directly, but with their derived meshes) so the original texture coordinates become garbage, stretched over the triangles.
Pic5&Pic6:
Now more by accident I figured that switching back and forward
between singled and divided texture space results in what can be seen in the 4th screenshot: a correctly textured object, with the rendering also looking correct. It must somehow update the tx-co of the mesh.



this I posted some time ago on the rhino Newsgroup, didn`t get much respond however;
same problem, this time with displacement.
top:Nurbs cylinder
middle:rendered nurbs cylinder with displacement
bottom:rendered extracted rendermesh with new welding applied to it.

back then I could not understand what was going on.... now i can at least correct it.

[polynurb]

I think that also helps with problems of realscale..
I just opened an older file where I found some objects that did not properly accept the realscale option earlier.. then I switched single/divided/single and it displays fine...

[JDHill]

Don't worry about it too much, here's a 1D Scale using the new RS:



So, what you're looking at is:

- 2 1m cubes, 2 0.5m cubes
- a 2x2 checker-pattern map
- on the left, an RS texture managed by the plugin, tile x/y = 0.5
- on the right, box-mapping by Rhino, mapping 'Size' parameters set to 0.5

You can see that when you scale an object, the box-mapping is also scaled...this makes it very difficult for the plugin to maintain the RS concept. However, you see things are working much better on the left...

[polynurb]

That looks promising

thanks JD!

p.s.
looking back at the first post.. do you maybe have an idea what is happening there
with the welding stuff?

[JDHill]

Sorry, but I don't - I've seen some generally-weird behavior in Rhino texture-mapping tools since they were added...so I'm glad I've finally found a way for the plugin to do RS without them.

[firebird]

sorry for the question, but what is RS?

real scaling?

[JDHill]

I wished more people didn't know.

...it means that if you turn on the Real Scale parameter in a Maxwell texture (set Channel > 0, there will be a toggle button in the tex editor toolbar), then a tile X of 5.0 doesn't mean 'tile the map 5 times', it means 'make each tile 5.0m, no matter what size the object is'...this has been in the plugin since 1.5, but it has been very difficult to use, due to the problems polynurb was posting about earlier.