[Josephus Holt]

you are sure right that it makes no difference whether it's by object or by layer. When I updated to the latest wip it lost all the material plugin assignments on another scene I'm working on. Do I post this on the Rhino NG or is that something you can take up w/McNeel?

[JDHill]

It would depend on whether or not you can reproduce it using the new WIP. Meaning, does the current build save and read files without a problem? If so, then it would appear to be a bug that's already been fixed.

[Josephus Holt]

Guess I spoke too soon. The latest wip does not fix the problem. Still having major display (rendered) issues (not related to this thread).

I also reassigned ALL the textures by layer just to test, and now back to the same problem that started this thread...Rhino is losing the material plugin assignments, exactly the same thing is happening that you saw in the file I sent you. I just don't know what to do anymore....I wasted an entire day with this

So do I abandon the v5 render-mode view and model only in v5 (I like some of the new tools) and then continually import to c4d to view/render, or do I try v4 and see how the render view works there (it is VERY helpful while modeling/designing to see the materials)?

[JDHill]

I am trying to get a file into the state you have there, but so far I am unable to do it. That being the case, there is absolutely no way I can even begin to tell you what the cause would be. If you:

1. create a new document
2. create four new layers
3. import four maxwell materials
4. assign them to the four layers
5. create four cubes
6. put one on each of the four layers
7. save the file

- then -

8. open a new document
9. import the file from step 8

Are your materials present? Are they assigned to the layers as expected? If so, what do you need to do to make the issue appear?

I can't really tell you what a good strategy might be vis à vis building a workflow with Rhino/Cinema; I know there are people who do that, but I have not; I do not like modeling in Cinema. With Rhino V4, not being an pre-release alpha, you may run into less of these quirks, but you are going to be memory-limited.

[Josephus Holt]

Sorry...did not have time to try out with a new file. I went back to v5 wip ("save as" from v4)...all went well for a while, but I just noticed that I've again lost all my Maxwell material assignments. One other thing I see too is that where I had changed a material (clone from another one), that it's now back to what it was before I changed it...at least in the layer menu. The plugin has lost the assignment though. Just so you know...ALL the plugin material assignments get lost when this "bug?" stirkes!

I'm going through and reassigming the material with the plugin, then will do a backup save, and will try out a couple of things.

I just re-inserted several objects (that I remember putting in) as well as cloned some materials...so far all ok. I'll just keep the Maxwell Object Properties open and after anything done with the layers and/or inserting an object I'll click on an object to see if it still has the assigned materials.

Joe

[JDHill]

Well, if you can find anything in particular about what it would take to reproduce it, let me know, because it's just not happening here. Don't take that as me doubting you -- it's just unlikely that I tax the system as heavily as you do.

I didn't really follow the problem with cloning; are you saying that:

1. you have a material, 'material' assigned to a layer, 'layer'
2. you clone the material in the plugin and end up with 'material (2)'
3. you then drag 'material (2)' over to 'layer', replacing its 'material' with 'material (2)'
4. some time later, you find that it didn't take: 'material' is still assigned to 'layer'

Is that the scenario?

[Josephus Holt]

Well, if you can find anything in particular about what it would take to reproduce it, let me know, because it's just not happening here. Don't take that as me doubting you -- it's just unlikely that I tax the system as heavily as you do.

I didn't really follow the problem with cloning; are you saying that:

1. you have a material, 'material' assigned to a layer, 'layer'
2. you clone the material in the plugin and end up with 'material (2)'
3. you then drag 'material (2)' over to 'layer', replacing its 'material' with 'material (2)'
4. some time later, you find that it didn't take: 'material' is still assigned to 'layer'

Is that the scenario?

I'm watching it close now and will until I find out what action causes it.
Regarding the material cloning problem, yes, you read that correctly, that is what happened.

[Josephus Holt]

Can't believe it...I just noticed that the Maxwell assignments are LOST again!!!! I was not paying attention!!!! Trying to go back and see where it happened

[Josephus Holt]

almost 8:30 pm....the "bug" just slipped past me again and wiped out all my material assignments, was not able to back up to where materials where still assigned...have to catch it almost in the act. It's related either to the insertion of an object OR editing existing geometry with materilals assigned. I WILL GET HIM

[JDHill]

It will be helpful if you are very specific with regards to terms like 'insertion of an object' -- lots of stuff goes on behind the scenes, and it may make a big difference, depending on exactly what you are referring to. Any app that has undo/redo is constantly making copies of things, replacing existing items with stored items, keeping track of deleted/undeleted items, and so on -- if there is a specific operation in which the copy is not behaving correctly, i.e. it is not copying all attributes correctly, then you could end up with a problem like this.

[Josephus Holt]

It will be helpful if you are very specific with regards to terms like 'insertion of an object' -- lots of stuff goes on behind the scenes, and it may make a big difference, depending on exactly what you are referring to. Any app that has undo/redo is constantly making copies of things, replacing existing items with stored items, keeping track of deleted/undeleted items, and so on -- if there is a specific operation in which the copy is not behaving correctly, i.e. it is not copying all attributes correctly, then you could end up with a problem like this.

Hope to narrow it down soon to which action will do this and be able to send a file in which it can be reproduced. What I find interesting (and distressing) is that when this happens, the layer state gets restored to a state that was before I saved it, because I'm constantly saving. For instance, for the countertops I had originally asigned a material called "ubatuba", but have long since replaced it with an MXM called "granite black". When this event happens, sure enough "ubatuba" shows up again for the countertops, eventhough the computer has been off and restarted since. Anyway, I hope the next time this happens that it will be immediately after a specific action so I know what action caused it. Joe