[Josephus Holt]

Working with textures in Rhino is going to do me in one of these days....both these brick walls were fine at one time (the left one is correct at the moment). I had to restart Rhino because that was the only way I could get the floor texture to refresh correctly and then the brick walls on the right seemed to have lost their mapping. When I click on the left wall, you can see how the correct mxm is selected. When I click on the right wall...nothing. Anything jump out at you? I've done refresh materials, clear cached data.

[JDHill]

What shows up in the Object Properties panel when you select the right wall? In the Materials page, is a plugin material indicated, or is it a native Rhino material? What about in the Maxwell Object Properties page? Is the wall regular geometry, or is it a block instance?

[Josephus Holt]

The Object Propeties was by Layer, as well as the Maxwell Object Properties (does that answer your question?). The one on the left which I had no problems with was By Object with plugin checked. When I changed the right one to by object>plugin that fixed the problem. Looks like the By Layer option is giving me some headaches, but is sure the easiest way for me to assign/change textures.

Will come back to this if/when I run into it again on this project...have to model/render the Club Room/Bar/Wine Room of the big house I've been working on.

[JDHill]

I'll still mention a couple additional questions, with respect to your by-layer objects:

1. Maxwell Object Properties shows by-layer, does it also indicate a Maxwell material?
2. does the layer's material (in Rhino) show up as being by-plugin?

[Josephus Holt]

I'll still mention a couple additional questions, with respect to your by-layer objects:

1. Maxwell Object Properties shows by-layer, does it also indicate a Maxwell material?
2. does the layer's material (in Rhino) show up as being by-plugin?

#1 No. see below. The material was dragged to the layer, and then I created this small section of wall with that layer active...the bricks show up, but the mapping is not correct.
#2 yes.

[Josephus Holt]

JD, I've got another instance where I had to make some adjustments on a texture map and when I go back to the (Dining Room) scene, Maxwell properties does not show that material assigned any longer..(just like what I posted). The material (Travertine01) is assigned by layer. What is the viewport showing, a Rhino copy of the material? So how do I get this back to being assigned a Maxwell Material?

[JDHill]

Could you remove most of the geometry from the scene and email it to me? I am not having any luck getting a document into the state you show here. I don't need any of the textures or anything, just the .3dm with a few objects that show these characteristics.

[Josephus Holt]

sure will as it's become a pervasive problem...I'm probably not doing something righ, but would sure like to know. I'll get it off to you in the next couple of hours.

[Josephus Holt]

it's time for a long walk...this is so frustrating! I just imported/inserted a Rhino object and it throws off all the viewport settings...have to constantly refresh viewport materials.

I can't believe this!!! I just found in a file I already rendered that MANY of the texture mapping are ALL over the place...nothing like what I set up! I've got baseboards with CYLINDRICAL mapping, and curved sections of the doors that were cylindrical and are now box mapping!!!!

Is this just a v5 wip issue or the same with v4? This just is not workable at all. Not pointing the finger anywhere...but I've just lost hours of work. If it's due to the nature of the v5 wip I'll just have to avoid it for the time being.

[JDHill]

What, exactly, do you mean by import/insert? When you use the Import command, Rhino does not replace the current document's layer attributes with those of the imported file; imported objects which use by-layer will now use whatever you have set up on that layer in the document you're importing into. Any layers in the imported document which do not exist in the current document will be added, and those will obviously have the only attributes they can: the ones from the document being imported. I have no idea how this bears on resolution of texture mappings during an Import; I have a difficult time divining how those are handled even when there is no Import involved.

[Josephus Holt]

I understand what you're saying and that is what I would expect.

I use the insert command quite a bit, but when I do, it changes the viewport mapping of other objects that are on completely different layers. Maxwell refresh viewport materials puts it back where it should be, it's just more work every time that seems like I should not have to be doing.

I have no idea what happened to a lot of my material texture mapping settings, although I suspect it's the "by layer" option that is giving me problems. Maybe before switching over to c4d for rendering (which I really want to avoid), I should try to set all my textures "by object" and see how that goes.

[JDHill]

I'm able to see what you're seeing with the file you sent. The reason is that Rhino has dropped the user-data attached by the plugin to the materials 'Travertine01' and 'Mosaic straight' at one point or another -- without this data, there is no way for the plugin to know which of its materials is supposed to be used for the layer. Also, there is no Maxwell material in the document which would correspond with the 'Travertine01' material. There was at least one recent WIP build that would drop various plugin data; what are the chances that the objects associated with the layers 'Dining Room' and 'Mosaic Straight' are from a document last saved a month ago or so?

[Josephus Holt]

I'm able to see what you're seeing with the file you sent. The reason is that Rhino has dropped the user-data attached by the plugin to the materials 'Travertine01' and 'Mosaic straight' at one point or another -- without this data, there is no way for the plugin to know which of its materials is supposed to be used for the layer. Also, there is no Maxwell material in the document which would correspond with the 'Travertine01' material. There was at least one recent WIP build that would drop various plugin data; what are the chances that the objects associated with the layers 'Dining Room' and 'Mosaic Straight' are from a document last saved a month ago or so?

Yes, those materials would be from another doc saved some time ago. I've been trying to (when I think of it) to always "save as mxm" in a separate file, but sometimes I forget that and so the material resides only in that doc.

I just changed all my materials to be "by object", will just do that from now on and see if there are further problems. Jeff LaSor from McNeel confirmed some viewport issues the last couple of wips.

[JDHill]

There would have been nothing you could have done to prevent this particular problem -- Rhino just simply lost some data, so we end up in a bit of a no-man's land.

As such, materials by-object would not have made any difference -- the data that was missing was attached to the materials (the Rhino ones), not the layers or objects. So, it would've been the same using by-object. Note also that if data were lost from objects, then any real scale data from the plugin would also be lost -- that could give you some texture mapping headaches.

Also, none of this is likely related to any display issues you may experience; those are most likely between Rhino and your video card.

[Josephus Holt]

There would have been nothing you could have done to prevent this particular problem -- Rhino just simply lost some data, so we end up in a bit of a no-man's land.

As such, materials by-object would not have made any difference -- the data that was missing was attached to the materials (the Rhino ones), not the layers or objects. So, it would've been the same using by-object. Note also that if data were lost from objects, then any real scale data from the plugin would also be lost -- that could give you some texture mapping headaches.

Also, none of this is likely related to any display issues you may experience; those are most likely between Rhino and your video card.

That's the price I have to pay to get to work on the v5 (64 bit) wip.

I just downloaded the latest (yesterday's) wip and it fixed at least one of my display issues right away.