THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 05/12/2009 at 11:01, xxxxxxxx wrote:
Originally posted by xxxxxxxx
assuming that you had versions (before) without 64 bit binaries:
- old dylib with just 32 bit binaries and new one (with 64 bit) installed
- customer put (or installed) the new plugin version in the wrong location
thanks again. Point 2 and 3 were the first things I checked with the customer. All fine (I told him to search the whole c4d installation folder including subfolders for any .dylib files and the according plugin dylib was single. Also he removed all plugins and only installed mine. Still no luck unfortunately. Also there was no 32-bit only version available before, included 32/64 bit from the day of release.). He also said, he just cleanly installed snow leopard and C4D.
Concerning point 1, the file structure seemed absolutely fine (he showed me screenshots) and he redownloaded my plugin archives several times (with me providing him the correct links), also with several browsers (Safari and Firefox).
I´m really lost as I have absolutely no idea what the problem could be (of course I am worried that other customers may also not be able to run the show, especially the demo, which would be very bad). This is a bit strange. :-( My gut tells me that it maybe is an exceptional case but can´t stop panicing somehow.
Well, the only thing I can really think of is that the files are somehow corrupted. That would make sense as the rest works fine (installation, folder structure, the fact that it works for my testers and that this never happened before with any other customer).
Well, ok. If there is anything else you can think of please let me know, otherwise I will double check everything with the customer again. Maybe we missed something *cough*
Thank you for the quick input