Still using deadline 3.1sp1
I have an alternate plugin.ini so we can betatest a software that we normally have the stable build intalled. But it doesn’t work.
I checked the commandline of the 3dsmax.exe process to see what deadlineslave used. And that looked ok.
“c:\program files\autodesk\3ds max 9\3dsmax.exe” -p “%temp%\dl.ini” -q -s “deadlineStartupMax.max”
dl.ini:
[include]
original=\slave\pluigns\plugin_beta.ini
dealine lighting=%temp%\lighningplugin12334553453.ini
and I checked and plugin_beta.ini was in the folder mentioned in dl.ini
And thoughts? This is really bumming me out.
Ben.
Hey Ben,
We just tested the alternate plugin.ini feature here, and it appears to be working properly. We set up a simple test scene that uses Brazil and created a plugin.ini file in the repository’s 3dsmax plugin folder that contained the Brazil plugin entry. We submitted 2 jobs for this test scene, one with and one without the alternate plugin.ini selected. Then on the test machine, we removed the Brazil entry from the local plugin.ini file.
The job without the alternate plugin.ini failed because it couldn’t find the Brazil plugin, but the job with the alternate plugin.ini rendered successfully.
Maybe try running the following from the command line to see if your alternate plugin.ini file is read in correctly:
"c:\program files\autodesk\3ds max 9\3dsmax.exe" -p "\\path\to\plugin_beta.ini"
Cheers,
We have a shortcut for the beta plugin that runs that exact commandline. That’s’ how the user launches max with the plugin.
It doesn’t add up. I’m going to try a startup script that will log the pluginpaths.get
b.