Everything related to Maxwell network rendering systems.
User avatar
By DarkLane
#364621
I´ve upgraded to 2,7,20 and I am encountering the kind of problem mentioned here:
http://www.maxwellrender.com/forum/view ... or+sending!

I have the mxi being saved to the root of my N drive, the mxs is saved to a directory on the N drive and the output image to another directory on the N drive. The temp folder is set to a specific directory on the N drive as well. All the nodes can see drive and the manager reports the nodes operating. The temp file is being saved in the temp directory along with the dependent files, I just can´t see what I´m doing wrong here.

But when the time limit is reached and the sampling level is reported back and it comes time to save the output image and the rest, I get the error ( in glaring red);

[30/January/2013 10:03:34] ERROR: Unable to open file for sending!
[30/January/2013 10:03:34] ERROR: File N:\Maxtemp\mxnetwork\rendernode_TM10563\shot00.mxi cannot be sent!
[30/January/2013 10:03:34] ERROR: File does not exist


Can anyone shed any light?
thanks
User avatar
By DarkLane
#364644
At the moment I´m only running one node to try and get this to work. The temp folder is set to my N drive and it is a separate folder.
User avatar
By Mihai
#364648
That's strange, maybe files from different jobs got mixed up. Try clearing all temp folders before adding a new job, you can do this from the file menu in Monitor, Manager, Node. Try with a very simple scene you know renders correctly. Are the output paths specified in the MXS itself or are you adding them only in the Add Job wizard?
User avatar
By DarkLane
#364661
Ok, I am using the LIghtwave plugin and I did some testing and ruled out problems with maxwell textures in my files and bad geometry, etc. I´ve double checked the output file locations and they are fine. I´ve cleared the temp folder and even set it to another clean folder to be sure.

Here´s what I see happening when I submit a job to Maxwell Render

1. The mxs files are written to the proper location
2. The temp folder collects and fills up with the proper files
3. the render begins and runs for the required time and sample rate
4. The render file is written out to the temp folder BUT then it doesn´t move it to the output folder.
5. The render fails

What I noted in the logs is that for some reason the output file is set to the temp folder (in this case MaxTemp). This isn´t the case in the plugin as I´ve double checked it and it is pointed to my output folder
N:\My Documents\Proj.Tempo60secs\shot12


[01/February/2013 10:35:45] [INFO] Starting voxelization.
[01/February/2013 10:35:45] [INFO]
[01/February/2013 10:35:45] [INFO] Scene Info:
[01/February/2013 10:35:45] [INFO] Image output: N:\My Documents\Maxtemp\mxnetwork\rendernode_TM10563\shot00.tga
[01/February/2013 10:35:45] [INFO] MXI output: N:\My Documents\Maxtemp\mxnetwork\rendernode_TM10563\shot00.
[01/February/2013 10:35:45] [INFO] Message to render node: render_info starting voxelization...
[01/February/2013 10:35:45] [INFO]


Any ideas
User avatar
By DarkLane
#364668
Another thing I noticed is that when I send my scene to the Network, even though I´ve set the mxs file to save to a particular location, it ignores this and it creates the corresponding number of frames as Proj.0000.mxs, etc in the root directory. I then can´t add another job because it tries to do the same again.... weird behaviour
User avatar
By Mihai
#364685
Could it be a permissions issue then? Would it be possible to film your screen when you add this job to the wizard?

Show:
1. Starting Monitor,Manager,Node (all of them set to deep debug mode)
2. Show what the temp folders is set to on each (it should just be the same temp folder for all three)
3. Add the job from the monitor
4. Set time to maybe 5 min.
5. Pause and start recording when the time is almost finished
6. Show if there are any files in the nodes temp folder.
User avatar
By Mihai
#364725
Ah, I think I see what's the problem you're not writing the MXI file suffix, if you look in your video the file is actually there but named only 0000. Try putting the .mxi suffix in the output field of the add job wizard.

This is an UI issue that needs to be fixed - know also you can drag/drop the image folder icon over the mxi folder icon to quickly copy the paths, and the mxi suffix will also be automatically appended.
User avatar
By DarkLane
#364728
Ah, I see. That explains it. It feels like a "D'oh!" moment as I should have checked that.
thanks for finding the problem
Help with swimming pool water

Hi Andreas " I would say the above "fake[…]

render engines and Maxwell

Other rendering engines are evolving day by day, m[…]