I see :)

it is all very confusing 😳

This shows the About dialog:
http://peter-ftp.co.uk/screenshots/2016-10-24_213800.jpg

The OS is win7-64, retail pack, not bootleg. I custom built this computer for video work. I am not aware of any unusual OS colour settings, nor any unusual Pro 13 colour settings.

Here are some Pro 13 configs:
http://peter-ftp.co.uk/screenshots/2016-10-24_214032.jpg
http://peter-ftp.co.uk/screenshots/2016-10-24_214136.jpg

and this is MSP12

http://peter-ftp.co.uk/screenshots/2016-10-24_214336.jpg

I've started 2 Tests with my Notebook:
i7-4720 HQ 2,60GHz, 8GB, 128GB SSD, 1TB HDD, GTX960M 2GB

Source was your Vimeo file 7 min 32s, mp4 AVC Bitrate 12,1 Mb/s max 40Mb/s
with your settings incl Textfiles and FX chain
Approximate Time total at 50% rendering
NBFX GPU  ON   01:10
NBFX GPU OFF  01:19
not really a great difference

OK, interesting. I never saw any real time difference in any version of Vegas no matter what I did, so I think that by the time you have a fast CPU (mine is a 6-core) it doesn't make such a difference unless the GPU is something pretty special. Especially as lens correction is a floating point FX and the GPU is presumably not going to help there.

But something has changed... I have gone from the usual 10x real time to 18x real time. I will remove the lens correction and re-test now.

Update: I may have done a 2-pass render rather than 1-pass... With 1-pass I get:

1:13 with lens correction
1:08 without lens correction

So while I cannot tell whether NBFX is using the GPU, the lens correction makes no difference to the render speed.

nearly the same as mine (2-pass)
your Camcorder can record

• MP4 (MPEG-4 AVC/H.264)
• XAVC S (MPEG-4 AVC/H.264)

Have you ever tried the XAVC or XDCAM-EX Template
rendertime:
XDCAM-EX 35 = 00:09:46
XAVC S            = 00:20:59

A bit of a long story but I don't want to shoot in what they call X-AVC-S because

- it eats the SD card 2x faster (50mbits/sec) which limits it to 5hrs which is an issue sometimes whereas 10hrs is never an issue, in my application (flying movies, externally mounted camera)

- the camera writes one big file, which cannot be transferred over wifi (because Sony crippled the wifi to work with only ios and android apps, and there is no device with enough free space to transfer the stuff to)

- in AVC (the 25mbits/sec mode) the camera writes 4GB chunks which can be transferred over wifi (to a rooted android device running a hack to redirect the chunks to an external 128GB SD card) which saves me having to open the waterproof housing

Regarding rendering, which you may have been referring to, there is no XDCAM 50fps template so I made one

http://peter-ftp.co.uk/screenshots/2016-10-25_091124.jpg

The render time is now 25 mins! Where is the catch?

BTW in XDCAM
https://en.wikipedia.org/wiki/XDCAM#XDCAM_formats
there is no 1920x1080 *50* FPS.

Regarding rendering, which you may have been referring to, there is no XDCAM 50fps template so I made one

there is a ready 1280x720 50p template😉
It is only for different testing and you must not wait 2 hours to see the result
 

The video file is 1.53GB, compared with 677MB for the one that took more than 2x longer... interesting! I will upload it now.

File stats
http://peter-ftp.co.uk/screenshots/2016-10-25_172734.jpg

Codec
http://peter-ftp.co.uk/screenshots/2016-10-25_172820.jpg

I forgot to change the size from 1280x720 so the bitrate is clearly a lot higher.

BUT - spot the discrepancy
http://peter-ftp.co.uk/screenshots/2016-10-25_173634.jpg

Vegas has failed to update the description. However, it turns out that you can't set 1920x1080Px50FPS anyway; it prevents that. If you set 1920x1080 and then set 50fps, it drops the frame size...

Regarding NewBlueVideoEssentials6VegasPro13ForWindowsSetup30.exe should you get a serial number from NB? When I install it it says one will be emailed but it never arrives - as mentioned previously.

In general I try to avoid trial versions of anything because they have to leave rubbish in some hidden place on the computer, to prevent a simple re-installation giving you another 30 days. And this rubbish can bite you in the future when you install a real version.

What does this do? Sorry for repetition but it was not obvious to me that this .exe is "Video Essentials VI" but I guess 6=VI :)

It is Video Essentials 6 bundled with Vegas Pro 13. It will automatically activate (you don't need a serial number) but it isn't recognizing Vegas Pro 14 at this time because of the name change.

It also appears to me that there is some confusion over the legacy products vs the current products. The About screen will look different for the current products than the did with the legacy products. And, yes, ve4 will work. You did not have ve4 installed in the shown image but is is a legacy product. I would definitely recommend the current product line over the legacy products as the legacy products are no longer being updated.

I'm still waiting for the updated installers. I will certainly let you know when they are available. I thought they would be available by now but, apparently, there were more under the hood changes that needed to be accounted for.

It is Video Essentials 6 bundled with Vegas Pro 13. It will automatically activate (you don't need a serial number) but it isn't recognizing Vegas Pro 14 at this time because of the name change.

Again: Video Essentials 6 bundled with Vegas Pro 13 works fine in VP14, without a watermark.

I suspect NB sell the lens correction plug-in within a variety of product bundles, and it behaves differently according to how you bought it.

Maybe the version which comes in the $99 bundle simply does not work properly.

I have sent them this latest info of course but have had no response.

I got a reply from NB, asking to delete the Common directory under Program Files\NB and reinstall. It doesn't help. Those checkboxes still can't be checked...

i guess, that possibly only a complete new installation of vegas and all your plugins could  solve your problem.
i would do this step by step, to look when the problem appears

don't forget to clean your registry after deinstallation

Life is too short... I can run lens correction in MSP12, which is 100% solid.

It cannot be hard to look at the NBFX code and see what could possibly prevent a checkbox not showing the tick! The problem is the usual one: the "support" people are sending back boilerplate replies from a script sheet, without the programmer having looked at it.

I have no problems with the checkboxes, although i have all of your software installed for testing
I don't think it's a newblue problem, it's more a problem of your configuration/Installation.