Not trying to discourage you from creating a Carrara bug list, but with a supposed patch coming out soon, some of it may be irrelevant shortly. You may want to hold off putting a lot of effort into this until the patch arrives. To make the list useful, it would have to be categorized ie to allow anyone to locate and match up a bug they are experiencing with what's on the list. Part of the difficulty would be categorizing the bug list - ideally there should be 2 - 1 PC and 1 Mac version for bugs that are present only on one platform. Then to categorize by area, such as the VM, Spline, etc. which would be a lot of work. Some of the bugs have good workarounds, some don't, but the workarounds would be useful - but for anyone already using C, they probably have figured a lot of them out. As far as Eovia fixing them, this may be another difficult area to assess. I've sent in quite a few bug reports, mostly serious/crash types directly to Eovia, without any response. Secondly, Antoine specifically pointed out some time ago on the Carrara list (Yahoo) that the bugs should be posted directly to the Eovia site - stating to the effect, that if they weren't reported, they couldn't fix them - your bug list may get ignored. Although I never saw any, there were previous bug lists prepared and you may only be duplicating what someone else has already tried to do. Given that we've only had 1 patch in over a year and that Eovia is working on Version 2, the bug list for Version 1 might be only useful to someone who choses not to upgrade. Pardon, if this isn't what you wanted to hear, but I wouldn't want to see someone spend a lot of time and effort in a large undertaking as this and find it largely ignored or unused. It's a fine application. But I won't recommend it to anyone due to the bugs. I know a couple of users on both platforms who couldn't get it to run at all. regards John Spirko