Love the workflow! Do you setup textures when importing fbx into houdini? How do you apply the animation with the textures applied when importing it back into Blender? I cant seem to get this workflow right. I would import fbx into Houdini and do my simulations then export as fbx but the textures are bot applied and the animation is one mesh.
Yes, I do the UV unwrapping + texturing before exporting to Houdini. Both FBX and OBJ keep vertex data so your UVs will be preserved also when you export back to Blender you just need to make sure you don't delete it before you export (check my videos at the end where you can see what I export) same goes for the one mesh problem, you need to seperate by path in the alembic export node I talk about it in my videos too.
Hi, great idea with the movement. I'm not sure if attribute transfer gives you the correct uv's in this case, since the target geometry is moving, while the source geo is not, and attribute transfer is position based. If you just use the unpack node after the bend, you should see the UV's again, it's not gone :) Also if you want to stay with the packed geo and also see the UV, just write "uv" in the "Transfer Attributes" field on the Assemble node.
oh waw I didn't know that thank you very much for the info, your method is way better. even with moving geo I had correct UVs in blender, weird. Thank you again for the advice, it's noted.
@@aumission It seems in case of packed primitives attribute transfer work a bit different. If you delete the uv attribute between the merge and assemble node, the attribute transfer won't work anymore. Anyway if you are dealing with non-packed primitives and points, attribute transfer won't work correctly if there's difference in transform/size. Attribute copy is the node you can use in those cases, where by default it looks for matching in the ptnum attribute, but you can change it to any attribute you want that you know matches between the two geometry.
![ไลฟ์สุ่ม iPhone 295 บาท... โกงมั้ย?[ โกงมั้ยครับ ep.97 ] | DOM](http://i.ytimg.com/vi/gdstHEE4UUE/mqdefault.jpg)
Nice work, love the lighting in your scene!
Thank you
Love the workflow! Do you setup textures when importing fbx into houdini? How do you apply the animation with the textures applied when importing it back into Blender? I cant seem to get this workflow right. I would import fbx into Houdini and do my simulations then export as fbx but the textures are bot applied and the animation is one mesh.
Yes, I do the UV unwrapping + texturing before exporting to Houdini. Both FBX and OBJ keep vertex data so your UVs will be preserved also when you export back to Blender you just need to make sure you don't delete it before you export (check my videos at the end where you can see what I export) same goes for the one mesh problem, you need to seperate by path in the alembic export node I talk about it in my videos too.
@@aumission great tips! Thank you 🙏🏽
Do you have a discord or contact info I can reach you on for more insight with this?
It didn't work. Can I send you my file?
Hi, great idea with the movement. I'm not sure if attribute transfer gives you the correct uv's in this case, since the target geometry is moving, while the source geo is not, and attribute transfer is position based. If you just use the unpack node after the bend, you should see the UV's again, it's not gone :)
Also if you want to stay with the packed geo and also see the UV, just write "uv" in the "Transfer Attributes" field on the Assemble node.
oh waw I didn't know that thank you very much for the info, your method is way better. even with moving geo I had correct UVs in blender, weird. Thank you again for the advice, it's noted.
@@aumission It seems in case of packed primitives attribute transfer work a bit different. If you delete the uv attribute between the merge and assemble node, the attribute transfer won't work anymore.
Anyway if you are dealing with non-packed primitives and points, attribute transfer won't work correctly if there's difference in transform/size.
Attribute copy is the node you can use in those cases, where by default it looks for matching in the ptnum attribute, but you can change it to any attribute you want that you know matches between the two geometry.
aah I see. Thank you 🙏