[misterasset]

I'm getting a weird error when using Maxwell all of a sudden:

Materials info: Total Materials: 1
Bitmap info: Loaded Maps: 0 (0 missing)
DefineSceneMaterials Ok
Create Geometry Ok
Error: MXS Write Error! (null)

I already tried replacing the plug-in and completely uninstalled and re-installed Maxwell. I've tried using scenes I've rendered previously and this specific error is from one containing just a single plane. Anybody got a clue?

[lsega77]

have you specified a path for the mxs file to be written to?

Luis

[lsega77]

firstly, I noticed you asking this question in a similar thread in the 3dsmax section. So we'll clarify that this is a plugin issue....

I just did a quick test and confirmed that if you don't set the path for the mxs file in they system rollout in 3ds max, you'll get this error. for some reason or other the default path doesn't always work.

specify a new path for the file and it should render out.

just as a general rule of thumb, I would spec this path and the render output path aswell.

I'm not sure if this error/bug occurs with other app plugins.

Hope that helps

Luis

[misterasset]

Yes, of couse I specified an output path for the MXS. I'm doing everything I would usually do, but I'm getting that error. I've been with Maxwell now for about a year so I can usually figure out this stuff on my own. Any other ideas?

[rivoli]

that happens to me as well from time to time. still have to figure out why, but it looks totally random. often if I specify a different path for the mxs is enough (some scenes would save on the default path while others don't), and then it renders just fine.
but once I had a scene that stopped rendering giving me that error out of the blue, it rendered fine for a while and then just stopped working between one test rendering and another (and I didn't even change anything apart from the camera angle). in that case I couldn't find any solution, changing path did't work as any other thing I tried. I think I remember I had to open a new scene in max and merge the old one in there (geometry, cameras and all), and it started rendering again.
still don't know what actually happened.

[JesperW]

Don't be fooled by the path that's written in the textbox. This error will occur even if the path written in the textbox is valid, but has not been "picked" manually for the current model. Always start a new model by specifying all output paths.

I guess the software is propably trying to write to some other default location than the one written.

[misterasset]

Thanks for the idea, but I specified different locations, even to my desktop.

The thing is, this is happening with EVERY scene I open/create right now. Long established scenes or even if I just make a single plane and camera.

[Mark 3d Mark]

I'm getting the same thing.
I've e-mailed maxwell help and reply two weeks ago.

[Mark 3d Mark]

Sorry I've had no reply from anyone.

[jdp]

it happened also to me a couple of times last week. I wasn't able to track the bug but in my opinion it has something to do with memory. I quitted max and restarted it, after that everything seemed to work again.

[misterasset]

I had to un-install and re-install Maxwell... twice. Then I learned it was this one scene I got from a website that was causing it. I have no idea what was in the scene to do that, but if I opened it then nothing from 3DS Max would export after that; even if it was an entirely new scene. Needless to say I deleted the scene and never touched it again.

Not much help is it?

[rivoli]

you might want to send it over at the guys in madrid, maybe there's a lead to debug this mxs writing error in there.

[bodebodebode]

Hello people.

I´m getting the same here....

Almost nuts trying so solve this..

http://www.maxwellrender.com/forum/view ... hp?t=19116