It seems that you don't have much support.

@lan-mLMC I even can't understand why these significant information didn't cause everyone's attention.

These significant information are why Vegas Pro fell behind Avid, Promiere, Resolve, FCP, Edius.

Can't understand why they don't fix these...

I didn't realize the way OFX is implemented is why FilmConvert doesn't work, for example. That's unfortunate if we don't have full functionality of OFX.

@rock-c I don't know what Vegas team's plans are, but I sure hope they look at these posts.

As for attention, for this type of threads, most of the time there will be someone here to tell you there is nothing wrong with how Vegas works and we do not need anything to change. :) I think people are so founded to their favorite NLE that they take very personally everything that is being said and they believe most of the suggestions are a direct attack to Vegas.

Anyway, I believe the team is wiser than that and we will see some nice improvements, hopefully in this area too, with Vegas 18. Looking forward to it!

@rock-c

+1

In a thread from 2016 I asked in the Boris FX forum (Creative Cow):

Why BCC 10 control points are simpler in Vegas Pro and more elaborated in Avid Media Composer?
https://forums.creativecow.net/thread/15/864814#864814

But the answer you got was that it was an OFX limitation and Boris needed to upgrade its OFX plugins. It's not clear that Vegas is at fault.

@RogerS @rock-c

Regarding the mentioned thread from 2016 I had asked in Boris FX forum "Why BCC 10 control points are simpler in Vegas Pro and more elaborated in Avid Media Composer?", I investigated further with Boris and just received this reply through email (case number 00167448):

I looked into the situation and discovered that, unfortunately, this is still a shortcoming within the Vegas host, even the latest version. This is actually not a shortcoming of OFX itself, as similar things are functional in Resolve and Nuke (the first of these being a free OFX host). Vegas can draw the simple point picker cross-hairs themselves, but it's unable to draw a visual control interface (let alone make it functional in these ways).
Thank you, and sorry.

Jon

Technical Support Team
Boris FX / Imagineer Systems
http://www.borisfx.com/
65 Franklin Street, Suite 400 Boston MA 02210
P: 888-77-BORIS (888-772-6747)
F: 508-357-8906

So, now it's clear that Vegas is at fault, at least regarding the lack of proper control points on the screen.

@cadudesun  ... Thank you for posting the BorisFX reply. My gut feeling was that it was going to be a Vegas Pro limitation because over the years I've never seen any plugin - Vegas Pro native or 3rd party - provide anything more than control points in the preview screen.

@RogerS @rock-c

Regarding the mentioned thread from 2016 I had asked in Boris FX forum "Why BCC 10 control points are simpler in Vegas Pro and more elaborated in Avid Media Composer?", I investigated further with Boris and just received this reply through email (case number 00167448):

I looked into the situation and discovered that, unfortunately, this is still a shortcoming within the Vegas host, even the latest version. This is actually not a shortcoming of OFX itself, as similar things are functional in Resolve and Nuke (the first of these being a free OFX host). Vegas can draw the simple point picker cross-hairs themselves, but it's unable to draw a visual control interface (let alone make it functional in these ways).
Thank you, and sorry.

Jon

Technical Support Team
Boris FX / Imagineer Systems
http://www.borisfx.com/
65 Franklin Street, Suite 400 Boston MA 02210
P: 888-77-BORIS (888-772-6747)
F: 508-357-8906

So, now it's clear that Vegas is at fault, at least regarding the lack of proper control points on the screen.

@cadudesun Maybe Ignite Pro puppet tool's error is also because of this.

Maybe Ignite Pro puppet tool's error is also because of this.

A very good point. Puppet was removed from Ignite Pro on its first update after its initial release as far as I can recall. But Puppet only relied on control points (nodes) and didn't involve drawing in VP's preview window or the like. I am only guessing, but maybe the problem was that the nodes were not able to be keyframed in VP's preview window. Of course, it could be because of any other number of problems.

I think people are so founded to their favorite NLE that they take very personally everything that is being said and they believe most of the suggestions are a direct attack to Vegas.

If this were true, every VEGAS 18 feature request thread posted on these forums would devolve into an argument, and they do not. There's a difference between requesting features and incessantly repeating the same request over and over in several different posts and threads, which some around here tend to do.

There are some valid (and new) feature requests presented here, this is how it should be done... and it's quite detailed in what is being asked.

Just to throw in my .02 cents worth. It would be great if Vegas could tap into the full OFX feature set of products such as Boris. I've spent too many years fiddling with crosshairs that are more guesswork than intuitive. The century is already 20% shot and I'm not getting younger.

It would be great if Vegas could tap into the full OFX feature set of products such as Boris.

@monoparadox It should! Even free Resolve has full OFX feature, but paid Vegas Pro not. It is a little ridiculous...

Just because they haven't been able to get to this particular request yet does not mean they do not plan to. Also keep in mind we're in the middle of a pandemic, and many coders are being forced to work from home, making collaboration more difficult and slowing projects down.

They're up against a lot, but they do hear your cries.