Build 321: Projects Error out upon opening Veg file

j.razz wrote on 10/13/2019, 3:02 PM

I started a project back in Vegas 15. Opened it in Vegas 17 and saved a new Veg file. Edited on it for some time, then had an issue where it became sluggish. I updated to build 321, rebooted, and reopened my project where I was greeted with the "send error report window". I tried multiple ways of opening the Veg file and was finally successful. I rendered out an intermediary file and started a brand new project in Vegas 17 build 321. I took the intermediary and placed it on the timeline, edited for a bit and then closed it out and reopened to be greeted with a send error report window again.

Here's how I was able to work around this: Open Vegas to a blank project (rather than clicking on the recent project list or veg file directly). Then go to open and navigate to the veg file you want to open. That is the only way I can open the project files.

The media was a combination of Canon 5d MarkIV 60p files and Phantom 4 pro 60p files.

My system is a Razor Blade 15" advanced laptop 2018 model with an Nvidia GeForce GTX 1070 gpu, intel 8th gen i7 6 core cpu, and 16gigs of ram. Here are more specs: https://support.razer.com/gaming-laptops/razer-blade-15-2018/

Anybody else experiencing this?

Comments

j-v wrote on 10/13/2019, 3:27 PM

Looks like this one: https://www.vegascreativesoftware.info/us/forum/vp17-vegasaur-crashes-on-opening-with-a-saved-project--116732/#ca731313

j.razz wrote on 10/13/2019, 3:35 PM

Thanks for that j-v. I did look prior to posting, but I missed that thread. It doesn't seem like there's a resolution (from the 3rd page of the threads), but hopefully an update from Vegasaur will fix the issue and make the workaround no longer necessary.

j-v wrote on 10/13/2019, 3:48 PM

I also use Vegasaur, don't see that error with it and I should not know what is the fault. I think it must be the combination of all kind of ( Windows) settings with other(?) settings.

j.razz wrote on 10/13/2019, 3:49 PM

Perhaps? I have no idea what the culprit is, but am thankful I can still open my projects after the update by opening a blank project and then opening the veg file from there!