"Exception thrown by method called " Error

Rozark wrote on 11/20/2021, 4:23 PM

Product: Vegas Pro 14 64bit Build 270
OS: Windows 10
GPU: Nvidia GTX 1050 TI

 

I recently tried rendering a new project using the "Render As" option but it wouldn't take me to the menu to select my render options. Instead, a dialog box appears with the phrase "Exception thrown by method called ". Now, I've been trying to fix this for the entirety of the past two days. I've scoured the first five pages of Google results and nothing has worked nor has anybody come up with a practical, working solution besides "just pay more money to upgrade". I don't have the cash. The only program I've installed between the last time I rendered a project and this time is Visual Studio Community 2019, but I don't think that would do anything. Please, I need this fixed. Heads up, I'm not very "video quality" technical, so I ask that you get a little more specific if you ask those questions. Here's a list of things I've tried:


1) Scripting -> Render Batch. Yes, I've tried it. No, the options listed do not include a 1920x1080 60fps option. I've tried converting to a 60i option then converting that to an mp4 with an additional program but have had no substantial luck. This is not a long term solution and it's avoiding the problem.
2) File size renames. All of the files involved are named with single letters or numbers. This doesn't work.
3) Enabling .net framework options in Programs/Features. I've done this. I restarted the computer afterwords and tried combinations of this + 4 and 5. This didn't work. I also saw a thread about a bunch of people going at it saying this was probably the issue, so I checked, and I have the most recent .net framework (4.8.numbers).
4) Ctrl+Shift+Double Click to start the program. Cache gets cleared, error still persists. Nothing here.
5) Fresh reinstall. I did this. No luck.
6) Changing the render folder location. It's been on both my C and D drive and the error still occurs.
7) Being aware that Codec packs can cause it to break. That's cool and all, but I don't install random codec packs as I rarely use this program to begin with.

Comments

harry-worth wrote on 11/21/2021, 2:48 AM

Did you try this fix

It appears that it need all these Top 3 items ticked

NET Framework should already be ticked

The two below need to be ticked

and restart

 

Rozark wrote on 11/21/2021, 7:58 AM

Did you try this fix

It appears that it need all these Top 3 items ticked

NET Framework should already be ticked

The two below need to be ticked

and restart

This is number 3 on the list of things that I presented in my original post that I have already tried, yes. I even have all of ".Net Framework 4.5 Advanced Series" enabled. If you're referring to the option under your cursor, I cannot see that option on your screenshot because text is over it.

harry-worth wrote on 11/21/2021, 10:05 AM

Hi Rozerk, No it was only the 2 item under the Header. OK well will keep looking.