I don't recall finding a good solution to this - pretty sure we are still just rendering things like depth as outDepth.r/g/b etc

An image plane name of depth.Z is turned into depth_Z (which is good for the vector types, but unfortunate for the float type). The replacement may be patchable somewhere in Houdini's python, somewhere like houdini/soho/python2.6/IFDframe.py - but I have not looked into this..

I don't think I ever contacted SideFX's support about this - would be worth doing

On 11/05/13 06:58, Michael Garrett wrote:
I meant to say "image plane", not "image place"....

On 10 May 2013 17:27, Michael Garrett <[email protected]
<mailto:[email protected]>> wrote:

    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]
    <mailto:[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] <mailto:[email protected]>
        rising sun pictures | www.rsp.com.au <http://www.rsp.com.au>
        _______________________________________________
        Nuke-users mailing list
        [email protected]
        <mailto:[email protected]>,
        http://forums.thefoundry.co.uk/
        http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users




--
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

Reply via email to