[Frances]

Frances -
I think it is only a problem with 1.1, which has only been released for Max 8 right??

No I'm using V1.1. It works with Max 6 thru 8 and VIZ 2005 thru 2007.

[JesperW]

I can't repeat this crash. I want to get it straight what you all are doing to produce it:

1. Open a scene that has Maxwell as the assigned renderer and mat. ed. renderer.

2. Open the material editor. If one of the materials in a slot is not found or the material is found, but is missing a bitmap, Max crashes.

Frances, like most nasty bugs this in an intermittent one. The scenario is exactly as you outline above. It has never happened to me on small models. Only when you start getting serious...

I am guessing the cause to be some kind of race condition when fetching preview images from many .mxm files simultaneously.

[misterasset]

Okay, now even my "work around" isn't working. Max has crashed 9 times in a row trying to open the material editor. I had patience with the plug-in up until now. Juan, when can we expect an update/fix? Thanks.

[JesperW]

Okay, now even my "work around" isn't working. Max has crashed 9 times in a row trying to open the material editor. I had patience with the plug-in up until now. Juan, when can we expect an update/fix? Thanks.

Try the ClearMedit script then. Since it removes all materials the editor is shure to open. Yes you do have to drag the materials back to the slots again, but at least you can continue working!

(BTW, haven't you been around long enough to know the pointlessness of asking for schedules around here )

[Peter Shupe]

Yeah - I tried clearing out the material editor and that seemed to work. I wouldn't want to do that on a regular basis though. I think maxwell drops bitmap paths even when they are in the right place. Then you can't tell what mxm file you are even using when you get the material unless you have the bitmaps all in C: because there is no way to stretch the area where the path is kept. Also it doesn't load the name of the mxm in the material slot. It doesn't seem like they have dedicated too much time to the plugins yet!! my 2 cents.

Ciao Peter.

[misterasset]

...and render out a test image. After the render is done (20sec), the material editor is fixed.

When you say "render out a test image" do you mean with scanline or Maxwell?

[Peter Shupe]

That does seem to work for me! I've only tried it once but seems to be the better solution than reset my renderer and lose all my materials. Thanks Tomas.

It has to finish the render apparently. I just set my SL to like 2 with small size and it completed and opened my material editor with no problem.

Regards Peter.

[Romans]

Hello!

I have sometimes the same problem.

For me the following steps are working so far: (max 8, sp3, true dwg2007)

1. open max (with the standard empty scene)
2. open material-editor (to load the slots)
3. close material-editor
3. open your max-scene with maxwell-materials (without saving the standard empty scene)

Thats all....

I think the problem is, that the material-editor has difficulties to load mxm-mats when its started the first time....but i may be wrong...

Good luck!

Roman

[essyxexhibits]

I have this same problem but everyone else's workaround hasn't worked for me soooooo...

When this happens it usually starts because there is a problem with the last material I added to the editor. So I reopen the scene, change back to the scanline, open my material editor and remove the offending material, then reload my Maxwell preset and I'm good to go. Saves having to reimport the scene into a new file and retrieve all of your mats.

But, as everyone has said, this is certainly the most important fix for the new release and I eagerly await it. (Wisely, they did not offer me a release date when I recently asked in a support email.)

[x_site]

well here's what i do:

1] open max and open scene to render
2] pray that it does not crash when i open material editor
3] keep fingers crossed and click material editor tab
4] max crashes
5] get sharp needle from maxwell voodoo kit
6] get maxwell doll from same box
7] stick needle into doll
8] repeat as necessary

Please NL help reduce global warming by fixing this issues asap.... things are getting hot under the collar and i am spending far too much time just watching max crashing

[aitraaz]

LOL

Used to have huge problems with this. Found out that keeping the native max materials slots to 6 (and never more), the problem almost never occurs, even for complex scenes. When the rare crash does occur, i save the file, open max, then open the max material editor, and *then* reload the scene, works always. Dunno if it helps....

[andrebaros]

Thank god for this forum. I just ran into this problem with a scene which had been working fine and then started crashing. It's at the point though that I have to save and apply the fix between every command.

Maxwell roulette has me by the &*$&*#. Press the render button and have a quick and beautiful rendering or crash and burn. I can't go back to anything else and get the results that people have gotten used to and I can't keep dealing with unexplainable crashes.

[subspark]

What scares me is how NL could release this plugin update without coming accross the bugs themselves. I'm sorry ladies and gentlemen but release 1.0.77 of the 3dsMax plugin was simply not worthy of release. Shame on NL. I can't render a thing letalone browse through my materials.

[misterasset]

This thread was from two plug-ins ago, when it used MXM Reference Materials, not Maxwell Materials.

I must say that I've found Plug-In 1.0.77 to be extremely stable and usueful.

Can you describe exactly what problems you are having, and double check the release of the plug-in you have?

[michaelplogue]

Aside from some problems with SSS and HDR's, this is by far the best Max plugin to date - and I have been pretty critical in the past. My workflow has dramatically improved with this version.