> Since Autodesk took over Combustion 4, we noticed that some of our
> machines have Combustion installed in a different location, causing
> our renders to fail on those new machines.
>
> So our old machines have Combustion installed in:
> C:/Program Files (x86)/discreet/combustion 4
> ^^^^^^^^
>
> ..and on our new machines, Combustion is installed in:
> C:/Program Files (x86)/autodesk/combustion 4
> ^^^^^^^^
> Is there some way to set up the submit-combustion script to
> run combustion regardless of which path setting is used?
Yes, you can just cram all the possible PATH settings
into the top of the submit-combustion.pl script, and the
operating system will try them all.
So for instance, find these lines in the submit-combustion script:
if ( $G::iswindows )
{
# WINDOWS
$ENV{PATH} = "C:/Program Files/discreet/combustion 4;$ENV{PATH}";
}
..and change it so that it reads:
if ( $G::iswindows )
{
# WINDOWS
$ENV{PATH} = "C:/Program Files/discreet/combustion 4;$ENV{PATH}"; # discreet product path
$ENV{PATH} = "C:/Program Files/autodesk/combustion 4;$ENV{PATH}"; # new autodesk product path
$ENV{PATH} = "C:/Program Files (x86)/discreet/combustion 4;$ENV{PATH}"; # (x86 versions of above)
$ENV{PATH} = "C:/Program Files (x86)/autodesk/combustion 4;$ENV{PATH}";
}
..and that will try all 4 combos of discreet vs. autodesk,
and with or without the (x86).
Note: due to how we're 'inserting' the directories into the PATH
one at a time, the OS will try finding the executable in reverse
order as shown above, giving precedence to the *last* PATH setting,
and then working upwards. (ie. bottom-to-top as shown above)
The first place the OS finds the executable, it will run it
from that location.
|