THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 05/04/2010 at 05:34, xxxxxxxx wrote:
Cinema 4D Version: R11/11.5
Platform: Mac OSX ;
Language(s) : C++ ;
I have a plugin which I build for R9.6-R11 and R11.5, on Windows and OSX. In general, it works fine and is used by some hundreds or thousands of people, but I got a report from one user last week for whom my 64-bit build would not load in R11 on OSX. The Cinema console tells him that my 64-bit plugin 'does not support 64 bit mode'. To rule out the possibility of a corrupted file, I had him email me the actual .dylib from his install, and it loads fine here. In the course of corresponding with him, he upgraded to R11.5, and he receives the same message in that case.
Does anyone have a clue about what might cause such a problem?
On 05/04/2010 at 07:12, xxxxxxxx wrote:
Strange... you probably already checked that there is no additional dylib of the plugin somewhere in his plugin folder, I assume?
On 05/04/2010 at 07:50, xxxxxxxx wrote:
Yes, by default, the plugin (as you know, but not others here) ships as a zipped folder, with both x86 and x64 dylibs. The expected behavior in 64-bit mode, assuming that the user does not delete the x86 dylib, is that when started in 64-bit, the Cinema console will give this message with regards to the x86 dylib, and then proceed to load the x64 dylib. In his case, the console prints does not support 64 bit mode twice -- once for each dylib. If he deletes the x86 dylib, then he only gets one of these messages, which mentions the still-present x64 dylib.
Over the weekend, he reported to me that after he 'made a software update with security update' and 'did a repair permissions' that his Cinema installation began refusing to start up in 64 bit mode at all. Furthermore, he then 'made a complete clean install of System and C4D on a separate disk to see what happens' (I assume that he means a clean OSX install) and that the result is that he is still unable to start Cinema in 64 bit mode, and that Cinema is now 'not updating anymore' , whatever that means. He says he has contacted Maxon about it.
So, while my current thinking is that there is probably some deeper machine-specific issue going on here, I wanted to post here anyway to see if anyone else had run across a similar 64-bit-no-load behavior.
On 05/04/2010 at 08:27, xxxxxxxx wrote:
Yes, I've had similar situations from users on Mac OS, and it seems to always be a problem specific to their machine or setup. Normally repairing permissions and reinstalling takes care of it, though.