I'll try that, fr0sty, thank you.

Hello,
I guess you have the latest build of VP 16 (424)?
Do you look in the task manager to make sure that Vegaspro160.exe is not always running, before relaunching VP?
Disk cleaning can help (Ccleaner or others).

I've been having this problem for ages now. I'm currently using Vegas 15. Does not matter if it's a complex project or a single file on the timeline. I usually have to click render as about 5 to 9 times (always hard crashing as a result) until finally for no reason it decides to open the render dialog box then works until I close and restart the program. Tried contacting tech support in the past but they were so useless I gave up and migrated mostly to Resolve. Still prefer Vegas for photo montages but I've come to hate using it because of the render crashing. For the most everything else Vegas is stable for me but if you can't deliver the project without extreme frustration what use is it?

download the 17 demo tomorrow and see if it still does the same thing. 15 was the worst with the render as crashes.

download the 17 demo tomorrow and see if it still does the same thing. 15 was the worst with the render as crashes.

How much time to wait for 17 yet？

I answered in the other thread where you asked... it is only just after midnight on August 5 in Central time in the USA where Vegas Creative Software's office is, chances are they will post it when they open up tomorrow morning. I wouldn't expect it for another 6-8 hours at the earliest.

I answered in the other thread where you asked... it is only just after midnight on August 5 in Central time in the USA where Vegas Creative Software's office is, chances are they will post it when they open up tomorrow morning. I wouldn't expect it for another 6-8 hours at the earliest.

Thanks.

Thank you all for your suggestions. I am running the latest version of VP16 by the way.

Before I started my day, I decided to try something (I must have dreamt this!). I went into each of the settings pages where I had made changes, tried to note down what changes I had made, then pressed the set default button for each of them.

Voila! The project is now rendering. A lot easier than setting Vegas completely back to default settings (layout, colour scheme, windows etc) so it will only take me a few clicks to get back to where I was.

Many thanks to all. This has always been a great forum!

It would be cool if we could isolate the exact change that made the problem occur, might prove useful to future users or the dev team.

It is (as far as I believe) fixed in VP-16 424, but you have to deinstall Vegas first, then run Ccleaner regcleaner, then reinstall Vegas Pro 16 424. When I did this, I never had a Render As.. -crash again!

I went into each of the settings pages where I had made changes, tried to note down what changes I had made, then pressed the set default button for each of them.

Voila! The project is now rendering.

@JohnAsh

On the Video Tab, see if "GPU Acceleration of Video Processing" is the culprit. It was on my system.

I'll try reinstalling, joostberk, though I'm rather wary of registry cleaners!

And I think you might be right Musicvid (GPU acceleration). However, if I copied a few random scenes onto a blank timeline and then "render as"', it went ahead and rendered without dropping out. So something in my project is not liked by one of the settings! At least the render is done now and I know I can overcome this problem (which happened before a month or so ago with an earlier project) without too much disruption.

And yes, if I manage to pin it down to one setting, I will certainly share it here. Ever since I bought a GPU card I have had the acceleration box ticked but it does seem to be a likely candidate. In VP16, though, in order to get the GPU direct display on my second monitor to work (I was losing the ability to switch back to the main VP window) I had to untick a couple of options in the settings relating to display. (Sorry can't be more specific here as am away from my main PC).

I have done more testing to try and pin this down. It is not easy as the project is a large one and takes ages to load, only to crash out again when I go to render it!

I am not now sure that my trick of resetting all to default was the key to allowing me to render. With everything set at default, I just loaded the project, went through all settings I might have changed and pressed the reset to default button, then pressed 'Render As', Egg-timer for a second or two and crash, it's gone!

So I loaded a very simple VP project with a few overlapped stills to render, press 'Render As' and, voila, I get the -'Render As' window up. I then loaded the problematic project, 'Render As' and, hooray, I can render.This is as recommended here by Fr0sty:-

fr0sty wrote on 8/4/2019, 2:16 PM

Until we find the source, one way I usually prevent these crashes is to open a blank project, drop media in, click render. usually the render as dialogue will open then. From there, open your project and render as usual. It doesn't work for everyone, but it helps me.

Thank you Fr0sty. But it really shouldn't be necessary to go through all these hoops and waste so much time trying to do something so basic. I have no idea why I keep paying out good money for upgrades to VP!