I was trying to use the component builder and I ran into the following, perhaps I'm misunderstanding something here.
I have a large .usda file. I want to split it into assets chairs, tables etc and do lookdev on them. The models came with UVs. I'm doing the following inside the component builder:




I Import and unpack, my UV's are untouched.



I make a group and prune everything but the chair, my UVs are still intact.

I move out, and in my setting I'm set up to keep all attributes, but the UVs are gone.


What am I doing wrong here?

I'll try to get those as binary to see if that will solve it. Thanks.

This is an odd one. I can read some exported files from C4D and some don't. All files were exported the same way, the only thing I can guess is that might have to do with file size. The smaller sub 1Gig files open fine, I have a 4 gig one that won't open. I can open the file just fine in a PC.
I'm on 19.5.640 on OSX 12.2.1 The error is attached in an image.

Actually I didn't add the normals yet because I was having this problem. I think is the geometry. The file was exported from Cinema4d. I'm surprised XPU can handle it, but CPU can't. Or maybe is that XPU is ignoring bad geometry and CPU is rendering it properly.

This renders are from 19.5.640, CPU first, I gamma them up so we could see better:

Sure thing, will do. Thanks.

I have an odd situation. I have a large USD file that I'm splitting into assets and doing lookdev as I go. When I render in XPU everything looks as I would expect it, but with CPU I get odd behavior, images below ,the first image is the CPU render. I'm on Houdini 19.5.368 on an M1 mac. The setup is really simple, any ideas?

This is all I have in my .env and it works fine. I would guess the same for custom builds. I'm on OSX.


HOUDINI_PATH = "/Applications/redshift/redshift4houdini/19.0.589;&"
PXR_PLUGINPATH_NAME = "/Applications/redshift/redshift4solaris/19.0.589"

Hello,
I was given some Redshift proxies for rendering. When I bring them into the SOP context with Redshift Proxy everything works fine. I set up my Houdini to use Redshift as one of the Hydra Delegates, but when I try to use the same proxies in Solaris there's missing geometry and the model is gray. How do we go about using the proxies so I get the same thing in Solaris I was getting before. I can't find any literature about it anywhere.
Thanks.

s88ng
running on M1 mini here
heightfields are funky, other stuff seems to be working more or less okay.

But definitely don't update, that's how macOS updates are, Easter is about right time to upgrade the system.
Sad but true.

Can you use Solaris with any of the render engines OK with the M1?

SideFx folks did some troubleshooting and this is fixed by adding the $HFS variable in the HQueue render rop under “Target $HFS”, which should be pointing to wherever your installation is present.

Can we get an answer from Sidefx on this please? Over a year and a half to answer the question? I have the same problem setting up HQueue so this seems to be an oversight in their installer for some reason.
My setup:
Linux Mint 19.3
Houdini Indie 18.0.566
Houdini installed with the launcher, HQueue installed manually from downloaded files. For some reason the launcher won't let me install the server:


Nothing happens when I click on: “Choose another version”

In my path:


In my installation directory:



Error from HQueue:



In HQueue properties “view”

“hythonCommandsLinux”: “export HFS=\”/opt/houdini/Houdini18.0.566/bin\“ && cd $HFS && source ./houdini_setup && hython -u”,
“pythonCommandsMacosx”: “export HFS=\”/opt/houdini/Houdini18.0.566/bin\“ && $HFS/Frameworks/Python.framework/Versions/2.7/bin/python”,
“pythonCommandsLinux”: “export HFS=\”/opt/houdini/Houdini18.0.566/bin\“ && $HFS/python/bin/python2.7”,
“pythonCommandsWindows”: “(set HFS=\\opt\\houdini\\Houdini18.0.566\\bin) && (set PATH=\\opt\\houdini\\Houdini18.0.566\\bin\\python27;\\opt\\houdini\\Houdini18.0.566\\bin\\bin;!PATH!) && echo Accessing \”!HFS!\\python27\\python2.7.exe\“ … && \”!HFS!\\python27\\python2.7.exe\“”,
“mantraCommandsLinux”: “export HFS=\”/opt/houdini/Houdini18.0.566/bin\“ && cd $HFS && source ./houdini_setup && $HFS/python/bin/python2.7 $HFS/houdini/scripts/hqueue/hq_mantra.py”,

Any help would be appreciated.

I also just found out about the Linux Appimage version of RizomUV. I tried it with that as well in the bridge, it doesn't work.

I'm on Linux and using Wine to run RizomUV, which works fine, although I can't get it to work from within Houdini. Any chance of taking a look at this for those of us that don't use macOS or Windows?
Thanks.

Hi,
I've created a rig with Autorig, after rig generation I go to the geo_skin node to do the capture but when I set the display flag to bonedeform1 I get:
Error: Invalid Max Size constraint (can't be 0).
Any ideas?

I tried the simple biped and simple male and female and it seems like the pose library is broken for recording new poses. It works fine with the poses that came with the characters, but any new poses get recorded incorrectly, so I can concur with your assessment unless I'm doing something wrong as well.

Mmm…Mine turn on at the most inopportune times. There might be something going on with our in-house software. I'll investigate.
Thanks,
Steven

Hi guys and gals,
I want to turn off Autotakes and don't ever want it on unless I explicitly tell it to. How do I do that?
Thanks in advance,
Steven

Hi everyone,
Is there a tutorial somewhere on Houdini's take on sequence level lighting. The way it would be done by a team. A lead doing sequence lighting publishing light rigs and juniors doing the shots and modifying when necessary etc, Katana style. I'm not sure what's the best approach for this in Houdini. Any help would be appreciated.

Here you go:
https://www.sidefx.com/tutorials/getting-started-with-hqueue/ [www.sidefx.com]

Best regards,
Steven