Houdini ocean geo cache render issues

corella
Posts: 7
Joined: Thu Aug 27, 2020 9:11 pm

Re: Houdini ocean geo cache render issues

Post by corella »

I am not sure if we are talking about the same thing.
If I use the $HIPNAME variable in a Redshift ROP an have it create a directory and the actual scene name is "testscene", Redshift will create a directory named /testscene/ automatically.
If I submit the same scene with the same variable through Afanasy it will tell me the directory does not exist, even if Redshift had created it already. When I click "create" in the warning dialog from Afanasy and Afanasy will create a directory called /testscene.hiplc/.

As you can see Afanasy generates a different string from the variable than Houdini or Redshift would. So when a cache directory path contains the $HIPNAME variable (like $HIP/$HIPNAME/xxxxx.bgeo), Houdini/Redshift would look for /sim/testscene/xxxxx.bgeo but when submitted through Afanasy it would look for /sim/testscene.hiplc/xxxxx.bgeo which does not exist.

I have the render from temporary file option turned off, so that is not it.

Look here. All directories with ".hiplc" are created by Afanasy. The other are creatd by Houdini/Redshift:
Image
User avatar
timurhai
Site Admin
Posts: 663
Joined: Sun Jan 15, 2017 8:40 pm
Location: Russia, Korolev
Contact:

Re: Houdini ocean geo cache render issues

Post by timurhai »

Hi.
Afanasy checks images output folder for existence on submit, and when it does not exist, it tries to create it.
There can be some cases, when this check is not needed, when Afanasy can't find out correct output folder, when you using takes for folder and so on.
You can disable this feature too.
Uncheck "Check Output Folder" checkbox.
Timur Hairulin
CGRU 3.0.0, Ubuntu 18.04 LTS, MS Windows 10 (clients only).
corella
Posts: 7
Joined: Thu Aug 27, 2020 9:11 pm

Re: Houdini ocean geo cache render issues

Post by corella »

Yes I know that. That is not the issue. The issue is the name that Afanasy assigns when it creates the folder, which has the extension of the scene file. That is wrong. It should not have the extension of the file name. The fact that Afanasy interprets the $HIPNAME variable as the scene file name including the extension is what seems to cause a variety of issues when trying to load cache file that have the $HIPNAME variable in the path.
User avatar
timurhai
Site Admin
Posts: 663
Joined: Sun Jan 15, 2017 8:40 pm
Location: Russia, Korolev
Contact:

Re: Houdini ocean geo cache render issues

Post by timurhai »

It seems that I don't understand you.
Afanasy does not deal with file extensions and $HIPNAME variable.
It just can check vm_picture folder for existence, and create it. And can save scene to temp file to render.
So I do not understand what is going on.
If you want, you can describe all your and Afanasy movements step-by-step.
Timur Hairulin
CGRU 3.0.0, Ubuntu 18.04 LTS, MS Windows 10 (clients only).
User avatar
timurhai
Site Admin
Posts: 663
Joined: Sun Jan 15, 2017 8:40 pm
Location: Russia, Korolev
Contact:

Re: Houdini ocean geo cache render issues

Post by timurhai »

O, Sorry!

I have checked everything.
Not submission script, but script that renders sets HIP and HIPNAME variables!
https://github.com/CGRU/cgru/blob/maste ... _af.py#L57

I will check this code!
Most probably it is obsolete and do not needed.
Timur Hairulin
CGRU 3.0.0, Ubuntu 18.04 LTS, MS Windows 10 (clients only).
User avatar
timurhai
Site Admin
Posts: 663
Joined: Sun Jan 15, 2017 8:40 pm
Location: Russia, Korolev
Contact:

Re: Houdini ocean geo cache render issues

Post by timurhai »

Can we return to the question about to bake HIP variable in the command or in environment?
This way, on submit temporary scene will be rendered, artists can continue changing original scene, but caches and images will use original HIPNAME.
Timur Hairulin
CGRU 3.0.0, Ubuntu 18.04 LTS, MS Windows 10 (clients only).
Post Reply