oliver7
July 17, 2021 17:16:10
I can only tell you about how its intended to work.. its not a "continuous" live link.... the hda builds the instructions, fires it at rizom, which launches, executes the instructions, closes, and sends the result back to Houdini. I build the original HDA before handing it off to labs, and its always been intended to work that way. In the processor, you could turn off autoquit, but for what you are asking for, its not meant for it.
I don't see Luiz's video showing anything different.
Sebastien_Rousseau
April 14, 2022 14:40:34
On my side I try to evaluate it for a game production and each time it send data to rizom, process it and 1 time on 2, it close without sending back the result. I tried version 2020, 2020.1, 2022, same problem. anyone get this kind of behavior and find a fix ?
gabieleer
Sept. 29, 2023 01:02:58
I'm having the same issue. At random times it spits out a proper UV, and later on even in a same setting, it closes Rizom without spitting out any UV. It pops up Rizom UV standalone, and unfold up to 70% or 80% something percent, random every time, and just shuts down. And no UV. Will this be fixed? I can't use this pipeline if I can't figure out why I'm getting this error.
caylakling8
Nov. 17, 2023 01:42:24
Siavash Tehrani
I'm having the same issue as jomaro with rizom 2020.1. Whenever the RizomUV Unwrap node cooks it opens the actual RizomUV GUI application, does its thing, then closes. I haven't used any versions prior to 2020.1 but looking at this video it seems like that shouldn't be the behavior: https://www.youtube.com/watch?v=wuYC1mwNua8 [www.youtube.com] Donkey Kong [donkey-kong.io]
Link not working?
Le_Vitsky
June 26, 2024 10:43:20
I'm having a similar but different issue - I set the path to Rizom, node fires up the app, the app gets in focus, and does nothing (opens the model though). I have to manually press unwrap save and close rizom - and then Houdini unfreezes and loads the model with Rizom's UV's. I know that is better than half of the problems you guys are getting but seems that something is off with the lua script the node generates, need to investigate further...
UPDATE: looked up the log in rizom and got this:
ERROR: Error: The parameter 'ProcessAllIfNoneSelected' is not recognized.
dug into the node, found the python3 node where the ProcessAllIfNoneSelected was located, commented it and got the next set of errors:
ERROR: Error: The parameter 'ProcessNonFlats' is not recognized.
ERROR: Error: The parameter 'ProcessSelection' is not recognized.
if i comment those three lines the node cooks out, but overall i get kinda bad result.
idk what to do with those three parameters, i guess they need to be swapped for new ones but i cant find those commands in the log from rizom
Dobri12
Nov. 24, 2024 09:56:59
Le_Vitsky
I'm having a similar but different issue - I set the path to Rizom, node fires up the app, the app gets in focus, and does nothing (opens the model though). I have to manually press unwrap save and close rizom - and then Houdini unfreezes and loads the model with Rizom's UV's. I know that is better than half of the problems you guys are getting but seems that something is off with the lua script the node generates, need to investigate further...
UPDATE: looked up the log in rizom and got this:
ERROR: Error: The parameter 'ProcessAllIfNoneSelected' is not recognized.
dug into the node, found the python3 node where the ProcessAllIfNoneSelected was located, commented it and got the next set of errors:
ERROR: Error: The parameter 'ProcessNonFlats' is not recognized.
ERROR: Error: The parameter 'ProcessSelection' is not recognized.
if i comment those three lines the node cooks out, but overall i get kinda bad result.
idk what to do with those three parameters, i guess they need to be swapped for new ones but i cant find those commands in the log from rizom
i have the same issue