[polynurb]

..just figured this out.. it happens even with a box and one material..

it is still being displayed in the object properties.. "material: Plugin" and the correct name, but it isn't properly assigned and does not show up in the plugIn maxwell material editor.

[JDHill]

I don't have the latest WIP installed. I'll try to check it out tonight.

[polynurb]

thanks for taking a look!

here is the sample file i mentioned (single box):

http://www.mediafire.com/file/lymltygiczt/NoMXM.3dm

if it may help in any way...

*posted on the newsgroup too

[polynurb]

FYI

i reverted back to feb 09. WIP and it reads the files saved with the last wip fine.. also saving as rhino4 (and opening in rhino4) worked.

[osuire]

Same problem here.
The display of texture mapping is also somewhat erratic : I need to open the material editor and fiddle around to make the display mathch the mapping that I set.
By 'fiddle around, I don't meann actually changing anything ; it seems that Rhino has to "think" the texture was updated to display the mapping properly.
This used to be a big pain in V4 some time back...

Do you have an idea why mapping is so unreliable in Rhino ?

--
Olivier

[JDHill]

A few possible reasons:

1. it's new: Rhino has only had mapping at all for one version
2. Rhino was not originally designed with heavy rendering in mind
3. Rhino is a NURBS modeler; render meshes add an extra layer of complexity
4. Rhino is inexpensive; that means a smaller team, so progress takes time

It is much easier for other more mesh-based modelers to accomplish this kind of thing, since their objects don't require the application to maintain doppelgänger render meshes -- their objects can be shown directly on the screen; if video cards could directly visualize NURBS surfaces, that would definitely help.

[polynurb]

Same problem here.
The display of texture mapping is also somewhat erratic : I need to open the material editor and fiddle around to make the display mathch the mapping that I set.
By 'fiddle around, I don't meann actually changing anything ; it seems that Rhino has to "think" the texture was updated to display the mapping properly.
This used to be a big pain in V4 some time back...

Do you have an idea why mapping is so unreliable in Rhino ?

--
Olivier

i also noted that.. on older WIP too, though.

in my current project i exctracted most rendermeshes to stay easy on ram and viewport performance.
oddly, when i add a new projector to the meshes, i often get that "flicker" problem, that the displayed projector is going back and forth between old and new. it is displayed rigth during viewport rotation, and jumps back once it rests.

[rober]

Hy guys

finally I have buy Maxwell 2.0 !

I have now the last version of all I think:

-The "beta" Rhino 5.0 (64 bits) -16/3/2010
-Maxwell for Rhino v. 2.0.5.0 17/10//2010

I will try to work ...I hope the problems with Rhino plugin and Rhino 5.0 (64bits) are finish ( ?!?)
What do you think about?
rober

[polynurb]

I will try to work ...I hope the problems with Rhino plugin and Rhino 5.0 (64bits) are finish ( ?!?)

rober

i somehow doubt they fixed it all within one update... but you will tell us

using betas is always dangerous... anyway it was the first serious glitch i experienced in almost a year of using Rhino5 (in 64bit)

[rober]

Hello Polynurb,

I start the tutorial of Think but I cannot drag a material !?!


JDHill...what happens:)!
rober

[rober]

another way to assign materials...

[polynurb]

sorry.. can't help you much with that.
i hardly ever use the drag N' drop material assignment, but prefer to use right click in the material manager after selecting the objects. that way should always work!

[JDHill]

Rober -- drag & drop material assignment doesn't work correctly if the camera Heads-Up Display is active. However, if you go to plugin Options and set De-select all on drag to No, then you should be able to pre-select objects and drag/drop materials on them with the Heads-Up Display active.

[rober]

Thankyou HDHill...

another diferences with the video tutorial :

1- continuing like in tutorial I have an "emitter.based" with
-3 ligths (Multilight)
-environment= none
-The sun, like in tutorial, continue activate but when Maxwell run I have in Multilight a cursor for environment (sun?)???
that I don't want...then I disactive sun and the cursor of environment desappear Is the sun an environment?
... diferently in the shaded viewport, when sun is activate I don't see the shade of the sun like in tutorial

2-In my plugin I have in Multilight:off, Intensity,Color+Intensity..What is this?

3- I'm not an expert of image bit deeph. In the new field near the name of image is better 8 or 16?
rober

[JDHill]

Hi Rober, the videos were made before 2.x was even released (in order to be available at its release), so you may find various differences between what you see in them and what you see using Maxwell V2. There have also been a couple of updates to both Maxwell and the plugin since the initial release.

That said, I'll try to answer your questions one by one:

1. this may be due to changes in maxwell.exe since the V2 release. To be honest, I am not an expert right now on what you should expect to see in the maxwell.exe multilight panel -- the plugin doesn't really control what you see there, and you may want to ask about it in the regular Maxwell forum.

2. where Maxwell V1 multilight only allowed you to adjust the intensity of emitters during rendering, V2 allows you to change both their color and intensity. Using the Color + Intensity option enables this new ability, but you should only use it when necessary, because it requires a good deal of memory.

3. unless you have a specific requirement, and you wouldn't be asking the question if you did, it will probably be best to keep using the standard 8 bit output.