ivguerrero

I have a point node where input geo colors (which are 0-1), are being pushed into a range from 0-10.  When I sample the values with a display component, they look correct; however, when I plug the point node into a mesh.inMesh connection, the values get clamped to a value of 1.

geo.worldMesh[0] --> pointNode.outGeometry --> newGeo.inMesh
rgbaPP(0-1)                       rgbaPP(0-10)                        rgbaPP(0-1)

Is the default color set being created by maya to hold the color data being clamped by default?  I don't recall having this behavior before.

I'm using maya2017 with version of SOuP released March 24, 2017.  The mesh was originally created with MASH in maya 2017 using the color modifier, but the color was further manipulated with SOuP.

Thanks in advance.

 

Quote 0 0
ivguerrero
Attaching example scene.  Note there are 2 display components nodes, one for the data coming from the Point node, and one for the mesh that's fed from the point node.
Quote 0 0
pshipkov
That souds strange.
Will check and let you know.
Until then, there was a way to specifiy if color set is clamped. Not in front of Maya right now, so cannot remember where exactly that settings was.
Quote 0 0
ivguerrero
Yup, there is a way to specify if color set is clamped or not.
The one I found was using the polyColorPerVertex node, which has clamp attr. I tried inserting that node in between the point node and the mesh and setting to unclamped, however the rgaPP values remained clamped.  I should add that this behavior only seems to happen with colors produced in MASH generate mesh (even if duplicated and history deleted on it).
Quote 0 0
pshipkov
Checked early today.
Maya is clamping the colors internally.
There is nothing i can do about it.
Will flag it to the Maya developers.
If you want to render the data, better supply it as a varmap.
Quote 0 0