> Chris from A52 writes [paraphrased]:
>
> We just installed Realflow 2012, but it's crashing on our renderfarm
> with this error:
>
> > --- snip
> > Executing: RealFlowNode -range 0 200 //disks/nas0/CGI/R_n_D/work.chrisj/realFlow/arrowhead/flowTest/flowTest.flw
> >
> > This application has requested the Runtime to terminate it in an unusual way.
> > Please contact the application's support team for more information.
> > --- snip
>
> Sometimes we see a windows crash dialog on the render node's desktop.
> We set these two variables at the top of submit-realflow:
>
> # WINDOWS
> $ENV{RFPATH} = "C:/Program Files/Next Limit/RealFlow 2012";
> $ENV{PATH} = "$ENV{RFPATH};$ENV{PATH}";
>
> Although it crashes through rush, if we run the same "RealFlowNode"
> command in a new DOS window with those same settings, it runs fine.
Solution: restart the rushd service after installing Realflow.
Usually when something works in DOS but the same command
fails in Rush, its an environment variable or user context issue.
After some investigation, we found that RealFlow 2012
sets this variable as part of its install:
RF_2012_PATH=C:\Program Files\Next Limit\RealFlow 2012
But it will CRASH if the variable is not set.
If you don't restart the rushd service after the install,
and don't set this variable in the submit script,
you'll get the crash.
Restarting rushd causes it to pick up the new variable change
from the RealFlow install, and it will then run normally.
I requested they report this as a bug to the folks at NextLimit;
RealFlowNode should really check if the variable is unset
and print an error message instead of crashing.
|