Attached Link: http://www.renderosity.com/messages.ez?ForumID=12390&Form.ShowMessage=1406569

I've made an attempt to create a workaround for Poser 5's material room bug - when you apply a MAT and after entering the Material Room, textures change back to a prior setting. My fix attempt is a Python script that sets the object's color to white, highlight/Ambient/Reflection to black and disconnects the shaders. It writes a temporary MAT pose and then loads that into the scene. You can also save the MAT created for re-use later. It will work on any object: standalone prop, smartprop, figure - as long at least one figure is loaded in the scene. It isn't 100% foolproof but it's a valiant attempt I think. Tested in Poser 5 SR-3 on a PC. The link is to the Poser Python forum- but I thought it might be useful, so I wanted to make brief mention of it here.

In a similar vein, I am finding that in P5 a complete MATpose can be used. a Poser 4 style MATpose with partial information can be used. a partial Poser 5 style MATpose does not work - it undoes existing settings. What I mean is - if you want to do a MATpose that does the nodes for a specific bump and be able to use it on any diffuse texture setting, it does not work. The colors get changed. With a P4 MATpose, if you do not want to change a diffuse setting or ambient setting, you just leave those lines out of the MATpose. If you leave nodes out of a P5 MATpose and it is something that has a setting in the figure, Those nodes are affected - disconnected/ colors changed. Has this been confirmed or refuted?

Haven't really toyed with the partials that much. The bug hits particularly nasty with the topmost layer. Maleposer.com has some nifty .mt5 files to fix a singular material and they work well. I did observe that you could even leave out the p4-specific settings in a MAT and as long as the new shader areas were present, it will change fine - so it almost appears that there's a rendundancy there -- it may be a backwards compatibility setting. So for a P5-only MAT, you could start it like this: { version { number 5 } figure { material SkinTorso { shaderTree { node "poser" "PoserSurface" { name "PoserSurface" pos 10 10 showPreview 1 nodeInput "Diffuse_Color" { name "Diffuse_Color" value 1 1 1 parmR NO_PARM parmG NO_PARM parmB NO_PARM node NO_NODE file "" } ... etc, etc...

.

Did that work, Jaager? I'm curious to see if that fixes "our" problem. Thanks, dave

Just came off my sleep cycle, I think I see what NW is doing. - the dittos. I will have to play with this as soon as I get a chance. I take it that I am not the only one who cannot get a P5 MATpose to work with whole node sections left out (the ones that I am not interested in changing with the MATpose, but that the figure is using already)? The problem I see with this fix: suppose you want to have a MATpose that adds bump texture A. and another for bump texture B. You want to be able to add them to any existing diffuse texture and not have to have the partial bump MATpose "know" which diffuse texture you are using (With FireFly bumps are particularly tricky since there are two real node choices and the P4 master at the top does not affect either of them.) name "Diffuse_Color" value 1 1 1 in the above - changes the color to white an existing character may not always have the base color white - there is often shading. A MATpose with this erases the existing diffuse color - even if all you wanted to do auto add bump textures - or ambient settings or other touchups to just one part of all those settings.

Yes, the script only makes white-out clearing MATs, not MATs representative of the current object colors/textures/etc. CL hasn't added any Python methods to reference the P5 specific materials yet. I have an idea on how to do it though - It will take a little bit of fiddling.

Since it is beginning to look like partial MATposes for P5 nodes is not something we can do, if Python script will do it, then it should make Python a little more main stream. Having to do partial changes directly in the Material room, especially for the skin on a subdivided material figure like V3 - - it just ain't no fun a'tall.

No, my friend, it isn't fun. It makes setting up materials for V3 a bit of a journey. Yeah, I'm having a blast working with the Python stuff - just using nice scripts is something no Poser 5 (or ProPack) user should pass up. Right now, I wouldn't know what to do if I didn't use a "Delete Lights" script, since Poser won't do it natively.

Attached Link: http://www.maleposer.com

A python script would be great especially one that could read the material names and then apply default settings to them all, but I'm not sure of all the mechanics at work here. In my experimentation, I have found (as Jaager has suggested) that complete P5 compliant MAT poses (ones that include all the parameters of the Root node or "Poser Surface" for each named material in the figure) will actually clear all the nodes not just detach them. Interestingly, this includes all linked secondary nodes even though they are not referenced specifically in the MAT pose file. This is the basis for my Clear Nodes MATS and material that you can get at Maleposer.com (in Freestuff area). These allow you to clear an entire figure at once (all materials) or just one material group at a time.

ronstuff - I have the Clear Nodes that you have available at maleposer.com and they are wonderful. The MATs that are made with my python script do clear the entire figure of all materials.

Great - I just tried it and it works fine - thanks so much! I made a button for it on my mainButtons so it would always be at hand! Now I wish somebody would write a script to make a hotkey that would hide/unhide the python window.