Without needing any scripting at all ... open up as many Vegas instances as you have renders to do. Start a render running in each one. Go to bed.

Thanks guys, never thought of just opening vegas multiple times and letting each one run - I'll try the free version tonight!

You could also use network rendering; a second machine is not necessary, run it on the editing machine. The renders run one at a time from a queue. Thus no conflicts for RAM and no potential for page thrashing.

interesting - so how do I do that - I tried opening multiple copies and network rendering with the box for distributed rendering check and unchecked and neither started a render - just sat there.

It should start a new, background, instance of Vegas which performs the render. The instance of Vegas that submitted the render request is now ready to do other work, for instance submit another render request. In this manner I build a queue of render requests and then go on with other work (or go to bed). Once the render request is submitted, the submitting instance can be closed or loaded with another project.

Tried follwing what I thought you meant - opened a blank Vegas and 2 more with projects - the two with projects started render as networked computers - looked at Sony Render service - both show they are in the que but never move beyond being ''queued
"

I remember some problem like this when I first tried network rendering, but I can't remember the details or how I got around it. Maybe I can dredge it up...