Hi,
1. "Render failed": This is unfortunately standard behavior of the Corona DR system if dr server is used for the first time after starting it up and loading the empty dr scene (see 6.)
2. "Chamfer versions": May be an issue, but usually is not. Except possibly getting wrong mesh topology
3. "Populate data": standard message and never an issue
4./5. "Graphics driver": standard log entry (and correct) if operating in slave mode
6. "Legacy (pre-V4)": As you might know, Corona loads an empty scene at startup which is Corona version 1.7, thus the log entry. No issue.
So only the different chamfer versions of the mentioned log snippets may be a cause and it also indicates that versions on master and slave are not exactly the same. But I don't think it would cause a Max crash, but maybe it does.
@ferrarod:
- Can you open a scene on a slave and render it there?
- DrServer reports the local IP as "255.255.255.255", that's definitely weird and indicates a name resolution issue at the nodes/your network. Or DrServer fails here to detect the local IP for another reason. It should read "10.0.0.208" in this case. Anyway, communication between master and slave seems to work in the first place, at least when it comes to file transfer.
- Additionally, the DrServer working directory is not standard: it points to the debug directory for rendered image strips, the sent scene is loaded correctly from there according to the log though
- I would try to delete "AppData\Local\CoronaRenderer\DrData\DrConfig-1.5.txt" and let Corona rebuild the defaults because of the above
Finally, a Max minidump of a slave can reveal what exactly is causing the crash. Search the temp directory of the slave for a file like "3dsmax_minidump.dmp". Hopefully there are a few.
Good Luck