[tcamco]

I am currently experiencing a simular problem. I prepare project for rendering in Maxwell, initiate the render and the rendering starts. During the rendering I notice I didn't change a texture map on 1 object. I stop Maxwell, make the correction, making sure I've applied a jpeg texture map and the diffuser setting in Maxwell and hit the render button. But Maxwell fails with an Error message after starting to load bitmaps. Nothing else has changed. I've tied moving the Form•Z file to the top level of the start up drive (If I don't move them to the top level Maxwell will not start automatically, but I have to double click on the Maxwell icon to start the render) and saving the Maxwell mxs files to the top level of the start up drive also. It's very frustrating! If i close the Form•Z file and re-open with a different saved view it will sometimes render.

As for the pallette settings remaining the same I found this usefull if I'm rendering multiple views of the same project. It's better than having to constantly re-enter the same information.

I'm running OSX 10.4.2 on a Power Mac G5 dual 2.0 and Form•Z 5.5.1 and Maxwellz0.5.2.3a

[Guest]

I deleted the output files, changed the path, and it started rendering fine. Problem soloved.

[tcamco]

adehus
I did notice yhe report you mentioned and tried pushing render button 10 -12 times and still got the error message.

[juan]

Hi,

Sorry for the delay, too much work.. (you will see the awesome results soon )

I will investigate you issues as soon as possible. Honestly, it is difficult to imagine how the maxwell palette settings could corrupt the process of writing the mxs file. There are not so many ways to do that. The 99% of the times it is due geometry issues.

I suggest you to follow this steps: Delete the previous mxs files that could have been generated before in the target path. Try to render the scene. If you get a warning showing issues in the process, look for a file named "maxwellz.txt". It is written when there have been problems in the scene analysis. It uses to be placed in the root folder of your local drive or in the current folder of your scene. Take a look at the last line of the file. Can you post here this line?

Also try hidding different objects and layers. Usually the guilty is just one object, not the entire geometry. Hide all the objects and render it. do you still get the issue? If so, send me the scene to maxwelltech@nextlimit.com If the render works fine, do some tests with different objects hidden and you will find easily the one which is corrupting everything. I had a scene with 500 objects, 1 million of triangles and the wrong object was a simple square will null normals.

Please let me know any issues you have. Sorry for the inconveniences.
Regards,

Juan