Have you had VP9 working okay with Windows 10 before? Or is this a new install on W10?
If the latter, perhaps consider the possibility that VP9e which was released some 5 years before the release of Windows 10 may not be perfectly attuned to W10 when VP9 was developed under previous Window builds.
I recall that there was a similar display problem with some FX in a much later version of Vegas Pro (under MAGIX) in which a couple FX did not display properly. Vaguely, I think that the solution was to wind back the display resolution in Windows 10 to a lower display rez.
This machine began its life on Windows 7 Pro. I did an in-place upgrade to Windows 10 when Microsoft ended support for Windows 7. I've found that in-place upgrades will retain features of older programs and/or allow some applications to run on Windows 10 that won't even install on a clean installation of Windows 10. Photoshop Elements 7 was on this machine and still runs after in-place upgrade to Windows 10, while it failed miserably on a clean installation of Windows 10. My HP 4570c scanner runs fine on a machine with an in-place upgrade while Windows 10 and HP offered no support and it didn't work on a clean Windows 10 installation.
Both machines use the same monitors; Sony Brivia 2k 42", I/O 32" desktop monitor (x2)
Maybe it's the theme or something like that? I switched the Vegas vanilla profile on/off, I've tried various screen resolutions/re-booting each time, I tried with each monitor individually - nothing changes heh : )
It's reassuring to see it working though, thanks John! I'll see if I can figure this out...
My copy of Vegas and these exact same Vanilla plugins worked on this machine around a month ago (last render: 09/18/20)
One thing I noticed (after a fresh install of Vegas - Kin-A!), on opening the plugin window the default size is too small, or appears 'shrunken' !?!?!
The 'newer' plugins (just to rub my face in it lol) display fine
I'm wondering whether this is in fact down to one of those windows updates? I mean, the operating system is the only thing on this machine that has changed in at least twelve months
... the solution at the time being related to fonts - the last comment providing instructions about what to do, and this involved a minor coding change in the fonts folder in the registry. As with anything to do with the registry, its always a good idea to save the particular registry folder/item before changing it - just in case.
BTW, the registry string is still the same in W10 and is:
@Dexcon yes, that font issue has come up regularly, sometimes with a bit different solutions working, other times none of them. Several threads over the years, search e.g. “sserife.fon” or “sserifer.fon” on the forum.
Double clicked program short cut icon while holding down ctl+shift ticked check box 'Delete all cached application data'
Closed Vegas
Opened regedit and changed font
Rebooted the machine
I've been a Vegas user since Sonic Foundry created the software. This is the very first issue I've ever had with Vegas, Acid or Soundforge (I own all three)
Thanks for all the replys though, very much appreciated