Marc-André Belzile


About Me

Not Specified
Not Specified


Recent Forum Posts

Multiple houdini.env files possible? Sept. 19, 2022, 10:37 a.m.

I have tried to create an article regarding that, feel free to have a look, hope it will help.
Article []
The path keyword is a shortcut for appending elements to HOUDINI_PATH, as you pointing out elements are prepended by default. You can have more control on how to set path like this

    "path" : 
            "value" : "/user/bob/libs",
            "method" : "append"

Or with the env keyword like this

    "env": [
            "HOUDINI_PATH" :
                    "value": "$BOB/test",
                    "method": "append"

How to use json file to make Redshift custom builds work? Sept. 8, 2022, 8:26 a.m.

Hello, I have tried to install a Redshift custom build for Solaris and the regular OUT context,
meaning I would like it to work in both contexts.

Houdini/Solaris 19.5.303 plugin for Redshift 3.5.04

Downloadable here: []

Tried it with the houdini.env file, but whenever I open the IPR window, Houdini crashes.
Someone in the comments suggested to use packages instead, but I am not confident modifying the lines myself.
That's what they sent me:

{"REDSHIFT_COREDATAPATH": "C:/ProgramData/Redshift"},
{"PATH": "C:/ProgramData/Redshift/bin"},

Would someone be so kind and explain to me how exactly I need to modify this text for it to work?
I am assuming it doesn't work like this straight away?

Things like: Do I replace {"RS_PLUGIN_VERSION" : "${HOUDINI_VERSION}"} with the exact version, like "Houdini/19.5.303"
Or is the advantage of packages that this is not necessary?

The only lines you need to modify are REDSHIFT_COREDATAPATH and PATH with the redshift installation path on your machine. Place the above in a .json file under $HOUDINI_USER_PREF_DIR/packages.

Viewer state type conflict: kinefx Sept. 5, 2022, 6:01 p.m.

This issue was fixed with 19.5.354