Thanks, but that is not the correct way to solve the problem.
VP 15 Edit starts correctly, so I expect that VP 16 Edit does the same: if it does not, it means they got something broken and they need to fix it
If they do not,.I keep my money and will spend elsewhere.
I already contacted Magix for this issue... let's see what do they answer.

Cheers

Roberto

If it works, it is the correct way to solve the problem. VP15 Edit didn't come bundled with that THIRD PARTY plugin that came free with VP16. Something about it isn't working well with your system config (but worked fine for me and many others). A simple 5 step process is all that is needed to correct the issue on your system. If you have issues with the Boris FX installation, you should be contacting them about it, not Magix. The folks at Magix decided to help you anyway, by giving you a workaround that will get your installation up and running correctly, even though it wasn't their software causing the issue. Given that, I'd respond to them with thanks, rather than threats of taking your money elsewhere after refusing to even try their simple fix.

1. "VP15 Edit didn't come bundled with that THIRD PARTY plugin that came free with VP16" => that's absolutely not correct: VP 15 Edit was bundled with BCC Object plug-ins.
2. Calling "threat" a decision to not spend money on something not working is a bit out of context, isn't it ?
3. SW shall preserve the compatibility with previous versions, especially if we are talking of just the last version, not a very old one. This shall be valid even more if the SW is sold with 3rd party plug-ins, because they can create issues, so regression tests are mandatory.
That's not my rule: it's a general customer-oriented rule. Would you like to buy a new television and discover that it does not work anymore with your surround system or BR player for some unknown reason ?
4. The work-around targets VP 14 (so, if it has been existing since 2 versions how come it has not been fixed yet???) and HitFilm Pro, which I do not have.

Anyway, thanks for the help, but without a clean fix I will rather keep my money in my pocket ( a decision, not a threat, got the difference ? ;-)

Cheers

Roberto
 

1. I stand corrected, but it doesn't change the fact that it is a third party plugin, your inquiry should have gone to Boris, and the vast majority of Vegas 16 users have had no issues installing that same plugin (otherwise this forum would be overflowing with posts about it, and the Magix dev that attempted to help you wouldn't have had to dig back to a Vegas 14 post to find someone with a similar issue).

2. You didn't tell them you were going to spend your money elsewhere as a congratulations. You threatened a negative reaction (not giving them money) if they didn't provide a "better" fix than their simple 5 step solution to make your rare case work properly. But I digress...

3. No software installs without issue on every single system it is attempted to be installed on in the wild, not on an open platform like windows that allows full customization of the hardware inside, where all software must be compatible with hundreds if not thousands of potential hardware configurations. You have a very rare case, it is involving a third party plugin, and you're demanding that Magix develop a more elegant fix than a simple 5 step process for a problem that likely isn't even being caused by their software. I can't help but find that to be a bit extreme of a reaction to be having to them trying to help you.

4. The workaround is a way to flush out installed plugins and re-install them, in the case that something going wrong with the installation of one of the plugins prevents Vegas from launching. It doesn't mean there was ever a problem with Vegas, only that when a third party installer malfunctions, this is a way of fixing it so it can install correctly.

Ok, Frosty,

i will try the work-around.
But still, having about 25 years of SW programming experience, I can tell you that it is not correct that a SW crashes (yes, with an error message, but after the message box is displayed it crashes) if a 3rd party plug-in is not recognized or has something that the SW does not recognize.
The right way to do that would simply to advise with an error message that something went wrong and that the specific plug-in won´t be usable and so not listed or gray-listed once the SW starts. That is what i would do (and what I did for some SW that I developed).
Magix tech support ahs anyway contacted me and this evening i will send a screenshot of the problem (as per their request), so hopefully they will investigate on it: apart from work-arounds, that´s the right approach, because a case like this, even though could be "rare", it can be due to some "bad" coding that can generate other types of unwanted troubles.

Cheers

  Roberto

Hi Frosty,

your work-around worked,
I uninstalled BCC 3D Objects and installed it again and now VP 16 starts correctly.
Also it can recognize and effectively apply those effects (which were offered in Bundle with VP 15).
So, I need to send a big THANK YOU to you!

Regards

Roberto