Hi Ben, We're having this issue right now and I'm wondering if you found a satisfactory solution. I thought maybe we could do a bit of hand written vex code using a vex code node (not exactly sure here but guessing based on RSL conventions...) that would force a float data type to be stored in a variable name that we would want.
Also, does having a period in the image plane name screw it up? Like can you just name a "depth" image place "depth.Z"? Probably not, that would be too easy. Thanks, Michael On 21 December 2011 05:41, Ben Dickson <[email protected]> wrote: > In a Mantra node, if I output some variable as a "VEX Type: float type", > > http://i.imgur.com/6Ea62.png > > ...then resulting EXR has a channel list like this: > > channels (type chlist): > A, 16-bit floating-point, sampling 1 1 > B, 16-bit floating-point, sampling 1 1 > G, 16-bit floating-point, sampling 1 1 > Op_Id, 32-bit floating-point, sampling 1 1 > R, 16-bit floating-point, sampling 1 1 > > This Op_Id channel is read into "other.Op_Id" in Nuke, which seems > reasonable, but you can only see the name in a Copy node (the Shuffle > just shows it very similarly to a red channel of "other"): > > http://i.imgur.com/1FCpz.png > > If I select "vector type" in Mantra, it duplicates the data into Op_Id.r > Op_Id.g Op_Id.b and this shows up nicely in Nuke as a layer, but the EXR > is 3 times as large.. > > Anyone found a good solution to this? > -- > ben dickson > 2D TD | [email protected] > rising sun pictures | www.rsp.com.au > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
