Relative Houdini newbie here so be kind!
I'm trying to set up my environment so I can have site and user configurations sitting on top of the default houdini install. In particular, a custom menu using MainMenuCommon.xml in my studio houdini config path.
If I set my HOUDINI_PATH as follows (in my Shotgun app_launch hook):
houdini_path = z
studio_configs/houdini/15.5os.environ = houdini_path + os.pathsep + ‘&’
when I open Houdini via the shotgun launcher, Shotgun fails to initialise, and using hconfig -ap my Houdini_path looks like :
“Z
dev/users/joe.bloggs/repos/hvhoudini/15.5;&Z
dev/users/joe.bloggs/repos/hvhoudini/15.5;&”if I don't set the HOUDINI_PATH, then when I launch Houdini and run hconfig -ap, the Houdini_path is :
HOUDINI_PATH := “c
users/joe.bloggs/appdata/local/temp/tk-houdinivsmfzt;Z
dev/release/shotgun/studio/install/app_store/tk-houdini/v1.0.10/startup;&Z
dev/users/joe.bloggs/repos/hvhoudini/15.5;&”With this config, I DO get Shotgun, but I don't get the menus I've defined in Z
dev/users/joe.bloggs/repos/hvhoudini/15.5/MainMenuCommon.xmlSome observations.
- In the first test, the Houdini path has two copies of the path + ‘&’ path that I only defined once in my app_launch hook.
- In the second test, there is an unusual space after the HOUDINI_PATH when running hconfig.
I think I am approaching this the correct way, and my feeling is that there might be a bug with the Shotgun engine where it appends the Shotgun paths to any existing paths in HOUDINI_PATH. I will post a ticket with SG as well as this post to see if they can see where the problem lies.
Does anyone have any experience getting a studio HOUDINI_PATH to work alongside Shotgun?
Can anyone see what I might be doing wrong?
Thanks in advance for your help.
Patrick
