This is super handy. Thank you for it. One note to the workflow, would it be possible to resend again object that came from UVLayout already? So instead of having nodes: file->headus_uvlayout1->headus_uvlayout2 you will have just one headus_uvlayout? (having one headus_uvlayout node instead of having two nodes)
Probably best way is to make it: if geo_uvlayout.obj exist, use it instead of geo.obj
martinkindl83 This is super handy. Thank you for it. One note to the workflow, would it be possible to resend again object that came from UVLayout already? So instead of having nodes: file->headus_uvlayout1->headus_uvlayout2 you will have just one headus_uvlayout? (having one headus_uvlayout node instead of having two nodes)
Probably best way is to make it: if geo_uvlayout.obj exist, use it instead of geo.obj
thoughts?
That's a very good point Martin. I will try a few things and see how it goes.
I've added an option to select whether to use the SOP input or an existing _uvlayout file. This way one does not have to go to the file system and delete files in order to use the SOP input again.
I've updated the attachment of the HDA in the first post. Please have a go at it
Hi Andy,big thanks! I'm not a programmer, so I'll describe the problem as much as possible. One guy in russian community(big thanks too Alexander Alehin) found an error related with deadlock in a subprocess. UVLayout stay as zombie process under Linux if you rerun Houdini and start hda once again. The fix is: In Scripts instead of:
Ivan Malishev Hi Andy,big thanks! One guy in russian community(big thanks too Alexander Alehin) found an error related with deadlock in a subprocess. UVlayout stay as zombie process under Linux if you rerun Houdini and start hda once again. The fix is: In Scripts instead of:
thank you for reporting this. If I apply these changes, then Houdini locks (at least on Windows) until I quit UVLayout. Maybe the behavior is different on Linux? Can anybody else using the HDA on Linux chime in on this matter? Until then I'll look into checking based on the OS and branch in the code.
Andy
Edit: Hey Ivan, could you try or pass on the attached HDA and let me know? Thank you.
Edit2: I've removed the attachment, since it causes a lock. See below.
Edit: Hey Ivan, could you try or pass on the attached HDA and let me know? Thank you.
Thank you for feedback,hastened to write before testing Alexander's fix by myself. He said it works perfect for him. But now i am testing and it totally freezes Houdini. So i can't test your os checking too.( I don't know what to do,it remains to wait for other users,i think.) And how you wrote
If I apply these changes, then Houdini locks (at least on Windows) until I quit UVLayout.
from what I read in the Python subprocess docs, I'd expect a lock of Houdini since the Python code calling the subprocess waits for the child process to finish.
I wonder does the quit button on the HDA quit UVLayout on Linux? If so, I wonder what that zombie process is. Have you checked the running processes with ps from a shell?
To quit UVLayout which is started in plugin mode I have to write a file with the same name of the geometry file but with .CMD as extension and its content is ‘kill’. Once that file is written UVLayout detects it and quits itself.
I understood the regularity of the error,it's not about the code. Forgive me for taking away from the truth.) If i start Houdini from desktop shortcut-a zombie process appears. If i start Houdini from console - HDA works perfect.
I think I have fixed the issues with launching UVLayout on the Mac. Please give the attached HDA a try. Once you confirm it's working I'll replace the one in the first post and in the tutorial section.
Thank you all. Andy
I've deleted the attachment and reuploaded to the first post.