yeah, that is odd. But when I upgraded to current Windows 10, Vegas did not give me an option to use the GPU at all. It did not recognize my video card, although both monitors worked. I reinstalled the drivers and everybody was happy.

Well i do see the GPU option in the prefs->video dialog. I can see the GTX listed in there so Vegas knows the card is installed. That implies the drivers are working in v14 otherwise it would not be listed. But yes, i will try a reinstall anyway.

This issue really seems to be in detecting the secondary display information. v14 just doesn't see any for whatever reason. Hence the missing fields in the dialog box. No idea why at this time.

Some interesting finding here. As a backup purpose, I make regularly a bootable image of my Operating System on a separate SSD on the same PC. And on this recent backup/image, I did updated my Vegas-Pro #454 to the Magix version Vegas-Pro13 #545 just to see what will happened with script. But I did not play with it more than that. So, I did have a look again, and I just discovered that Vegas-Pro13 #545 had the exact same "external display" problem than Vegas 14 !

So, obviously, this problem come from the earlier version Vegas-Pro13 #545. I don't mean that you had to installed Vegas-Pro13 #545 to get the problem, I mean the bug is already present in the "coding" of Vegas-Pro13 #545. Hope this will help Magix to find more quickly a solution...

hello Magix, do i need to post a ticket?

I don't work for MAGIX of course, but having read this thread, I would say definitely YES. So far it's looking like you're more likely to reach the right people by submitting a support ticket than here on the forum, same as in the SCS days. https://support2.magix.com/customer/en/vegas/form

Nice find jwe, and thanks for doing that test with v13 #545

Yes Nick, i'm going to submit a ticket today. Looking like a bug.

So i just typed a whole description in the ticket form and got back "Unfortunately there was an error during sending your request, please try again later".. :(

Today, on the same desktop system, I installed the Vegas for a "clean" Windows 7 and ... voila: output to the second monitor is working. Probably, bug appears in combination with other versions of the installed system components: .NET frameworks xx, Visual C++ ... Redistributable xx and etc.

.NET version had crossed my mind vitus. Quite honestly its going to be tricky to nail this down to a framework conflict and not being able to submit a service ticket doesn't help either.. I am now out of time and have ditched testing v14 for now. Maybe MAGIX can respond please. This needs sorting out.

Error found in Submitting a ticket: Product Version does not test for invalid characters. I had typed "trial 14" which trashed my description text (time wasted), where just "14" worked. No warning given.

Always worth copying text to the clipboard or even Notepad before submitting anything that you've worked hard on to anywhere. It's a paranoid habit of mine.

In that version field I think I put the following and it worked ok:

14.0 (Build 161)

Yes I do the same usually.

.NET 4.6.2 also fixed it for another user: https://www.vegascreativesoftware.info/us/forum/fullscreen-display--103699/

Edit: and another https://www.vegascreativesoftware.info/us/forum/nvidia-k2000m-vegas-13-14--104146/

Working!

Thanks jwe, that did the trick, and thanks Nick and everyone for your help too.

.NET version checker available here:

http://www.asoft.be/prod_netver.html

and .NET update here:

https://www.microsoft.com/en-GB/download/confirmation.aspx?id=53344

My installed version was 4.5, I updated to 4.6.2 and job done. Vegas should be detecting this as a minimum requirement and installing the latest version as needed. Seems not.

Paul, could you please reply to your support request acknowledgement email under the same email title telling them the solution and that you suggest Vegas should detect for and install 4.6.2. There's no proper support ticket system at the moment where you can update info, but by doing that it should reach the right people more effectively than here and there's a chance to get it fixed quickly.

.... at least i think that should work, although I suppose it might not until someone from support has actually replied to you in person, as opposed to you just getting the acknowledgment.

Already done Nick! Details sent.

Thanks Paul.

But... arrrggghhhhh... I just remembered that .NET 4.6.2 might be responsible for breaking Media Manager.

Ha.. Never mind. Who could have guessed these issues could be releated. Vegas is dependant on the .NET framework and has been for years. I guess we'll just have to keep an eye out for this in the future.

Wish I'd never asked you to update that ticket lol. I want a bugfix release of VP14 that doesn't go looking for .NET 4.6.2, cuz if it breaks MM then it'll be a showstopper for me. Doh

What a mess.. So does your MM break just by installing 4.6.2? I thought .NET versions can coexist without any problems.

Hi Nick, I don't use MM but I just installed it and it seems to work very well here with .NET 4.6.2.