Maxwell Render | Official public forum

I find the lack of the simple materials very annoying too. Let's hope there will be some improvement. On the other hand it might be best for us to keep a big library of all the materials we use as MXM files. I think we just need some time to get used to that.
I was hoping for an automatic translator for materials. It would be a great help and would really speed up the test renderings.

Personally I only care about the MXM material, but it sounds like the 1.1 exporter is horribly broken in other ways (UV map mis-numbering, broken multi-materials, crashing, etc.).

- Casey

if u dont use sub multisubject material and use just mxm u wont have any sort of crash

Michal, that happened to me this afternoon with a 1.0 scene. I made a simple scene with a cube to test each material from that scene individually. Assign material > render; assign material > render. After some tryes I found a couple materials that were causing max crashes. The only common thing between those two materials which other materials didn't had was that their names had brackets (); they both had IOR files applyed too but I had others with IOR files that worked correctly so that was not the problem (beware that IOR file names have changed to something more comprehensive thanks to Tyrone and co.). I know that sounds quite silly but worked.

Good luck.

I know it's not the answer you're looking for, but go back to using the previous plug-in.

Any scenes I made with V1.0 plugin all open in Studio V1.1 with no problems.

I've not yet had chance to try an export from Max with the V1.1 plug-in, but at least you can still use the V1.0 plug-in.

UVW Map objects, assign a plastic material & load a map, then export. That way no UVWmap errors occur.
Then use Studio for material assignments & editing.

Like I said, not the answer you want but a workaround for the moment until a fixed plug-in is released.

Tim.

is texture display in viewport working now?
without this 1.1 is useless for me...

numerobis

It is working; but, even if it wasn't, you could use standard max material to check mapping.

I did my first test export today with V1.1 plug in for Max.

Only problem was missing dll for Plastic on Max starting.

Used an existing MXM created in V1.0 and exported fine.

Memory increase per export has stoppped too.


Tim.

Tim Ellis wrote:Memory increase per export has stoppped too.

That's definatly good news! Have you verified this with a complex scene yet?

Michael not yet, this was with an approx 400,000 face scene, with only one mxm material.

Once exported, I repeated five or six times, each time the memory allocation rose, but dropped back to it's original level when export was completed.

Tim.