evan mathis
evanmathis
About Me
EXPERTISE
Generalist
INDUSTRY
Film/TV
Houdini Skills
Availability
Not Specified
Recent Forum Posts
Gamepad Camera with a PS4 controller - the correct mapping Nov. 15, 2025, 2:03 p.m.
I'm adding this here so you don't have to figure it out.
It works great on Linux (I had to get the "joystick" lib first as I'm on Pop_OS) and should be the same on other OSs
when you use the gamepad camera shelf tool, you'll find the setting to re-map here:
/obj/cam1/constraints/devicetransform
It works great on Linux (I had to get the "joystick" lib first as I'm on Pop_OS) and should be the same on other OSs
when you use the gamepad camera shelf tool, you'll find the setting to re-map here:
/obj/cam1/constraints/devicetransform
light linker with prototypes? July 3, 2024, 11:32 a.m.
I've got 3 light linker rules for 3 separate references-
1) A sphere
2) Some text
3) Some animated prototypes from a SOP create node
1 & 2 work fine, but once added to the light linker, the prototypes are no longer lit.
Without the light linker everything is lit just fine.
Any thoughts what I'm f'ing up would be very much appreciated.
(edit) to clarify, if i use the light linker * at all * even having unaffected lights in the scene, the prototypes are unlit.
(edit2) I pulled all of the pieces into a collection via an instancer, (which i probably should have done int he first place) and now everything is lit by one light and not excluded.
1) A sphere
2) Some text
3) Some animated prototypes from a SOP create node
1 & 2 work fine, but once added to the light linker, the prototypes are no longer lit.
Without the light linker everything is lit just fine.
Any thoughts what I'm f'ing up would be very much appreciated.
(edit) to clarify, if i use the light linker * at all * even having unaffected lights in the scene, the prototypes are unlit.
(edit2) I pulled all of the pieces into a collection via an instancer, (which i probably should have done int he first place) and now everything is lit by one light and not excluded.
Localizing reference textures... there has to be a better way March 30, 2024, 7:04 p.m.
Hm. component output isn't working as well as I'd hoped.
But, there is a "modify paths" lop [www.sidefx.com]
It even has * almost * the solution i'm looking for on the manual page:
Change all UsdVolFieldAsset file paths to point inside a volumes subdirectory
And while I can make sense of what that does, I have no clue how to adapt it to my purposes.
But, there is a "modify paths" lop [www.sidefx.com]
It even has * almost * the solution i'm looking for on the manual page:
Change all UsdVolFieldAsset file paths to point inside a volumes subdirectory
if attributepath.endswith('.filePath'): parts = assetpath.split('/') return '/'.join(parts[0:-1]) + '/volumes/' + parts[-1] return None
And while I can make sense of what that does, I have no clue how to adapt it to my purposes.