Maxwell Render | Official public forum

JD, with 3.1, C4D doesn't load the plugin, complains about; get processor active group count

Is this the XP thingy again? or do I need a fresh install?





Random test render of the day, just thought you might like it... (Some things in the scene need fixing though)

I'd have to guess so, though it's not likely to be my own code calling this missing function. If you tell me exactly what happens (I mean, exact spelling, capitalization, etc), how/where you see it happen, and what the messages say, I can see if there is something I can do.

Here it is, sorry took a while.

Whatever the case, it's not my own code calling that, so there's not much I can do.

Hi Eric,

Is your windows version older than Win7?

Thanks

nachob

Yes its XP.... xp64 pro sp2

I cant upgrade for a while, Dont even have a spare hard drive.... to put win7 on.

While you two are here in one thread, can I ask when global bump map for materials will be working again thru mxed via c4d. Because its a bit of a nightmare to potentially damage a library mxm, just by opening it and resaving. (the global bump is only lost if I click on that).. I may have already changed files without knowing and prob wont spot the error in the renders.. Thanks, is this working for other MW3 plugins? No one else complains about this,, just me.. why..

I don't find any problem with global bump. There used to be a problem where displacement was not written/read correctly, for materials using types (i.e. Opaque, Transparent, etc), but it was fixed some time ago. So please tell us a set of steps we can use to use to observe this issue.

We have discussed it before a few times over the past year, you said it was caused by MW3 not the plug.... you may be going senile I expect Or simply overloaded.

Open this mxm in cinema, unlink it, then open in mxed. global bump slot will be blank, if you resave without changing anything global bump will still be there in material editor, if you click on the slot and resave its gone permanently.

http://www.mediafire.com/download/yxrn4 ... l_bump.zip

This was a MW2 mxm, I just opened it in MW3 to send via pack'n'go but the issue is still there.

I don't think I've completely checked out just yet, before posting, I searched this forum for posts by you, with global and bump, and only came up with this very thread. That said, with the added detail of importing an MXM, then unlinking, I do see some problem. But it's not just with editing in MXED; if you write an MXS, it won't be enabled there, either. But, it will, if you change anything, like the bump value. So I'll take a look and find out what's happening.