Daniel Hruby wrote:Trying to get mine going...Renders Failed on the G5 Quad. It appears to not file complex IOR used in one of the materials. I only work on the MacPro and have all my textures right on the MacPro drive with my host app and maxwell. The G5 Quad is monitor-less and controlled via Timbuktu remote from the MacPro. I just want to take advantage of the Quad on my renders that I start on the MacPro.
My set up:
1 ethernet connection and WIFI connection. Apple Talk off on both machines. FIrewall off. No stealth mode.
From MacPro I am pointing to folders that reside on the MacPro. The MXS, the MXI, the output and the bitmaps (from a pack and go folder that I have on both machines. I just dont know which one to point to - neither solves my problem.
Can anyone give me the 4 locations I should set this for from the Mac Pro? I would greatly appreciate it a diagram or a complete explanation. I never seem to get a clear answer that means anything to me. Excuse my ignorance.
Do I need a third drive connected to both machines for my texture library and MXS ?
Thanks for help in advance> I am eager to get this working.
daniel, it appears that with the latest update it is not so critical anymore where your MXS and texture library are stored. if you assigned the path with the 'bitmaps' entry in 'add job' dialog, the servers should find all textures.
btw, i'm using a similiar setup, working on a macpro quad and using a G5 quad as server + a few other macs, but i don't use any wifi connection and only manually asssigned IP's.
first thing, just make sure that all servers running are really updated to 1.5.1, just check in the console log, if version number is OK.
then, two good things to check are:
1. make a 'pack and go' collection before sending the job. double check and reload the MXS to make sure that the IOR file is really pointing to the new folder. if not, assign the correct path (in the collected folder) and resave. then, when adding the job, assign this collected folder as bitmaps path.
2. make sure that if you had a network rendering failure, like missing textures, to stop the job, then quit and restart the maxwell server which had that error before adding a new job. apparently in certain situations the servers 'stick' to the previous setup and don't register for example that the texture path was changed.
hope this helps... let me know.
markus