1. There is a free demo you could have used to test it out on your system.

2. Instead of whining, try asking for help. It can get you a long way around here towards finding a fast solution. In most cases, simple fixes like GPU driver updates often solve these issues, which are often specific to certain system configurations.

I got latest NVIDIA Drivers - 431.60

Didnt know there are stdio Drivers. Thought the are only for RTX Studio Laptops.

Well Vegas 16 worked.

Nvidia releases gaming and studio drivers for its GPUs now. Give the studio driver a shot, and if it doesn't work, we'll move down the list of things that could be hanging it up.

Vegas is one of the least restrictive NLEs out there when it comes to hardware configurations, but in doing so it can be hard to make sure each of the dozens and dozens of possible hardware configurations that meet minimum specs works just right in all situations, espcially when dozens and dozens more driver versions, windows update versions, etc. are thrown into the mix on top of that to complicate things even further.

Something added, updated, or changed in 17 broke compatibility with your specific combination of drivers, OS, and hardware. It's unfortunate, but it happens and it's usually fixable.

This is an abusive nonsense post that breaches community guidelines. Should be banned.

This is an abusive nonsense post that breaches community guidelines. Should be banned.

Abusive for what? Making a 700$ software that doesnt work???

Nvidia releases gaming and studio drivers for its GPUs now. Give the studio driver a shot, and if it doesn't work, we'll move down the list of things that could be hanging it up.

Vegas is one of the least restrictive NLEs out there when it comes to hardware configurations, but in doing so it can be hard to make sure each of the dozens and dozens of possible hardware configurations that meet minimum specs works just right in all situations, espcially when dozens and dozens more driver versions, windows update versions, etc. are thrown into the mix on top of that to complicate things even further.

Something added, updated, or changed in 17 broke compatibility with your specific combination of drivers, OS, and hardware. It's unfortunate, but it happens and it's usually fixable.

Thank you so much Sir, I'm not getting GPU driver crash anymore. But still have problems opening Projects and Also VP17 doesnt proxy 4K files Automatically anymore. I have checked the box in Preferences - Video , for that, but now the box says "Proxes Files LARGER than 4K". Any chance you could help me to figure out if I can proxy 4K files? Thats a fault module i get when software crashes - C:\Program Files\VEGAS\VEGAS Pro 17.0\FileIO Plug-Ins\mxhevcplug\MXVideoAllocator.dll

Yeah, since they upgraded to 8k support that setting got changed. You can still proxy your 4K files by selecting all the files in your project media pool with crtl+A, right clicking on them, and selecting build proxy. I'll mention adding an option to auto proxy other resolutions as well, maybe they'll add that in a future update.

I can't reproduce your issue with opening old projects... but there are some third party plugins that have to be updated to work right with Vegas 17, so if you were using third party plugins in those projects, that may be where the problem lies.

You can still proxy your 4K files by selecting all the files in your project media pool with crtl+A, right clicking on them, and selecting build proxy.

Beware that this is only possible if you select in Project Media more than 1 file.
if you select one file(1) the option is greyed out.
That is the case in my installed Pro 17

Also, you can set your minimum X and Y resolution for "autocreating video proxy" in the internal preferences.

As a courtesy to users who may experience the same issues that you bring up in here, please mark that last post as a solution if updating your plugins works to solve your issues... then the mods can change the thread title to something that would indicate you had that problem (so it pops up in their google searches when they search for how to solve that problem), and those folks can easily find their way to the solution.

Yes, that would be a much better approach than dropping F bombs, and universally condemning Vegas as "Unusable Garbage." Be respectful and people will help you.

This reminds me a little bit of when Magix released V14. This is the battle testing part for Vegas and once it clears these waters, we all end up with a solid performing software. I wish people could see squashing bugs as a community activity and actually a good thing because we all end up with a better program in the end. Embrace the bugs. Report them. And we all win on the next build.

I started testing this version today. I still have 29 days left to reach a sensible conclusion.

So far I'm liking the new features. They are doing what they were designed to do.

Just Vegas SlowMotion that is generating some weird artifacts, a sort of preview glitch and Vegas Screen Capture that doesn't work here.

But it is still early to reach a conclusion. I will do more tests.

I think it's a good decision for me that I'll stick with VP16 & buy Vegas 17 when I see a release of a 3rd or 4th build. Until the huge waves have calm down.

What huge waves? The reports so far have been minor at best, nowhere near as bad as the so4compound catastrophe that was Vegas 15 and 16's constant render as crashes, or the disaster that was 14 (crashed all the time, couldn't open half the media I shot, etc). 16 also had bad installation issues at launch. I'd say this has been a pretty smooth rollout. All of these issues have been easily fixed (make a new encode preset, update your drivers, update your plugins, etc) other than Veg's slow motion report, which I too have found to be the case sometimes (but can usually get around it by setting the quality to a different setting).

Download the demo, that's the best way to see if it's ready for your productions or not.

+2 (Just followin' ya' round frosty ) 😀

Ignore the histrionics from some new users. Behaves pretty similar to V16 as far as I can see. YMMV.

"Huge waves" of users posting about something's not working or something compatible for them is broken that is what I mean. I love Vegas but let's face the truth here that every 1st roll out of a new version no matter what software it is there will be some minor or even major bugs, that is why build updates/patch are given for improvement purposes. I'm not saying anything wrong about Vegas or it is buggy, I'm just stating my opinion at the very least that, when it it is smooth in the roll out then I would buy it after it's become smoother by means of waiting for updates. Patience is the key.

There are 10 threads and one post in the news forum regarding users who experienced problems on this forum, and of those 10, they all were traced back to 6 unique issues, most of which have easy fixes or workarounds: issues with needing to update the GPU driver for Vegas to work, installation issues due to a conflict with Boris FX, issues with plugins needing to be updated to work with 17 (which could tie directly into that last issue), issues with imported custom render templates not working, and issues with artifacts in the new slomo plugin, and a couple users are reporting that the screen capture window is coming up blank for them, though it isn't for others.

I can't help but see referring to that as "waves of people reporting problems" as a bit of an exaggeration. If you'd been around for the previous launches, you'd know this one has actually gone quite smoothly. No major issues that make editing a nightmare, no reports of frequent, random crashing... I'd say things are going pretty smoothly.

Well, it's a good news for me to hear & not trying to argue here, but it's just the 2nd day for V17 & you did count the postings & enumerated them, so it's too early to judge me that I'm exaggerating here, wait for a few days or weeks, then there will be post just like this reporting a minor glitch found or even disappointed user dropping f or whatever you call that, cause it is still under testing for the improvement of the next build. It's not the rule of what features works for you & it does not for 'couple of others' means it will not be counted, they just reported it cause they've experienced it with the new version.

So, I repeat, what I have been waitin here is just a refinement of the minor reported issues (a build update), so that I can buy Vegas 17 & ride my projects comfortably.

Not buying the first batch is good practice with any technology, but fwiw I was able to complete a 2.5 hour long 4K 4-camera multicamera project in Vegas Pro 17 with minimal issues, far fewer than I would have expected to see in the most recent build of 16.