My Vegas 16 crash at start. Renamed the plugins folder, etc. Error: Initializing GPU-Accelerated video processing... I have a GTX 1080 Ti with latest drivers. Any help, please?

we all have same problem Vegas pro crashes

Maybe we need magix PC and then will work

1.Go to C:\Program Files\Common Files\OFX and Rename the Folder OFX to OFX.OLD.

2.Start the vegas Pro 16

3.Close the Vegas Pro 16

4. Go back to the folder C:\Program Files\Common Files\OFX and Rename the Folder OFX.OLD for OFX

5.Start the vegas Pro 16 and enjoy.

P.S: If you have the FX Home Hitfilm Ignite Pro plugin you will need to uninstall and install again.

I tried this and unfortunately it still didn't work.

In C:\Program Files\VEGAS, I have folders labled: VEGAS Pro 14, VEGAS Pro 15, and VEGAS Pro 16. Each contains lots of .dll's, both in subfolders and loose.

I'm trying to stop VP16 from always crashing after being open just a couple of minutes. Would VP16 try to load plugins from the VP14 or 15 folders, making it necessary for me to rename those folders as well as the VP 16 folder?

In the Program Files folder, There are also folders for Boris, NewBlue, proDAD, WAVES and several others that may or may not contain Vegas plugins.maybe others I don't recognize. Do I need to disguise these as well? Is there something in VP16 itself that will list all the plugins and extensions it loads?

Thanks for any help.

In C:\Program Files\VEGAS, I have folders labled: VEGAS Pro 14, VEGAS Pro 15, and VEGAS Pro 16. Each contains lots of .dll's, both in subfolders and loose.

I'm trying to stop VP16 from always crashing after being open just a couple of minutes. Would VP16 try to load plugins from the VP14 or 15 folders, making it necessary for me to rename those folders as well as the VP 16 folder?

@Widetrack No. They're independent.

In the Program Files folder, There are also folders for Boris, NewBlue, proDAD, WAVES and several others that may or may not contain Vegas plugins.maybe others I don't recognize. Do I need to disguise these as well? Is there something in VP16 itself that will list all the plugins and extensions it loads?

Part 2 of this post should cover what you can try disabling: https://www.vegascreativesoftware.info/us/forum/faq-vegas-pro-won-t-start-what-can-i-do--104784/

General crashing troubleshooting tips are here. Part 10 of it reiterates the above advice (but I didn't mention VSTs): https://www.vegascreativesoftware.info/us/forum/faq-troubleshooting-crashing-and-stability--104785/

This is encouraging. VP15 and 16, Build 307 have been crashing on me--not at launch, but after about 10 min of use. Last night, it got so bad, both were locking up seconds after launch, before I had a chance to so anything at all.

So I spent much of today going through three hard disks, removing (not just re-naming . . . deleting) every, single, 3rd-party plugin I had, a few of which actually had visible signs of mold and insect infestation on them. I was eventually able to launch an instance of VP16 that showed nothing but Vegas plugins. I uninstalled VP 14, 15, and 16, three versions of Sound Forge, and DVD Architect.

I began DLing the VP16 installer, and was surprised to find under the Magix Christmas tree, a new build--#352 (all by itself. I didn't even DL any of the plugs or other apps. I installed and opened 352, and began rebuilding last night's project from scratch. I've had Build 352 open since about 2pm (it's now 11:18), I've edited, rendered and re-edited a small, but memory-intensive project with lots of resizing, flying and zooming images, animated effects, and so forth . . . . and the little beast has performed flawlessly. So far.

If this goes on, I will be one cheerful boy scout. But i do miss some of those plugins. Boris, Hitfilm, NewBlue, the OFX stuff, and a few other usual suspects.

Does anyone have any thoughts about which may hold the least potential danger as I start re-installing them?

Thanks to all for the thought and struggle so many here have put in on this issue.

@Widetrack IMO Boris first. Hitfilm 2nd. NewBlue last.

Thank you, Nick. I'll try that.

Nick, just FYI, I installed The Boris plugin package and saw that all the Boris plugins I remembered showed up in Vegas. Then I began thinking I never really used any of them much, and started looking around. Many of the YouTubes I found were (apparently) about an effect that does not appear in the current version of the Boris/Vegas package--or maybe, anywhere. Then there were the ones that were impossible to follow (I know. I'm old and slow). Then, for the first time since the whole process above, Vegas locked up as I was trying to figure out what the Composite Choker was. So, i guess I'll delete everything Boris from my disk and start again.

One last question: what is the best way to learn about the other effects included in Vegas?

Thank you again for your diligence and help.

@Widetrack This post links to the highest quality tutorial resources that we know of. If you mean 3rd party effects, I'd start on the providers' website and any forums specifically for their products.

Did you people find solutions to the Ignite Pro plug-ins issues ? (mostly on page 1) I'm currently struggling trying to update from HitFilm 3 Pro, things are confusing ... I have a full topic about it here: https://www.vegascreativesoftware.info/us/forum/confused-about-hitfilm-plug-ins-and-where-are-some-of-my-plug-in--114662/

I realise after asking the AlanH as check and answer, however, I have nothing called OfxStitch
Will try installing the version that Nick Hope linked in here above ... though that means Ignite Pro 2 and Ignite Pro 4.

I get the exactly same problems with Ignite Pro 2 as with Ignite Pro 4.

1.Go to C:\Program Files\Common Files\OFX and Rename the Folder OFX to OFX.OLD.

2.Start the vegas Pro 16

3.Close the Vegas Pro 16

4. Go back to the folder C:\Program Files\Common Files\OFX and Rename the Folder OFX.OLD for OFX

5.Start the vegas Pro 16 and enjoy.

P.S: If you have the FX Home Hitfilm Ignite Pro plugin you will need to uninstall and install again.

Thanks very much. This fix let me start VP16 successfully at last after trying for a couple of days but crashing towards end of launch with the DotNet Framework error. 😁

OMG thank you so much man