SUMMARY
This article describes the recommended way of testing your Frame Server setup to ensure it is using networked workers and not local processes.
Information on troubleshooting different issues can be found in the following article:
Q100080: Troubleshooting Frame Server issues on external machines
MORE INFORMATION
1) Disable the local Frame Server processes to confirm that your setup is exclusively using network workers.
To do this, please change the following setting in Nuke on your main machine to a value of 0:
Edit > Preferences > Threads/Processes > frame server processes to run
This setting specifies the amount of Frame Server processes on your local machine, the default value is based on half the number of available CPU cores. Changing the value to 0 will prevent any local Frame Server processes from being created.
NOTE: Please restart Nuke before moving to the next step so the Preference is correctly applied.
2) Check if any network workers are connected to the main machine and are functioning correctly.
Launch Nuke and run the following lines in the Script Editor:
from hiero.ui.nuke_bridge.FnNsFrameServer import frameServer
for worker in frameServer.getStatus(1).workerStatus:
print(worker.address)
Any process shown should be a networked process, as the local Frame Server processes were deactivated in step 1.
3) Render a Write node to test if the Frame Server is able to render correctly.
If the Frame Server render is successful and you would like to use your main machine in addition to the network workers when Frame Server rendering, change the frame server processes to run Preference from step 1 to a value greater than 0.
FURTHER READING
Please visit the following links for additional information on the Frame Server:
We're sorry to hear that
Please tell us why