Misaligned buckets

[vlado]

Eh, it's rendering grey, or with misaligned buckets? The issues are separate, so which one are we talking about?

Best regards,
Vlado

[simmsimaging]

Sorry - I may be mixing two threads by accident, but I am getting buckets rendering in grey/black from one of the nodes. I thought I'd caught reference to that somewhere in this thread and thought that was what this one was about too.

b

[simmsimaging]

Just wondering if anyone had figured out how to get around this one yet. I removed the updates and it did not seem to help.

Thanks!

b

[RErender]

Just wondering if anyone had figured out how to get around this one yet. I removed the updates and it did not seem to help.

Thanks!

b

You don't have increment on save turned on, do you?

[simmsimaging]

You don't have increment on save turned on, do you?

Not that I am aware of - where would that option be found? It's definitely not something that I was aware of turning on, and one or two files that rendered fine with DR now render with grey buckets from one node.

Thanks for the help!

b

[RErender]

It is in the files tab of the Max customize settings, sorry though, I see you are having gray buckets, not the misaligned ones. Gray buckets are usually a network issue, running the spawner as a service is somewhat fickle, if they are running as a service you might try running as an exe instead.

[simmsimaging]

Thanks - my mistake for jumping in on the wrong DR problem thread I will check the spawner, but I'm pretty sure I was running it as an .exe file already.

b

[simmsimaging]

Thanks RErender - made sure to remove the service and run the .exe and it seems to have fixed things. Many thanks.

b

[stevesideas]

Was a solution to the misaligned buckets when using DR ever found ?

[pascalls]

Not that i am aware of. We had missaligned bucket with sp1 but since we moved to sp2 the issue has not occured.
Regards

[simmsimaging]

So far I have resolved it several ways:
- making sure network drives are accessible to all machines (didn't find any difference with UNC paths though)
- makings sure all machines have same plugins
- running the spawner manually and NOT as a service

On a more case-by-case basis:
- rebooting the spawners
- rebooting all machines
- banging repeatedly on the monitor and/or chanting "come on, you can do it... come on....."



b

[pascalls]

So far I have resolved it several ways:
- making sure network drives are accessible to all machines (didn't find any difference with UNC paths though)
- makings sure all machines have same plugins
- running the spawner manually and NOT as a service



b

We did all that and the problem was reoccurring on a random basis. Restarting spawners resolved issue...