node "simple_color" "BG Color" { name "BG Color" pos 270 10 nodeInput "Color" { name "Color" value 0.34374 0.31249 0.273396 parmR NO_PARM parmG NO_PARM parmB NO_PARM node NO_NODE file NO_MAP } }

Above is the base of what lays underneath what you see in the Material Room. All the lines in a Node are made of the above lines. Given that the above are used to feed the inputs that are the black boxes of the code that is what makes the colors you see in the final output. My question is WHY don't you want Poser to use a Plug-In Render engine that can be changed by you the user instead of waiting for the Programmers to make a new version of Poser? Since the format of the nodes is fixed It would be real easy to program a bridge to send a Render to any engine that Poser wants to support. And Given that Open Shade Language OSL is supported by Cycles, AMD ProRender and LuxRenderer then you the user could use any one of them you want and when they are updated to support the newest hardware you are right there. And with OSL the venders only have to support that and Firefly since SuperFly is mostly Cycles based it should translate with little problem.

Poser 5, 6, 7, 8, Poser Pro 9 (2012), 10 (2014), 11, 12, 13