- Thu Jun 26, 2008 3:04 pm
#274027
Hi!
My 15 nodes are up and running with win64 and version 1.7.
I've done some tests now, with all nodes in a Co-Op rendering... about 50% of the nodes fails. The message in Maxwell Server is that a texture cant be found, its there though, so there must be something else.
If I start a non co op rendering with the first node, then number 2, number 3, number 4 ect, I can start renders sucessfully until node number 7-8, after that one it starts to fail.
Its not the same nodes that are failing all the time, its totally random.
My server that holds all the textures and MXS files are running win32, and I've installed the patch that pushes up the max numbers of connections.
Are there any timeout setting that can be set in maxwell render?
It feels like server dosnt get an answer from the server with the textures, and directly fails.
Any Ideas?
All the nodes are connected to the same Gbit switch

/ patrik
My 15 nodes are up and running with win64 and version 1.7.
I've done some tests now, with all nodes in a Co-Op rendering... about 50% of the nodes fails. The message in Maxwell Server is that a texture cant be found, its there though, so there must be something else.
If I start a non co op rendering with the first node, then number 2, number 3, number 4 ect, I can start renders sucessfully until node number 7-8, after that one it starts to fail.
Its not the same nodes that are failing all the time, its totally random.
My server that holds all the textures and MXS files are running win32, and I've installed the patch that pushes up the max numbers of connections.
Are there any timeout setting that can be set in maxwell render?
It feels like server dosnt get an answer from the server with the textures, and directly fails.
Any Ideas?
All the nodes are connected to the same Gbit switch

/ patrik
Application & OS: [Maxwell Studio][Ubuntu 14.04]
Workstation: In the build...
Renderservers: Rebus
Workstation: In the build...
Renderservers: Rebus