Vegas POST, Vegas Effects does not start.

set wrote on 11/12/2019, 7:20 AM

Do you have additional OFX installed?

If so, try moving them temporarily and see if it helps

Go to C:\Program Files\Common Files\OFX

Move the content to, perhaps like C:\Program Files\Common Files\OFX off

Add:

to keep working in Vegas Pro, but 'disabled' in Vegas Post:

Move "BCC_OFX_3DObjects.ofx.bundle"、"BCC13_OFX.ofx.bundle"、"NewBlueFX" to "C:\Program Files\VEGAS\VEGAS Pro 17.0\OFX Video Plug-Ins"

Ref:

https://www.vegascreativesoftware.info/us/forum/bug-of-vegas-effects-puppet-s-edit-mode-to-animate-make-png-warp--118321/#ca738657

diLuciana-Marcis wrote on 11/12/2019, 8:51 AM

yes, I had HitFilm express installed, of course I removed it before writing the post.

before asking for help I usually try them all ....

By the way, it is quite strange that the folder in which VEGAS EFFECTS is installed is the same as HITFILM: "/ FXHOME"

diLuciana-Marcis wrote on 11/12/2019, 9:04 AM

yes, I had HitFilm express installed, of course I removed it before writing the post.

before asking for help I usually try them all ....

By the way, it is quite strange that the folder in which VEGAS EFFECTS is installed is the same as HITFILM: "/ FXHOME"

In the folder \Program Files\Common Files\OFX, however, there were 3 plugins:
HitFilmVegasBasic.ofx.bundle (removed along with HitFilm)

but they still existed:
BCC_OFX_3DObjects.ofx.bundle
is
BCC11_OFX.ofx.bundle
I tried to remove them individually, and going by exclusion it seems that the problem is due to the presence of BCC11_OFX.ofx.bundle
in fact removing this folder now VEGAS EFFECTS starts correctly.
Thanks 😊

alifftudm95 wrote on 11/12/2019, 9:19 AM

Hi, I just bought VEGAS POST suite. 🙂
I have carefully followed the installation and activation instructions: 👀
Vegas Pro 17 (OK) 👍
Vegas Effects (OK) 👍
Vegas Image (Not Required ?)

Unfortunately, Vegas Effects does not start. 😕
 
It was successfully activated by starting Vegas Pro, right click on timeline -> edit in vegas effects, but at this point see the Vegas Effects startup logo, but immediately after that the software window closes and does not even appear in the activity management list ...😟

I tried to restart the computer, but the problem remains. 😕
The system: I7 8850 - 32GB - NVIDIA QUADRO p3200 6GB - WIN10 64 💻

Please help!

I have the same problem. Contacted Magix but still unable to resolve the error. But they did said "repair each installation of C++ redists" which is Im not so sure how

alifftudm95 wrote on 11/12/2019, 9:19 AM

Do you have additional OFX installed?

If so, try moving them temporarily and see if it helps

Go to C:\Program Files\Common Files\OFX

Move the content to, perhaps like C:\Program Files\Common Files\OFX off

Done this, still wont load up

diLuciana-Marcis wrote on 11/12/2019, 9:33 AM

C++ redists" which is Im not so sure how

https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

fr0sty wrote on 11/12/2019, 10:04 AM

I'm in the same boat, and I already had to repair my C++ redists to get Vegas working very recently (had to uninstall it, then it wouldn't re-install until I did all that). I'm looking forward to trying this software out!

diLuciana-Marcis wrote on 11/12/2019, 1:16 PM

are you talking about the same version? VEGA POST?
What exactly does not start?
Vegas Pro (version 17?)
Vegas Effects?

[...] A common solution there was to make sure there are no issues with C++ redistributable packages from Microsoft.

Start > Control Panel > Programs > Programs and Features.

Once the list of installed apps is populated, use the search box in the top right to search for "Redistributable"

Find the latest version of each redistributable, for both x86 and x64

Select Microsoft C++ Redistributable, right-click and click on Change.

On Microsoft C++ Redistributable Setup, click on Repair.

Click on Close once setup is successful.

repeat for all - I'm not actually sure which versions Acid Pro 8 uses, but my system had updates for 2012, 2013, and 2017 installed on the same day as I installed Acid Pro 8, so start with those.

reboot

try installing again [...]

Then repair installation of VEGAS and restart Windows

set wrote on 11/12/2019, 4:15 PM

I'm in the same boat, and I already had to repair my C++ redists to get Vegas working very recently (had to uninstall it, then it wouldn't re-install until I did all that). I'm looking forward to trying this software out!

errr... so... the steps is:

uninstall any Vegas Pro / Vegas Post
install overwrite the new C++ redists
restart Windows
reinstall Vegas Pro & Vegas Post ?

diLuciana-Marcis wrote on 11/13/2019, 6:48 AM

Maybe I was luckier, there were no problems with MS C ++ REDIST.
it was enough to delete (or rename) the BORISFX folder BCC11_OFX.ofx.bundle into main folder \Program Files\Common Files\OFX. no additional software editing / installation was required

erkki-halkka wrote on 11/18/2019, 12:03 AM

I had the same issue - and cleaning up the OFX folder worked for me too.

Deleting BCC11_OFX.ofx was not enough though, there was still something else that was crashing Vegas Effects in my OFX folder. Clearing everything except Neat Video worked. I didn't go through the trouble to isolate the specific offending plugin.

