I have a bug list on my web page. I think it would be useful if there was a single someplace we could post our bugs for the Eovia folks to access them and then fix em'. Is there such a place? Can Renderosity create such a space?

There is already a FAQ space on this forum, but it's hidden to you folks because it's empty at this time . You could send your bug list to me and i will post it here . Thanks . litst litst.@freesbee.fr

Here's my site. http://www.concentric.net/~Franzs/cdp/index.html I set up this page to look like it's a group of people but actually, it's just me at the moment. I have a friend who's going to be helping me with a project and so making it look like it's a group of people is more sharing for credit. There's a link on the page which describes my RDS to Carrara transition experience. The bug list is in there.

I noticed a bug you forgot to list... Carrara's Manual says that it can use Photoshop FX filters; This is a lie. They meant to add this feature, wrote it up in the manual, but never implemented it. I got confirmation on this from MetaCreations a long time ago. --

Setting an exhaustive list of Carrara's bugs would be an never ending story !... For example, a bug i've never heard about : try to apply a spike deformer to an object, you'll see that some polygons are missing . I could continue for long ! litst

Well I think there is a significant value to creating a list. I've only truly been compiling this list for about a month and I'm actually just learning the program. I'm a little reluctant to say I'll keep the list but I can give it a try for a start. If people e-mail me the bug in the format to fit into the table on the site (i.e. send me the information to put into the four boxes in each row), I'll post it. If we could do the FAQ thing, I think that would also have a lot of value. What do you all think?

Well, i think a FAQ with some walkarounds ( workarounds ? not sure of the word ) would be more helpful than a bug list . If you all help me, we could set that up in May . Of course, it will grow over time ... litst

I found some bugs that werent listed on the faq- Camera 1 Keyframe Limits: Carrara gets confused when Camera 1, your active camera, has more than about 15 keyframes. Once you get past thoat point, you cannot move/rotate/dolly/pan/bank the camera until some keyframes are deleted. Render Failed Part 2: You listed a Render Failed Bug, I noticed it also occurs in some booleans. Sometimes the bool will work, sometimes not. Seems random. Saving Movies: Sometimes, when saving QT movs, Carrara bugs out and crashes. However, the mov file is intact, but any changes in the scene file are lost. Sometimes this crash can be avoided by going to the assemble room, saving, and then tryting to save your movie. But that doesn't always work. *Note-These may or may not be Mac specific. These all occured on my iMac DVSE '99, 256 mb ram. Nebula Supernova Studios

One bug that bugs the hell out of me is the way Carrara renames all the groups 1 to whatever once you save a obj inside a Carrara file that you have imported, then close and reopen it. This seems to be mostly with Poser figures imported as a single group using a layers list for the textures. Just my little rant..had to rebuild the model I was working on from a saved version because I imported a poser figure to check the scaling of the model. Later Ed

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

I'm a proffessional software developer (70% of my job anyway) and all the things you've mentioned are absolutely dead on. If you'll notice in the original post, I was reluctant to "hold" the list and was more interested in an FAQ on this site which is more appropriate. Some things. 1.) I have posted bugs to the Carrara site at Eovia and I've actually received reasonable feedback. If your experience is older, perhaps you should give them another shot. 2.) There's been some chatter about another patch (past 1.0.1). I think it's probably going to be Carrara 2.0 and we'll all be buying it. They're supposed to be releasing it this summer. It's a complete supposition on my part but probably accurate. 3.) I am another person who couldn't get the code to work out of the box and had to apply the patch. All the work I've posted on this forum has come from Carrara as well as many others so it does run. I've been a Ray Dream user for many years and the transition hasn't been painless. Making the change requires some significant effort on a person and I know many haven't made that jump yet. That's fine because I truly hope the next version will be a lot more stable and hopefully more powerful. I thank you for your comments because I think they're the realistic side of keeping a bug list. Keep posting.

As John pointed out, what would be really useful at this point is a list of workarounds . I'd suggest we start to make a FAQ on this forum when the patch will be released, so that we don't lose too much time creating it for only a few weeks ... I'm sure we'll have some bugs left to entertain us after the patch ! ;) In the meantime, when somebody has a technical question, there's a lot of advanced Carrara users here who are glad to answer . litst

Hello! I agree - start the FAQ after the patch comes out and concentrate on the patched version where possible. I'd also suggest that you create a rough template or format for reporting bugs/workarounds - similar to what many companies use for beta testers/bug list. Ideally, it would list platform(s), a specific area of Carrara, ie VM, Spline, Assembly Room, etc. so the user can more easily locate the bug/workaround. As well as posting bugs with no known workaround, other than frequent saving - simply to make the user aware, or the possibility that someone does find a decent workaround later on. And perhaps, just do a small trial run concentrating on one area first and ask for feedback to see if people are making use of it. regards John Spirko