slave spawner restart looping

I had a power failure and now a slave is not loading max in slave mode properly.

the spawner runs fine from start up and the icon is in the bottom right but 3dsmax.exe just loads and crashes and loads and crashes endlessly.

i uninstalled max 9 and vray and reinstalled both and its still having the same problem.

any ideas short of reformatting?

info: not registered max or vray licenses as they are just slaves - max 9 64 xp64 and vray 64 rc3.

Try running a normal backburner rendering with the slave and see if it fixes it.

Best regards,
Vlado

i dont normally use backburner

but i tried to use it anyway - the server is seen by the manager and by the monitor but when i submit the job it does not see the server in the list..

so the slave just sits there without picking up the idle job :frowning:

fixed it with a full rebuild :frowning:

i wonder what broke, something in windows .net or direct x i imagine?

I’m having the same problem.

What do you mean by “full rebuild”, if you have already uninstalled/reinstalled max and vray?

i mean the extra fun type: rebuilt windows from a formatted drive.

totally clean.

Try the following:

On the fresh installed MAX 8(9) machine(s), run the BB (Backburner)
Manager. Go through all the setup about subnet and timeouts, etc.
Once it has run normally, close it and try re-running the
VRaySpawner60.exe

In Short - just open the Manager and click < OK >.

Best regards,
nikki Candelero

so I uninstalled backburner on my render slave, took off previous versions of max, and reinstalled backburner. Then ran the manager as you suggested, then started the vraydummy file, and it worked!

But, I then go to my workstation, bring up a max file, click DR, type in the name of my slave and hit resolve successfully, then start the render. The vray message box shows that it sent to the slave, but the slave never joins in (and I increased the render detail/size so that it would have time to join in).

And after finished, it does tell me that "warning: render host unknown (192.168.0,4) is not responding.

Am I missing one last step?

Thx!

Doh!!!

I’m a big dummy.

I accidentally was using max 64 on my workstation instead of max32.

Now it works! :smile: