I’m just starting to experiment with Deadline as an option for renderfarm management on my Mac-based setup. As yet, though, it seems to be giving me some trouble on my pre-existing, and working, renderfarm. I have the repository set up and the slaves can see it. Jobs can be submitted from Lightwave or Deadline and show up in the repository and the slaves respond - except that there seems to be no way to set the path to the ScreamerNet executable - I just get the same error on all nodes that the LightWave executable cannot be found and so no rendering occurs.
I haven’t seen a way to set the path in any of the dialogs presented for job submission and the documentation seems to make no mention of how to configure this aspect of things. Can some kind soul point me in the correction direction, please?
Mono 2.4.2.3 is installed on all machines (and all are running OS X 10.6.2).
UPDATE : Found the information in the documentation, but seem to have forgotten the superuser password and I cannot find information as to how one might reset it.
Ahah. Well I appear to have screwed up the superuser password, so cannot get in to that panel. I wonder how one resets that.
In the meantime, I poked around and found that a list of executables for ScreamerNet were defined in Lightwave.param in the repository plugins folder. Despite adjusting the LW9 path there to be correct, I’m still unable to get the slave to start up ScreamerNet. I still get the error shown in the attachment.
I’ll send you a private message on how to reset the super user password. In the meantime, when you submit a lightwave job, try setting the build option to None instead of 32 bit to see if that helps.
Also, we’ve made a lot of improvements to the mac version in Deadline 4.0, which is currently in beta. Since you’re just starting to experiment with Deadline, it might be worth taking a look:
viewtopic.php?f=10&t=2778
Cheers,
Superuser password reset, and app paths configured. We get nearer to a working system, but it seems that we go wrong now when the scene is loaded. ScreamerNet reports success, but loads the ‘scene’ far too quickly and then blasts through outputting blank frames.
To check this out further, I fired up Layout on the machine holding the repository. That has a working ScreamerNet setup and it finds ScreamerNet running in a terminal with no issues at all. Asking Layout to send the Deadline generated scene mentioned in the Slave output to the nodes would appear to work fine, but the terminal output shows what is going on (and this is for some reason not fully reported in the Deadline Slave application - see the attached screenshot). Basically, we have a file access problem and nothing works from here on out :
LightWave command: load.
sendack: Loading
Loading “:private/var/folders/DB/DBihMNEqG0yHF0hTOqKl1++++TQ/-Tmp-/aliensnubfightersovercolony_cameraindome-v2_hdi-plants_deadline.lws”.
Unable to access the scene file.
LightWave command: wait.
sendack: Ready
LightWave command: render.
sendack: Rendering frame 1
Allocating frame buffers.
Allocating segment buffers.
Frame: 1.
Segment: 1/1.
Pass: 1/1.
Updating geometry.
Rendering frame 1, segment 1/1, pass 1/1.
Image Reconstruction.
Image Reconstruction : 0%.
Image Reconstruction : 1%.
Image Reconstruction : 2%.
Image Reconstruction : 3%.
Image Reconstruction : 4%.
Image Reconstruction : 5%.
Image Reconstruction : 6%.
Image Reconstruction : 7%.
Image Reconstruction : 8%.
Image Reconstruction : 10%.
Image Reconstruction : 11%.
Image Reconstruction : 12%.
Image Reconstruction : 13%.
Image Reconstruction : 14%.
Image Reconstruction : 15%.
Image Reconstruction : 16%.
Image Reconstruction : 17%.
Image Reconstruction : 18%.
Image Reconstruction : 20%.
Image Reconstruction : 21%.
Image Reconstruction : 22%.
Image Reconstruction : 23%.
Image Reconstruction : 24%.
Image Reconstruction : 25%.
Image Reconstruction : 26%.
Image Reconstruction : 27%.
Image Reconstruction : 28%.
Image Reconstruction : 30%.
Image Reconstruction : 31%.
Image Reconstruction : 32%.
Image Reconstruction : 33%.
Image Reconstruction : 34%.
Image Reconstruction : 35%.
Image Reconstruction : 36%.
Image Reconstruction : 37%.
Image Reconstruction : 38%.
Image Reconstruction : 40%.
Image Reconstruction : 41%.
Image Reconstruction : 42%.
Image Reconstruction : 43%.
Image Reconstruction : 44%.
Image Reconstruction : 45%.
Image Reconstruction : 46%.
Image Reconstruction : 47%.
Image Reconstruction : 48%.
Image Reconstruction : 50%.
Image Reconstruction : 51%.
Image Reconstruction : 52%.
Image Reconstruction : 53%.
Image Reconstruction : 54%.
Image Reconstruction : 55%.
Image Reconstruction : 56%.
Image Reconstruction : 57%.
Image Reconstruction : 58%.
Image Reconstruction : 60%.
Image Reconstruction : 61%.
Image Reconstruction : 62%.
Image Reconstruction : 63%.
Image Reconstruction : 64%.
Image Reconstruction : 65%.
Image Reconstruction : 66%.
Image Reconstruction : 67%.
Image Reconstruction : 68%.
Image Reconstruction : 70%.
Image Reconstruction : 71%.
Image Reconstruction : 72%.
Image Reconstruction : 73%.
Image Reconstruction : 74%.
Image Reconstruction : 75%.
Image Reconstruction : 76%.
Image Reconstruction : 77%.
Image Reconstruction : 78%.
Image Reconstruction : 80%.
Image Reconstruction : 81%.
Image Reconstruction : 82%.
Image Reconstruction : 83%.
Image Reconstruction : 84%.
Image Reconstruction : 85%.
Image Reconstruction : 86%.
Image Reconstruction : 87%.
Image Reconstruction : 89%.
Image Reconstruction : 90%.
Image Reconstruction : 91%.
Image Reconstruction : 92%.
Image Reconstruction : 93%.
Image Reconstruction : 94%.
Image Reconstruction : 95%.
Image Reconstruction : 96%.
Image Reconstruction : 97%.
Image Reconstruction : 99%.
Frame completed.
Last Frame Rendered: 1.
Rendering Time: 0.7 seconds.
Freeing segment buffers.
Freeing frame buffers.
We’ve made some adjustments to the Lightwave plugin in 4.0 beta that should resolve these problems. We’ve received your beta request (will respond shortly), so it would be great if you could test this out for us. This fix will be included in beta 9, which we’ll try to get out this week.
Cheers,
