[kami]

Hi JD
My real scale is behaving strangely today (I just updated to the latest Rhino 5 WIP).
Just to let you know ... maybe it's related to the newest update.
here is the file:
http://dl.dropbox.com/u/4900894/real_scale_error.zip

The texture is always streched to the whole object (like surface mapping) and it does not make any difference whether real scale is ticked or not.
Or am I overlooking something?

Thanks for checking,
kami

[JDHill]

Just a quick question: can you duplicate the behavior on V4? Currently, I would expect many parts of the plugin not to be working entirely correctly on V5.

That said, this file appears to be working fine here on the August 12 x64 WIP. I opened it, fixed the missing texture paths, set tile to 5.0/5.0 and exported to Studio: the tiles here are 5mx5m, and they are also that size in the Rhino viewport. Are you sure that you have Maxwell set as the current renderer? Texture mappings are managed in a plugin-specific way, so if Maxwell is not the current renderer, your results may be unpredictable.

[kami]

It works fine on Rhino4 here as well.
I got the August-12-Wip and maxwell as selected render engine. And it does not show correctly nor render correctly there.
Size is set to 5x5m as well and the object is 100m long.

[JDHill]

Hmm...I really can't tell you much more about it then. Might there there any way that you would be able to trick it into working? If so, what would it be? Something like that might help me to understand what's happening in the failure case, and then to reproduce it here.

[kami]

Hi JD
There seems to be a general problem with rhino5 on my machine. I just noticed that real scale isn't working at all at with the latest update (it is always displayed as surface mapping rather than box mapping). I have no idea what's caused that and what I can do against it. I just reinstalled the maxwell plugin without any effect. You got any ideas?
cheers, kami

[JDHill]

Sorry, but without more info to go on, and not being able yet to duplicate the behavior here, I can't really make any very intelligent guesses. I would probably just suggest playing around with some native Rhino materials/mappings, and see if you find any similar issues there.

[kami]

thanks. I'm gonna wait for the next release and try around then.

[kami]

I installed the latest rhino5-wip (x64) yesterday and also reinstalled the maxwell plugin. the problem persists. The Real scale switch is just not working at all. If it is activated and I change the tiling of the texture nothing happens in the viewport, nor in the rendering. the texture is always tiled once in every direction per surface.
I have no idea, what could be causing this and what I could change, or try. What would you do? All I remember is, that I was installing windows updates lateley, but am not sure if this is related, as it worked fine a few weeks ago and still works fine on rhino4.

[JDHill]

Sorry, it's still working fine here on the Aug. 19 build. Have you tried to reduce it to the simplest case?

1. open a new document
2. make a 1m cube
3. create a new material
4. assign it to the cube
5. assign a map to refl0
6. turn on real scale
7. set tile x/y to 0.5

Do you not have a cubic mapping now, with two copies of the map in both directions? If you do, then check the other real scale materials you're using -- do they use channel 0 in their real scale textures?

I'm sure you checked all of that, but I mention it anyway, just in case.

[kami]

Ok. I did the test below and will post the result below:
here is my scene:

starting rhino 5, creating a cube with 1x1x1m and a material with 1x1 tiling (the texture showing two white squares, one black and one red per tiling). no realscale
http://www.deiters.ch/maxwell/r5_01.jpg
what I noticed is that the texture isn't scaled correctly even here

next try: change the tiling to 4x4 per surface
http://www.deiters.ch/maxwell/r5_02.jpg
nothing happens

next step: enabling real scale and putting it to 0.5mx0.5m
http://www.deiters.ch/maxwell/r5_03.jpg
still no change

Now I save the file.
http://www.deiters.ch/maxwell/realscale.zip

and open it in rhino 4:
http://www.deiters.ch/maxwell/r4_01.jpg
rhino4 is displaying the texture incorrectly

doing a maxwell_restoreviewport:
http://www.deiters.ch/maxwell/r4_02.jpg
not it is correct!

I have no idea, what I can do. It seems like my rhino5 is making some strange things ...
Is this a wip-related problem and am I asking at the wrong forum?

cheers, kami

[JDHill]

Actually, in your first image, it is scaled as expected -- that is what the default 'surface' will would look like on the cube. The remaining V5 images would make sense if real-time materials were disabled in the plugin -- are they? What does restoring the viewport do in V5?

[kami]

you're right, I thought wrong. the first image would be right.
but the second rhino5 one should look like this:
http://www.deiters.ch/maxwell/r4_03.jpg

and when I hit refresh viewport on the realscale one with 0.5x0.5 it looks like this:
http://www.deiters.ch/maxwell/r5_04.jpg
still different than the rhino4 version

what do you mean by "if real-time materials were disabled"?

[JDHill]

The plugin allows you to turn off real-time viewport feedback, since with large models, it can slow things down alot. The toggle for it is in the database manager's top toolbar.

[kami]

oh my god, JD, it is working !!!!
I can't describe how happy I am

what I don't understand is, why the RestoreViewport did not work before. But nevermind, everything seems fine now.
I searched a lot under those settings in the scene manager. How can a button so dangerous be so hidden. I almost never use the database manager.

cheers, kami

[JDHill]

Not sure -- Restore Viewport should work regardless, since it is an explicit action requested by you.

How can a button so dangerous be so hidden. I almost never use the database manager.

For what it's worth, every time you start Rhino with it disabled, this is printed in the command-line:

Code: Select all

Maxwell: Real-time viewport materials are disabled. To enable them, see the Database Manager toolbar

So yes, I know it can be hard to find, but do you have a different idea, which is not likely to be just as bad for a different user? Because, I don't think that one place or another would really address the root problem: the plugin has issues with feature creep; it is getting older, and lots of specialized things (many only marginally useful, imho) have been implemented by now, which has made for quite a cluttered interface.