alifftudm95 wrote on 11/18/2019, 8:33 AM

Do you have additional OFX installed?

If so, try moving them temporarily and see if it helps

Go to C:\Program Files\Common Files\OFX

Move the content to, perhaps like C:\Program Files\Common Files\OFX off

Oh damn this does fix the crashing error. But the problem now plugin inside VEGAS Pro also is disable. Anyway to separate it?

fr0sty wrote on 11/18/2019, 11:30 AM

An update will be required either to Vegas Effects or to the plugins causing the issue, most likely. The above did fix my problem as well, with NewBlue being the offending plugin folder.

Now I'm rendering a 30 second animation using atomic particles... it's been rendering since last night and it's still only half way done. Definitely slower than After Effects doing the same task, though the plugin suite needed to make After Effects do what Atomic Particles does costs an additional $1000, so, I'll take it.

Brent-Jensen wrote on 4/16/2020, 2:59 PM

BCC13_OFX.ofx.bundle was causing VEGAS Effects to crash on my system, so I moved it out of the OFX/Plugins folder. Does this means that I cannot use Boris Continuum and VEGAS Effects at the same time in Vegas Pro since they cannot coexist in the OFX/Plugins folder? Or am I missing something?

bitman wrote on 4/28/2020, 4:13 AM

@Brent-Jensen Exactly! You cannot use Boris Continuum and Vegas Post (Vegas effects) product at the same time in Vegas Pro. This has been an issue from day one since Magix introduced Vegas Post. I have several forum posts on this.

bitman wrote on 4/28/2020, 4:20 AM

@set "resolved" and "solution" to the forum post is perhaps correct towards this post and it's title, but it is just a workaround that creates a new issue, namely that Boris FX (or even some old NewBlueFX) does not work anymore...

set wrote on 4/28/2020, 4:37 AM

Agree, putting out from ofx will cause other application that using ofx, unable to detect it...

here's the other alternative method to keep working only in Vegas Pro:

Move "BCC_OFX_3DObjects.ofx.bundle"、"BCC13_OFX.ofx.bundle"、"NewBlueFX" to "C:\Program Files\VEGAS\VEGAS Pro 17.0\OFX Video Plug-Ins"

Ref:

https://www.vegascreativesoftware.info/us/forum/bug-of-vegas-effects-puppet-s-edit-mode-to-animate-make-png-warp--118321/#ca738657

**Above comment post has been updated with more info

bitman wrote on 4/28/2020, 7:50 AM

@set That may indeed work for Vegas alone, I have not tried the alternative method back then, as I have other NLE's I use which support Boris, and as a consequence would lose Boris OFX in Magix's own VPX (Video Pro X), and some NLE called Blackmagic DaVinci Resolve which I find somehow difficult to master...

Maybe the lack of a official fix (in Vegas - and/or boris/Vegas post) to the OFX compatibility issue is perhaps that Boris and Vegas Post's hitfilm source are both competitors and are not keen on the other being fixed, with Vegas being stuck in the middle.

What I do not like about Magix's Vegas website, is promoting both Boris OFX elements as part of their suite product and Vegas Post as if everything is working together hunky-dory. At least they should put up a warning to their Vegas Post product that it is incompatible with a list of OFX's (such as Boris continuum, some newblue etc...) at least until they fix it.

Ian_S wrote on 8/8/2020, 4:18 AM

Is this still an issue with Vegas Pro 18 or is there now some way to use other OFX plugins at the same time as Vegas Effects. Also, is the problem to do with trying to USE the two in the same project or is it that you can't have them both INSTALLED? Thanks.

Peter_P wrote on 8/8/2020, 5:08 AM

I have a problem starting Vegas Effect2 (Vp18) when my AMD RX570 card is enabled. I have no Boris OFX installed.

When I disable the AMD RX570 card with the device manager, Effects and Image can be started.

set wrote on 8/8/2020, 6:26 AM

Is this still an issue with Vegas Pro 18 or is there now some way to use other OFX plugins at the same time as Vegas Effects. Also, is the problem to do with trying to USE the two in the same project or is it that you can't have them both INSTALLED? Thanks.

Still similar.

Richard-Libutti wrote on 9/25/2020, 10:26 PM

I'm having the same issue with VP18. Everything worked great in free trial, but now after I bought it, Effects won't load. Everything else works, but Effects won't open. I made no changes to my system between using the free trial and paid version.

set wrote on 9/26/2020, 6:38 AM

Seems in free trial mode, the OFX is limited to their internal only. - but after bought, it can detect 3rd party OFX, including the possible incompatible, do above suggestion that has been tagged as solution.

NicRAM wrote on 11/2/2020, 12:29 PM

It cannot be so difficult to solve for someone who writes such software - I have Vegas Post 18 Suite - for a moment it worked with BCC 2020.05 (Vegas Effects started), unfortunately I installed BCC 2021 and it stopped working. Actually the problem is BCC13_OFX.ofx.bundle located in C: \ Program Files \ Common Files \ OFX \ Plugins, as it moves to C: \ Program Files \ VEGAS \ VEGAS Pro 18.0 \ OFX Video Plug-Ins to BCC in Vegas Pro 18 works and Vegas Effects starts (unfortunately they don't work together). However, doing so excludes BCC from other applications such as Resolve. This is unacceptable in commercial software.