I just bought MS3. I did not have MS2, but I did mess around with the MF2 demo a little.
I have only noticed a couple of things so far:
I am trying to output my timeline as a .MOV file. If I do it at the highest framesize and bandwith settings, It errors out after about 12-15% of the way through. T attempted this about six times. I did a 320x240 (or similar) at a lower bandwidth, and it was fine. My timeline does contain a lot of video/audio, over 30 minutes worth.
Also, I thought it was cool that this version had the .swf format. However, it was too poor of quality to be useful. Perhaps if I did not have so much video, it would be better. I will try a small clip.
Did you get any error message when the rendering quit? Could it be an overheating problem -- Something can't handle intensive cpu use?
Odd that it would only occur with movs...
I read that thread, so now I will go home and do some testing. My computer was on continuosly for about 4 days and I was rendering a good portion of that, although I did reboot once. I do have a program ASUSPROB that monitors the temperature of the MB & CPU, but I was often closing it to give all the resources to the video software. Next time I will keep it going and monitor it.
My post may have been a little unclear. I was just wondering if I'm giving up anything - features or stability - by moving from Screenblast 2.0 to 3.0?