Maxwell Render | Official public forum

Hello,

I build up a scene on my Mac with Maya 2010 and Maxwell 2.0.2.0. It contains about 1000 Cars (Maya instances). I turn on "Maya instances to Maxwell Instances" and it works very well.
Now I wanted to Render the Job on Rebusfarm and there the same scene crashes. Rebus is on 2.0.3.0. I updated my Maxwell to 2.0.3.0 and now it crashes on my machine too.
When I disable "Maya instances to Maxwell Instances" it works, but just with maybe 10 to 20 Cars. And the guys of Rebus surely wont downgrade the Farm...

What can I do? My deadline is tomorrow in the early mornig.

Thanks and Greetings, Linus

This sounds like an engine problem, so I'm moving it to the main forum. Could you send us the MXS file, so we can debug it?

I've just been told that there's a known bug in 2.0.3 when you instance objects with per-face material assignments. The only solution at the moment is to break the object into pieces so that you have one material per mesh. The problem will be fixed in the next engine patch, but I don't have an ETA for that.

Ah, ok! I had instance objects with per-face material assignments in this scene. But in the end I could render it on my machine with 2.0.2, so it worked for me. Thanks a lot!

Afternoon all,

I'm currently experiencing the same problem but in 3dsMax 2009 after just having upgraded to Maxwell 2.0.3 using the
latest plugin version (all x64 bit). I am using per-face material assignments on numerous instances like cars and trees.
The scene renders fine in Maxwell 1.7.1 although it takes ages to reach SL 16 @ a resolution of 4800x2400 pixel using
cooperative render between 8 PC's. Would it help to disable the conversion from Max to Maxwell instances in the render
settings or should I rather roll back to Maxwell 2.0.2 as well?

Please advise as I'm also running out of time... Thanks a million in advance.

Jost

Hi fuso, I did that, but so I just could render 10-20 Cars without a crash and not my 1000... And it takes a long time to bring all the geometry over to Maxwell. I think going back to 2.0.2 is the best solution right now... Good luck!

@ Pixelprinz: Thanks for getting back to me so quickly. I also realised that my Max > Maxwell export now takes about 3
minutes and I ended up with an mxs file of just over 1.3GB and after having almost finished voxelisation, it just crashed
anyway, what a mess. I really hope rolling back to 2.0.2 will fix it. Everything times 8 to get the render farm back

No drinks in the pub tonight for me I guess...

Cheers

Test it with one node on 2.0.2 first! But for me it works and if not, break the object into pieces so that you have one material per mesh, like Mihnea Balta says. And you know what? I will have some drinks for you...! Cheers!

Of course I'll test it with one node first but thanks for reminding me. Do you reckon I will also have to roll back the plugin
version to at least one release before the current?

Yes, unfortunately the MXS file format has changed, so the latest plug-in produces files which cannot be loaded in 2.0.2.

Mihnea Balta wrote:I've just been told that there's a known bug in 2.0.3 when you instance objects with per-face material assignments. The only solution at the moment is to break the object into pieces so that you have one material per mesh. The problem will be fixed in the next engine patch, but I don't have an ETA for that.

I experienced the same after the 2.0.3 update within max. It was my understanding that proxies had to be created from a single mesh. Are you saying maxwell can create a proxy from a group of unique meshes?

On a side note, would it be possible to incorporate a "no future notification" check box specific to new releases when the update window appears through the main engine? Or is there an option somewhere to disable notifications alltogether?

rusteberg wrote: I experienced the same after the 2.0.3 update within max. It was my understanding that proxies had to be created from a single mesh. Are you saying maxwell can create a proxy from a group of unique meshes?

No, this problem is related to multimaterials. You can create a proxy from a mesh which uses a multimaterial, and that will cause 2.0.3 to crash (it used to work in 2.0.2 and it will be fixed again in 2.0.4).

rusteberg wrote: On a side note, would it be possible to incorporate a "no future notification" check box specific to new releases when the update window appears through the main engine? Or is there an option somewhere to disable notifications alltogether?

I don't think it's possible to disable it now, but I'll pass along your request.

gracias señor.

rusteberg wrote:On a side note, would it be possible to incorporate a "no future notification" check box specific to new releases when the update window appears through the main engine? Or is there an option somewhere to disable notifications alltogether?

oops, just noticed there's a checkbox to disable checking for updates.... never mind, that'll do!