[Mihai]

I'm not sure what you mean, you had to use Maxwell materials from the start, right from alpha.

I don't understand why you're so upset either because it makes a certain renderer uses it's own material definitions, even biased ones. Vray would never be as fast as it is if it wasn't using it's own optimized materials specifically made to work with Vray. Brazil also has it's own cameras, Mental ray also has it's own materials....what are you so upset about?

[Rochr]

Well, that´s the problem, while the beta could work with textures and Maxwell material tags, RC5 with the new plugin don´t.
It simply refuses to render with the all annoying "Render Failed" -message or comes out as a completely blank scene with only the sky visible.

I don´t really mind long render times, and would gladely continue using the beta if it didn´t leave out a few hundred correctly tagged objects every time i tried rendering the scene.

[spekoun]

I have already written about it, but *.mxm and texture maps works fine with latest plugin. Of course there are many other bothering bugs, but there is not problem with UVW and custom mxm tag (as my experience shows). I am on PC, so i do not know abou MAC. And except plastic i set every material directly in cinema using old tags (metal, dieletric,...) they are correctly translated. Of course, when i need fine tweaking and benefit from all possibilities of new material system I have to use custom mxm tag.

[arch4d]

i totally agree, spekoun !

everything works fine now with the new plugin on my PC too.
the only thing i wish is that the exported mxs-scene REALLY should take over the groups of the cinema scene, and only create one material of the ones with the same settings.

instead the plugin generates hundreds of materials, so you have a lot of work to do in studio...

[Becco_UK]

arch4d: In Cinema, apply the same mxm material to each object with the same material (very quick if they are in a null and you apply to children).

When you make the mxs via Cinema and later open in Maxwell Studio there is just one material for your material grouping.

All the objects are kept seperate in case you need to use different materials.

[Rochr]

spekoun:
I´m on PC as well, but i´m curious on how you´re getting the textures to work, because i´ve had no luck at all.
I apply a texture in the color channel, drop it onto an object and use a Maxwell diffuse tag, yet the render fails. If i delete the texture, but keep the diffuse tag, it renders.

I haven´t tried .mxm materials, but there are only extremely smooth and shiny materials there, and what i need is a rough concrete surface with cracks and dents. Textures and bumpmaps are the (imo) best way to get a decent result when it comes to materials like that.

[Becco_UK]

Rochr: This is the unfortunate part of RC5 - some excellent 'rough and dirty' materials can be made in Maxwell Sudio and saved as mxm files.

As I understand it, the problem arises when, in Cinema, the previously saved mxm material (with textures) is applied and they do not render using the plugin.

For the detailed scenes you make I imagine it is a right pain with all the backwards and forwards messing about between applications.

The recent previews you posted at Renderosity may make the point better known here too.

I would have thought it was in Next Limits' interests to sort the Cinema plugin out positively and promptly. My true 'studio' is Cinema4D so why am I being forced into the second class Maxwell Studio just to make materials.

[Rochr]

Thanks for the explanation Becco.

And you´re absolutely right, taking those kind of scenes back and forward and also loose the hierarky in the process would turn into a crazy nightmare, so it´s not an option.

It really would be nice to have these damn bugs sorted out and any time soon. If one look at it from a business pov and take into consideration that Cinema4D users are one of NL´s largest userbase, it´s slightly odd that NL doesn´t put much more effort on that part.
Or perhaps colored tags and such are considered major updates and we should be content, who knows...

[thomas lacroix]

i think we'll have to wait for V1 to come out before having any news on the plugin front...

[thomas lacroix]

that's not what i meant, i meant that the plug must probably have to be updated to work with maxwell 1.0, lets just hope that the new C4d plug will be released the same day the V1.0 will ( sometime max had got the "primeur" )

[macray]

Normally it should be released in time so you shouldn't become too familiar with Studio.

As all the other cinema users - I assume I'm not the only one - I'd like to work only with cinema and the maxwell plugin.