[Sidefx-houdini-list] PC cache from Mantra into SOP space?

Peter Bowmar pbowmar at gmail.com
Wed Aug 20 00:25:32 EDT 2008


Oh, nevermind, to reload it I _also_ transform space:camera to
space:world. Duh. I hate spaces transforms :) All is well, nothing to
see here, move along, move along.

Cheers,

peter B

2008/8/19 Peter Bowmar <pbowmar at gmail.com>:
> Hi Jason,
>
> Yep, this works great for pcwrite() to get it into Houdini. However,
> when I try to use pcopen using:
>
> Pin = ptransform("space:world","space:camera",P);
>
> then a pcfilter() it doesn't work, I just get black back.
>
> If I remove both transforms (out and in) then it works fine. This is
> what I faced before, and why I ultimately took off the xforms,
> sacrificing the ability to load the .pc correctly into Houdini for the
> Mantra render turning out correctly.
>
> I'll post an example on Odforce at some point, perhaps I'm thinking
> about the Pin wrong...
>
> Cheers,
>
> Peter B
>
> 2008/8/18 jiversen <jiversen at rhythm.com>:
>> Hey Peter,
>>
>> I've found that if you write your point cloud in world space, it behaves
>> as expected when I import it into SOPs.
>>
>> ...
>> Pout = ptransform("space:camera","space:world", P);
>> Nout = ntransform("space:camera","space:world", nN);
>> rval = pcwrite(fname, "interpolate", 1,
>>                           "P", Pout,
>>                           "N:vector", Nout,
>>                            attrname, attrval     );
>> ...
>>
>> Mario Marengo wrote:
>>> On Saturday 16 August 2008 11:33:36 pm Peter Bowmar wrote:
>>>
>>>> Hi,
>>>>
>>>> So, trying to load in a PC file written from a pcwrite() in mantra, into
>>>> SOPs.
>>>>
>>>> It all works except it's in the wrong space :(
>>>>
>>>
>>> Hey Peter,
>>> Hard to tell what might be going on without knowing the transformations used
>>> when writing out the cloud...
>>> I just did a quick test writing with both camera->world and camera->object and
>>> reading back into both an unparented object and one parented to the camera
>>> respectively, and it all seems to line up.
>>>
>>> Why do you need the optransform() again? (remember that a camera->object
>>> transform at the pcwrite() call should give you this implicitly -- basically
>>> saying "put it where it came from"... unless I'm misinterpreting what you
>>> wrote).
>>>
>>>
>>
>> --
>> jason iversen
>>  fx supervisor
>>    r+h
>>
>>  is this awesome? (y/n)
>>
>>
>> _______________________________________________
>> Sidefx-houdini-list mailing list
>> Sidefx-houdini-list at sidefx.com
>> https://lists.sidefx.com:443/mailman/listinfo/sidefx-houdini-list
>>
>



More information about the Sidefx-houdini-list mailing list