Heh. Same here -- the majority of the bugs I've had, I was working quickly and doing a million things, and there isn't a way I can narrow it down to "THIS keystroke sequence crashed it." Which is bad news for me...when I'm naming groups before export to Poser, I spend a lot of extra time doing "detach polygons" and saving, before and after applying the name. All I know is that Carrara used to crash all the time while naming groups, and it doesn't crash for me now, and saving after every keystroke is still faster than recovering from a crash. Most of the annoyances I've encountered are technically not bugs, however. It would be more accurate to call them poorly implemented and documented features. Such as the preview window in the Texture Room having no memory (very annoying when working on a small object). Or none of the radio buttons having memory. Or the way the standard control-A to select all, control-z to undo, spacebar drag to move view doesn't work in the UV Mapping Room (nor does it have memory for size, options, or selections). Come on, fellows -- if you are going to go with this "room" analogy, the basic view and navigate controls should be the same for all. I also understand why it would be counter-productive for the programmers to engage in dialoge with bug-finders. Simply put, most of the user complaints will be user error. The programmers haven't time to walk users through the manual, email after email. However, an automated "your bug report was recieved. Please do not reply to this address" would be great.