Re: OctaneRender® for Poser beta - build 1.02s [CURRENT]
Posted: Tue Mar 12, 2013 2:45 am
Hi Ken
A V4 figure with a hair prop and some cloths on my system is only around 15 grayscale slots, so I wonder if you are using some specific which is using up all the slots? I also use a turbulence node instead of bump map on my skin materials, so the requirement drops.
Good suggestion. I'll include this in the next release. Also, no card has less than 32 grayscale slots. ALL pre-600 series cards have 32 grayscale slots.
At the moment - if you change a "glossy" to a "diffuse", the texturemap names are retained. However you are correct, changing a "floatimage" to an "image" does not retain the maps (and it should). I will fix this in the next version.
Paul
A V4 figure with a hair prop and some cloths on my system is only around 15 grayscale slots, so I wonder if you are using some specific which is using up all the slots? I also use a turbulence node instead of bump map on my skin materials, so the requirement drops.
SUGGESTION 1: Octane plugin should have an option to convert selected "floatimage" into an "image" node whenever possible to save grayscale slots. I have only 32 slots, and other users with lesser cards might have even less.
Good suggestion. I'll include this in the next release. Also, no card has less than 32 grayscale slots. ALL pre-600 series cards have 32 grayscale slots.
SUGGESTION 2: When a material node that uses a texture map is changed to another node type that also requires a texture map, the current one should be automatically reused. In my attempts, I am asked to go hunt for whatever texture map was there before from a long list or from disk.
At the moment - if you change a "glossy" to a "diffuse", the texturemap names are retained. However you are correct, changing a "floatimage" to an "image" does not retain the maps (and it should). I will fix this in the next version.
Paul