Maxwell Render | Official public forum

ERROR: - object Polygon.0 has triangles without material...

OMG. Give me 1.1 back please!!!

Anyone?

It's a problem with the plugin not applying custom mxms correctly. Nicole says they are working on it and they expect to have it fixed by the weekend.

BUT!!!!!!!!!

Don't they have a bl$$dy website entirely devoted to custom MXMs!!!!!! WTF was the developer of cinemaxwell doing??? How could this be released without testing against 'custom' MXMs when just about every bl$$dy scene uses downloaded MXMs???!!!!

I'm getting seriously pi$$ed off with this. At the moment I'm using this as a student but imagine if you relied on MW Render for your income...good grief!

adri: The problem mainly occurs with materials created with the new Maxwell Material Editor. The ones that ship with Maxwell work fine. Most of my old custom materials work ok too (although I have had several crashes when these old materials also use textures).

As a temporary solution, open the saved mxs in Studio. You will probably see one or more of your materials have been exported but not assigned to objects. If you haven't got hundreds then you should be able to quickly apply the mats by hand. Not ideal but a work around until the plugin gets fixed.

Maxwell 1.5 'feels' much better to me but the Cinema plugin problems have spoiled the experience (again).

Right,

That's it for me.

I've just tried opening up MW Studio and got a load of crap errors on the screen!

Can't be bothered with this anymore.

Advanced Render it is until VRayForC4D is released.

bye bye NL. And you'll be getting an email requiring a refund of my student licence fee.

Que es esto pues???

1.5? mas bien 0.00005 y gratis hasta que funciona al menos!!!



Hasta la vista NL. No tengo tiempo para estos tonterias!

Adri

got the same error after switching back to 1.1 and tried to render an old scene... so something is broken?



edit: after checking it I found out that it was a missing mxm...

I haven't downloaded 1.5 yet but don't think i'll bother, by the sounds of it its a bit of a nightmare! I don't know what NL have been doing for a year - realflow perhaps, but really they should have at least had a more stable version and the new features are nothing ground breaking at all. I jumped ship a while ago and Im glad I did, its a shame that NL are making such a hash of this! I am much happier on the other side but i guess here isn't the place to comment on that, just amazed at NL and feel a bit sorry for them, im sure they mean well.

As for cinemaxwell I still don't know why they bother with this lengthly tagging proceedure. Either have seamless plugins or just make studio exchange better so it remembers all your UV mapping and material applications etc. for me that would be a smarter route but i guess they have promised plugins from the start.

This error tends to come up when you have a maxwell render tag and a cinema 4d material tag on the same object and you have not:

Dropped the cinema 4d material into the maxwell material tag texture slot.

Give that a try and see if the problem clears.

It is not a bug, but the way this plugin operates to function.

It is a bug. Create a new custom mxm material with the Maxwell 1.5 material editor, apply it to any Cinema object and the error message will always occur.

Drop what you like, where you like but the plugin has serious flaws which every right minded person knows.

Becco_UK wrote:It is a bug. Create a new custom mxm material with the Maxwell 1.5 material editor, apply it to any Cinema object and the error message will always occur.

Drop what you like, where you like but the plugin has serious flaws which every right minded person knows.

Yep, it only happens with new materials created from the new material editor, older MXMs created with 1.1 and 1.0 work.

Thanks for putting that very nicely Becco, in testing I checked previously tried and tested scenes for Custom MXM testing. The check with a newly created MXM from 1.5 was an overlook on my part, and you can bet, it will never be the case again.

adri wrote:BUT!!!!!!!!!

Don't they have a bl$$dy website entirely devoted to custom MXMs!!!!!! WTF was the developer of cinemaxwell doing??? How could this be released without testing against 'custom' MXMs when just about every bl$$dy scene uses downloaded MXMs???!!!!

I'm getting seriously pi$$ed off with this. At the moment I'm using this as a student but imagine if you relied on MW Render for your income...good grief!

Hello Adri,

I have tested MXMs that were created prior to 1.5 versions of MXST and MXED and they work. I highly doubt there are that many newly created MXMs from the material site that were made with 1.5.

So if you have a problem with the existing stock of MXMs please be sure to let me know so I can test it and get it reported as I have not find any yet.

As you did post with this thread, newly created 1.5 MXMs are a problem.

Here is an example posted with the use of a 1.0/1.1 Material Editor MXM (wet clay) loaded as a custom MXM.

As a side note, I run both a full installation of C4D R10 and the demo version of C4D R10 at the same time. I test these situations in both as an independent testing bed to look for problems. This test below was run from both versions using the same plugin that is available to the public. The result is the same.

Image notes: the MXCL render was only added on top of the Cinema 4D screen shot in photoshop as an image composite to conserve file space. I am using the same version of public release version of Cinemaxwell and having the MXCL preview in the plugin is not a new feature nor is it any indication of a future feature. Although that would be very interesting.

I agree that most 1.1 materials will work fine when used with the new Cinema plugin. However custom mxm 1.1, materials with more than one Cinema material dragged into the custom maxwell material Texture tag(s) space cause to Cinema 9.6 (Windows) to crash.

Took hours of work yesterday to get a 1.1 scene working with the new plugin - no fun at all because the scene had more than 3 objects and as usual its always one of the last objects to be checked when the problem is identified.

Example of Maxwell 1.1 Custom mxm that causes Cinema to crash when attempting to render or write an mxm file.

The more I see the the faults with the new plugin the more the problem looks like it's going to take longer than a few days to resolve.

I hope in fixing new Custom mxm materials that using the old 1.1 custom mxm's don't get even more damaged.