[hothpicas]

For users of versions not supported by this plugin, I can understand the problem, but for users of supported versions, I just don't understand the problem. The plugin works fine. You do have to remap all your texture tags, but it's not that big a deal. Before you blame the plugin and give up, double-check your scene to make sure it is ready for rendering. It's unfortunate that previous material associations don't work with the new plugin, but again, it's not that big a deal.

[adri]

I suppose it depends on how many tags you have to remap! In Arch Viz that can be plenty!

mmm...

[adri]

And I for one had hopes that the mats handling was going to be better in this release...

It's still early days but having had a look at the mat editor and bearing in mind that I work on both PC and MAC it ain't looking that good at the moment.

Ho hum

[zoppo]

i just tried little scenes with procedural textures so far - and they work (win xp32 / c4d10.1)

you might want to check the file options settings in the mw render settings.
the plugin doesn't check whether the output folder exists.

[rickyinmotion]

Hey Adri, i work usually with 3ds Max but my new customer works
with C4D and i'm a newbie with it.
Can you explain : "You do have to remap all your texture tags"
thanks

[seco7]

Has anyone had any luck with the new plugin? I cannot seem to get anything to render, even a simple sphere and cube scene.

ERROR: - object Sphere has triangles without material

ERROR: - Render Failed

I've tried everything I can think of, old MXMs, new MXMs, default materials, etc.

Check your material associations, to make sure your MXMs alll have a texture tag associated with them. I found that one of my associations was broken when I opened an old scene, which stopped the render.

This isn't an old scene, it is a new one with one simple sphere. With their track record I wouldn't expect maxwell to work with an old scene. Can you tell I'm very disappointed?

Update: Aparrently the old bug that looses custom MXM paths when a new one is added is still there. I have a couple old MXM that seem to work. Most old ones won't work at all, have absolutely no idea why. Even if I re-open them, check all the paths and save it won't work. It also seems that once a scene is "corrupt" with this error, the scene is toast. I had to start a new scene after each error or even simple disfuse materials will error.

[Tyrone Marshall]

Hello Everyone,

Cinemaxwell 1.5 is out and before you do anything further please check this thread for more information and tips to use the plug in.

ref: http://www.maxwellrender.com/forum/view ... hp?t=22962

As far as 9.6 and version 10 goes, support for 8.5 (old SDK) is no longer support as far as I know. I am not sure at the moment about 9.5 and 9.6. I will ask to find out the cutoff line.

I believe for the MAC it is UB going forward.

[Kabe]

It turns out that Cinemaxwell 1.5 isn't compatible with the PPC version of Cinema 9.6. It does work with the UB version. Several important plugins are still PPC only, so Maxwell will remain a rarely used dusty toy for me.

There will be a 9.6 PPC version soon.

Kabe

[Tyrone Marshall]

It turns out that Cinemaxwell 1.5 isn't compatible with the PPC version of Cinema 9.6. It does work with the UB version. Several important plugins are still PPC only, so Maxwell will remain a rarely used dusty toy for me.

There will be a 9.6 PPC version soon.

Kabe

Thanks Kabe for the clarity on the PPC issue.

[shen.de]

I think rochr is right!!

I'm using c4d 9.01 ... I cant believe they expect me to buy a higher version just to use maxwell .... this is just mad!!

[vinys]

I'm using c4d 9.01 ... I cant believe they expect me to buy a higher version just to use maxwell .... this is just mad!!

If that would be the case, i would be angry and very disappointed too.

But let's better wait until Tyrone has confirmed that R9.1 is not supported anymore.