janjansen

janjansen

About Me

Connect

LOCATION
Not Specified
ウェブサイト

Houdini Skills

Availability

Not Specified

Recent Forum Posts

OCIO editor doesn't save state with custom config 2024年3月28日17:16

jsmack
I downloaded that config and manually added the default view line and then put the path to the config in the ocio.json package, and I'm seeing the tcamv2 view preselected in the viewport on startup. Is that not what you see?
I went 2 ways
- initially added the path to the config to the houdini.env file
- then tried the same path through as the OCIO varibale through a sys env variable
both ways led to the config being read, but left me unable to change the default view transform (it did add the default part to the (houdini created) config however but restarting houdini removed/changed it again for some reason). so removing the variable before restarting houdini was 'a' solution for the time being
guess i could try going through the ocio.json file instead - thanks again for your input!

OCIO editor doesn't save state with custom config 2024年3月27日20:47

jsmack
It's not trivial, the config would have to be redesigned.
looks like houdini does indeed do that work for me


jsmack
correct, the editor uses this location by default to save the edited config. Houdini is directed to use this config via a package file--this possibly overrides any preexisting environment variable defined location.


thanks much for your input, i def learned something along the way. my take is now that houdini keeps converting the v1 OCIO I have in the sys env upon start up and thus overwrites whatever display transform I chose every time.
(I could probably use the houdini generated config now and copy it back to my sys env location to verify)

thanks again!

OCIO editor doesn't save state with custom config 2024年3月27日19:56

I am guessing this is some kind of houdini bug(?) - or some clunky behavior in how to deal with old OCIO configs

- I now disabled my sys env variable
- copied the relevant cube files into this directory C:\Users\<my_user>\Documents\houdini20.0\ocio (same path i now see the houdini-made OCIO getting sourced from) and it all works. only problem I now have is that my OCIO for houdini isn't getting used system wide but rather only for houdini

- remaining question: is houdini able to deal with the look (!<Look>) CDL transforms in the viewport somehow?
- be great to read up how it's intended to work (and expected to be set up)

thanks all