Yes, it's hard to make Carrara crash and that's a very good thing. :) By definition, everyone that uses software is a crank when things don't work as expected. The way it seemed to work in Beta 4 and 5 was that some bug fixes (usually the annoying ones) were rolled into the next version. Serious bugs that fail operations or crash the program are dealt with in patches. Some seemingly "simple" bugs actually have required substantial code rewriting. In fact, there were a couple I was aware of from v3 that weren't remedied until v5 because they were nestled so close to the core that fixing them meant retooling how things were done throughout the application. Up to release 5 there was no word of making a UB version for the Mac (an unscientific survey went out asking how important UB was - I think you can find it in a thread here in fact.) The UB porting has all been done after the V5 release and it's no small task. (Just for comparison, Adobe isn't even planning on releaseing UB versions until spring/summer 07) So, my guess would be that core functionality and porting to MacIntel has taken precendent over lesser bugs up to this point. If I remember correctly, new functionality was coming at the beta testers like crazy 8 months ago - all with new bugs to work out. And bless their hearts, the development team loves new features. Next was cleaning up everything in the new features for the Gold Master. I've been involved in other beta cycles for software completely different than 3D stuff but the bug/feature/upgrade methodology seems to be the same for those as well. We can all agree that new features and old bug fixes never come fast or clean enough! :D