- Posts: 36
- Joined: Wed Jun 26, 2019 2:21 pm
- Real Name: Tom Bremer
I think I've seen/looked at everything on the net so far about env variables regarding to fusion. I currently have various paths like macros and scripts pointed to a network share, which is great when I append the share after the default paths in the preferences. And I've recently just installed Reactor to the network share as well and that works swimmingly as well.
We have a several users here that I want them to have the same path mappings without me having to go on each machine and changing each pref by hand. I have a logon script that auto downloads some prefs files for hotkeys and the render node prefs for cryptomatte to work, but I don't have it download the regular Fusion prefs because that saves layout info and people like their windows set differently. Setting the MasterPrefs env variable works, sometimes. I got it to work, but then noticed it would only update in the User section of the path maps. And then after several attempts at changing the prefs file I was pointing to with the env var, it stopped updating when i relaunched Fusion.
So, the question, I guess, is two fold.
1: Do you need to use the FUSION16_MasterPrefs env var in conjunction with FUSION16_PROFILE_PATH to get it to work correctly? Its currently not working for me, though it was.
2: Should the MasterPrefs file that I make overwrite the current ones in the regular prefs file? I thought I read that somewhere.
We have a several users here that I want them to have the same path mappings without me having to go on each machine and changing each pref by hand. I have a logon script that auto downloads some prefs files for hotkeys and the render node prefs for cryptomatte to work, but I don't have it download the regular Fusion prefs because that saves layout info and people like their windows set differently. Setting the MasterPrefs env variable works, sometimes. I got it to work, but then noticed it would only update in the User section of the path maps. And then after several attempts at changing the prefs file I was pointing to with the env var, it stopped updating when i relaunched Fusion.
So, the question, I guess, is two fold.
1: Do you need to use the FUSION16_MasterPrefs env var in conjunction with FUSION16_PROFILE_PATH to get it to work correctly? Its currently not working for me, though it was.
2: Should the MasterPrefs file that I make overwrite the current ones in the regular prefs file? I thought I read that somewhere.