Maxwell Render | Official public forum

Please help
the program use (in co render , network)
old model and old graphics

The only way it can "remember" the old textures is if it is reading a path to the old textures. Check your paths.

Dear Brian
See please it is not only the textures it is the old model too

You're resuming a render? This happens when you're resuming an MXS, but you've changed something in it, so you see the new on top of the old. Maybe network is resuming the render without you realizing it and you've kept the same name in the MXS files between the old and new.

I always press the start never resume

Did the old MXS have the same name as the new one?

No , I always give unique name

Do you specify a path to write the MXS and MXI for each new render, or just using the default?

I had a similar problem with another renderer (not maxwell).
for some reason copying new files over older didn't work over network.
somehow "older" files where not replaced.
deleted everything and copyed again with tera-copy.
worked.

choo-chee wrote:I had a similar problem with another renderer (not maxwell).
for some reason copying new files over older didn't work over network.
somehow "older" files where not replaced.
deleted everything and copyed again with tera-copy.
worked.

Well that kind of problems with files (not regarding maxwell) have occurred for us with windows offline folder caching and synchronization.
We had to clear the cache, turn off the synchronization (restart) and put it back on again.

Try to clear the temp folders as well.

thank you ! i will try it
in other words you say i need to restart all the computers that involve with the network render?

dubir wrote:thank you ! i will try it
in other words you say i need to restart all the computers that involve with the network render?

In other words I say that if you are using windows file synchronization, you might have a problem with that.
To fix it you might want to try to delete all windows file sync. files and folders (and also the temp folders), restarting the computer first before turning windows file sync on again on each node that "remembers".

It's a long shot