Nathan Apffel

Nathan Apffel

About Me

Long time Animator Learning Houdini
EXPERTISE
Generalist

Connect

LOCATION
Chicago, United States
WEBSITE
https://pntln.com

Houdini Skills

Availability

Not Specified

Recent Forum Posts

Labs exoside Quadremesher Nov. 6, 2024, 10:57 p.m.

Any change the labs team could fix the quad remesher node so it works with tops? specificality in a setup with the hda processor.
It fails and give an error like this:
ERROR: Node failed to cook:
Invalid source /obj/A_0/exoside_quadremesher3/python1.
(Error: Error generated by Python node.
Error: Remeshing failed. (BadInput)).
Deleting node '/obj/A_0'
ERROR: Failed to cook .hda
Blender has a plugin that will batch process quad remesher but It would be better to have it in Houdini.
I know sidefx is still working on a quad remesher that will replace the exoside one but it would still be helpful if I could get it to work with tops.
thanks for your consideration.

package file that points to shared packages folder Dec. 18, 2023, 10:29 p.m.

edward
Why do you need to run "hconfig-bin -a" instead of "hconfig -a"? Try starting Houdini from your shell using "HOUDINI_PACKAGE_VERBOSE=1 houdini -foreground". You should be getting some output, including a line that says "= = = Houdini Package log = = ="
thanks for clarifying. I got the package log this time.

package file that points to shared packages folder Dec. 18, 2023, 12:45 p.m.

edward
Are you launching Houdini from the shell? With HOUDINI_PACKAGE_VERBOSE=1, that should give you a detailed log in the shell for what/where it loaded packages from.
Oh thanks, I hadn't been launching from the shell.
when I do I don't get any info about packages even though HOUDINI_PACKAGE_VERBOSE=1
when I do hconfig-bin -a from the shell I see its calling the package files from the default location in the home folder. even with HOUDINI_PACKAGE_DIR = mnt/Z/Framework/houdini

this is the log from the shell on launch. (aparetly i have an issue with ocl devicetype)
No OpenCL platform has the specified device type (HOUDINI_OCL_DEVICETYPE): GPU.
  Falling back to built-in CPU OpenCL driver (see HOUDINI_USE_HFS_OCL)
No OpenCL platform has the specified device type (HOUDINI_OCL_DEVICETYPE): GPU.
  Falling back to built-in CPU OpenCL driver (see HOUDINI_USE_HFS_OCL)

I appreciate your help here. If you know of any other variables i can change to get useful output or to make houdini look for package files where i tell it to, that would be welcome.

thanks
VIEW ALL POSTS