D
Title says it.
It didn't bother me much, since it didn't seem to have an effect; the few plug-ins (that I really use at least), all worked just fine, so I did not pay much attention to those messages.
But, since I'm trying to pick up my python-learning topic again, I reviseted a little generator plug-in that i wrote a year ago, that worked r19 but now doesn't in r20.
In the process of looking into it to make it r20-able, I stumbled upon that "collision"-message.
So, first thing I tried: I got a new Plugin Id from here, but that didn't change a thing, message still shows up.
So I tried another pc, installed a fresh verion of cinema with 0 plugs installed. Then I tried 1 plug after the other and with every plug I get that message.
no matter, if commercial, self-written or anything. every plugin shows the same message. But nonetheless the then installed plugin works.
Well...
when it comes back to my own written one, that I originally just wanted to port to r20: it works for me - on my workstation and on the other pc I tried it on. but it doesn't work for people, I sent it to. The erreor message says: "...AttributeError: 'module' object has no attribute...".
So:
My self-written plugin runs on two of my own pc's. but any plug in I install on either one of those pc's shows a Plugin ID message - but without having an impact on the workability of any installed Plugin.
Other people that I sent my selfwritten Plugin to say, that my Plugin doesn't work for them, showing "..."...AttributeError: 'module' object has no attribute...".- message.
I have not heard of any Plugin ID problems whatsoever on their systems though.
I wonder, what the problem could be, I am not even sure, how/why those two aspects are entangled. If at all.
Not sure, how to go forward from here on.
Any ideas?
