I can't help you but I can tell you that I've seen the same thing. Sometimes just closing the application and relaunching will fix it (I mean successfully complete a render). Sometime I have to completely reboot the machine. There is no common thread that I've noticed. I've had problems with big projects and small, the whole timeline or just a segment. I've never had it occur where I was completely unable to render no matter what method I tried.
On Vegas32 and XP32 this has happened to me a few times. Project says 100% complete yet is just stuck there with processor at idle.
Oddly enough though,...one time on an overnight render, I looked at it in the morning and it was frozen like that. Disgusted, I said "screw it" and left it that way all day. I left the house and came home 9 hours later only to find that it "unfroze" itself.
However, if the clock is still running, and there is disk activity, let it run. The "estimate" is often far wrong esp. for highly compressed output, and it just needs to finish what it is doing, even if it seems to take a long time.
Vegas 8 did this a lot and I just had 9 freeze up a couple of days ago. For me the render always completes and I can open the file and watch it but I have to kill Vegas with the task manager.
Yes, I suffer from this as well (8.0c, XP Pro SP3). It's clearly not the isolated problem I was beginning to think it was. I'm 'pleased' there are more people than just me with the issue.
Must get the hang of this forum structure - possibly one of the most user-unfriendly I have ever come across! I've just posted this message twice as a new topic by mistke - what a dumb place to put the New Topic button! Well, for slow-witted people like me, anyway! And is there any way to subscribe to threads? Can't see how.
Anyway, this post-render hanging problem has been bugging me. As an experiment, and based on a comment on the DVi forum, I turned off Excalibur's Autosave feature, restarted Vegas, rendered a short project segment, then left the 'render complete' dialogue box open for ten minutes to see if the problem would manifest itself. I repeated this five times with the same project/render segment but I could not reproduce the problem.
I then turned Autosave back on with (I think) factory settings) and repeated the above process. On the very first render the problem occurred within a minute of the render completing.
Now, this is certainly NOT a scientific test and the problem is annoyingly random, so it could just be a coincidence. More to the point Edward Troxel says that Autosave is turned off when a render starts so shouldn't be the cause, however, it would be interesting to know how many people who are suffering from this problem are also Excalibur or Autosave users.
Advice from Edward Troxel is (until the issue is resolved) make sure you do a filesave before rendering so that Autosave does not try to save the file before the render complete dialogue box is displayed.
Looks like this is what has caused the issue for some of us, almost certainly any users of Autosave.