Hi JuanJo !
i would have an other question related to this subject, but before that i would like to make a brief sum up of what is working to export different type of geometry from houdini to octane standalone(OS
).Faceted Polygon Object
: Cd / Alpha and any other attributes can be exported as a Point OR Vertex attribute and then read in OS
with color vertex attribute
and greyscale vertex attribute
this method doesn' t work yet with curves object and particles object.Curves Object
: Cd / Alpha and width are the only attributes that can be exported throw the @uv primitive attribute
and @width point attribute
. @width is directly recognised in OS
, but to be able to use @Cd and @Alpha, we need to use your code tricks to pack @Cd and @Alpha into @uv.x and @uv.z. Then to unpack those info we need to use rgb4k_map.ppm
.Particles Object :
@width exported as a point attribute is directly recognised by OS
to control radiusPP (@pscale in houdini). In Houdini @Cd and @Alpha can be stored inside the @uv point attribute
. Again we need your code tricks to pack @Cd and @Alpha into @uv.x and @uv.z. Then to unpack those info we need to use rgb4k_map.ppm
My problem now is that when i try to export particles with @uv at point level
that contain my @Cd and @Alpha, while it works perfectly inside houdini , and while it works perfectly for curves. it looks that OS is unable to understand uv channel on particles
- can you confirm me that in OS
attribute uv is NOT supported for particles , but only for curves and poly objects ?
- uv channel support on particles is a feature that you have created by yourself inside the houdini plugin, that is not inherited from octane core dev ?
- Do you have an idea or method to be able to export the info contain in my @uv attribute inside OS
for particles ?
- In this regards does octane support some .alembic predifined variable like color or similar things ?
it' s a shame that otoy core dev has implemented user data, but have just done half of the work.
generally user data are more useful on curves and particles object type than on poly objects.
so at the end we still need to rely on your clever tricks for most exporting task. i hope you will be able to push the core dev team to update this soon. cause i'm waiting for this feature since 2016 when otoy announced that octane 3.1 that will be ship in fall 2016 will support this.
Thanks again for your great support !
ps : sorry for the whining session, but it's frustrating