[Boris Ulzibat]

Cinemaxwell 1.5 crashes Cinema 4D R10 each time i start it.
Maxwell 1.5 is great, but this issue kills me
I was able to start Cinema with Cinemaxwell only once, but it crashed when i tried to select output path for MXS.
Mac OS X 10.4.9, C4D R10.1.

UPD
I have tried installing Maxwell 1,5 on my iMac (intel) and Cinemaxwell loads and works just fine! (except for the known issue with MXM), for some strange reason, the UI colors are completely different on iMac and MacPro...
iMac has white and MacPro has grey UI. This is true for both studio and mxcl/mxed.
I have tried reverting to Maxwell 1.1/Cinemaxwell 1.1, but strangely, the problem remained the same!
I cannot figure out the reason, but with Cinemaxwell (now bot 1.1 or 1.5) Cinema quits when i try to edin ANY path, or open/save a file.
Can anyone enlighten me???
I am goimg crazy. Can't understand anything!!!

[shen.de]

this is a problem I read about in some cinema forums...

I'm thrilled to test v1.5 but I got an upcomming contract work to do... and I'm afraid mw1.5 f***s my work up...

furthermore it seems that cinemaxwell only works from c4d v9.6 up ...
I got 9.01...

does anybody from NL-team know anything about this issue?!


thanks in advance,

shen.de

[Maximus3D]

I can't say it works very well in C4D 10.1 either, so far i been unable to render out a simple sphere on a plane because Maxwell complains that it has no material or something like that. But it does! ..not the happiest of campers around no.

When Custom MXM's are applied to a object no matter what the object is then the error "ERROR: - object Sphere has triangles without material
</tt>

ERROR: - Render Failed" popsup. I thought the plugins were tested and confirmed to work now with the 1.5 release, this problem should been spotted by the betatesters.

/ Max

[shen.de]

doesnt look like they were tested when I take a look at the forum...

seems like nearly every plugin has serious problems.

but after checking again it seems like the mw1.5 doesn't recognize cinema versions 9.0, 9.1 !! thats aweful!

[Kabe]

No test that a small company like NL could manage is able to catch every
configuration that is out there. They have released more than 30 different
software builds yesterday...

At some point it's better to get it out in the wild and fix the upcoming
problems than to let all people wait for another couple of weeks, and then
stumble into nearly the same situation.

We have day 2 of the release, so try to calm down a little.

Describe your problems, send files to NL, let NL fix it, there will be updates.

Kabe

[Maximus3D]

I understand what you're saying Kabe, however this issue seems to occur on pretty much all systems from what i understand. And the bug being so obvious that even a blind dog would catch it i can't see how they missed it.

There's no need to email the scenefile to them as they can easily reproduce this themselves by simply applying a custom mxm to any object.

I'll hold off my excitement about the 1.5 release until i see the basic stuff working properly.

/ Max

[Boris Ulzibat]

Kabe, I understand what you are saying, I just hope the plugins will be updated REALLY soon, not as usual (wit C4D one at least).
Speaking about different configurations...
Macs are pretty much the same.
I guess the problem is not in this...
And yes, i have nothing to send to NL, because the plugin just doesn't work, even Cinema doesn't work with it...

[Kabe]

Macs are pretty much the same.

You must be kidding. The current transition of Cinema Mac is quite a task
for a developer:

Hardware:
Mac Intel, Mac G5 Single Proz, Mac G5 Multi Proz,

Host Software:
Cinema R10 Intel
Cinema R10 PPC
Cinema R9.6 UB Intel
Cinema R.9.6 UB PPC
Cinema R.9.6 PPC

Two different compilers (technically 3), 3 different plugin targets, 2 different processors, 2 different OS architectures.

Certainly this issue was overlooked, and NL and the testers are not
happy about this. However, I'm confident that the C4D plugin
won't be the last one to get fixed.

To serve a fix though, we have to nail down what is happening exactly
here. It might have sneaked in at the last second like at least one other
issue (ZClipping checked for old cams).

Kabe

[Boris Ulzibat]

I am not kidding, i was speaking about a number of different hardware configurations, which is definitely less than on the Wintel side.

[edit]
Adn i was not speaking about development, it was about testing!

[Kabe]

Testing different platforms isn't very nice, too. You find a bug. Now you
have to pinpoint if it is an issue with the Plug or the app or the data used.

Then you have to point if it depends on OS, OS version, Hardware or
Cinema version.

Believe me, it takes time.

Kabe

[Boris Ulzibat]

Testing different platforms isn't very nice, too. You find a bug. Now you
have to pinpoint if it is an issue with the Plug or the app or the data used.

Then you have to point if it depends on OS, OS version, Hardware or
Cinema version.

Believe me, it takes time.

Kabe

I understand it! I never said it is EASY, i said "I think it is EASIER in case of Mac than in case of Win".
Than, again, i may be wrong, i do not intend to be the "absolute truth".
This was just my thoughts.

About the release of the updates, i meant releasing updated plugins as soon as an issue is solved, rather than as soon as EVERY issue is solved.

[macray]

It would have been nice to have an indicatin in advance that it doesn't work with cinema <9.6 so I wouldn't have bothered to download and delete 1.1.

Now i have to set it up again to finish some projects....

[vinys]

It would have been nice to have an indicatin in advance that it doesn't work with cinema <9.6 so I wouldn't have bothered to download and delete 1.1.

Has any official NL member confirmed that < R9.6 are not supported any more?

God it makes me so angry that we have to find it out on our own. Would it had
been so hard to make a note somewhere???

[nicole]

Hi,

I can confirm that any pre-9.6 versions of C4D are not supported in 1.5 at the moment. We might consider to support earlier versions if the demand if high enough.
The features list available on the download page has a complete overview of the supported plug-ins, operating systems and versions, and that is available and visible to everyone who went to the download page to get 1.5. It also specifies which plug-in versions/ OS are still coming up.

Cheers,

Nicole

[macray]

I think it is not to hard to add a remark next to the download link to cinemaxwell that it supports only 9.6 and up!

And there was never anyone mentioning that the support for the version of Cinema we used when we bought maxwell would subside until we have a final version. So I assumed that it would work as always. And didn't bother to download the feature list. That doesn't give me anything. I don;t need to brag about this or that feature maxwell has when I can show images. So I didn't have a look at it. I downloaded the manual, maxwell and the plugin, only to find out that it doesn;t work - as there is no note to indcate it doesn't work on older versions anymore.

And it is not nice to find it out when I'm expecting a better maxwell that should be worth being called 1.5 instead of 1.2.
Sorry to be so bitter, but the responsibilty for that is on your side!