[arkviz]

MXCL crashes everytime it has to write mxi and image file from next frame on animation rendering. First frame is rendered ok, then next mxs is loaded. Voxelization ok. Render starts ok. It is running until mxi and image file is going to be saved. Now it crash. Please help....

[sconlogue]

I am having the exact same problem. I have not had any luck figuring this one out. I am using the latest version of the Max plugin and Maxwell. I have a test scene with a teapot, sphere etc. converted to editable mesh and textured with arroway. Paths are all correct as each node gets though one frame fine. After that they silently fail, manager just shows pending then eventually lost. All 8 nodes are doing this. The only thing that is animated in the scene is the camera. Anyone else experience this??

[Bubbaloo]

What plugin are you using? In Max you have to configure the settings to save incremental file names.

[sconlogue]

In my case I am using the Plug-in for Max. It is creating the sequence of MXS files just fine. The Node manager see's all the frames and puts them in the cue. If I restart the failed nodes they are able to render the next cued frame but then fail upon loading the following frame. So the mxs files work fine but all the nodes are unable to transition from one frame to the next assigned frame. I have noticed that scenes with no textures render fine. I have already check all the texture paths and they are pointing to the file server where the maps are located.