Those were the images mentioned above.

The GUI / canvas / redraw of the plugins is kinda buggy indeed.

I mentioned other bugs with VST (since Vegas 20 / build 4.x.x), but only got 6 (!) "customer satisfaction surveys" per ticket (and no solutions or answers at all).

Many or my (third-party) 32bit VST-2 plug-ins will not load or are not available in VP21. They worked fine in VP-16 though.

Sorry to say, most of Magix'a audio utilities are less functional than before. In Sound Forge 16/17, third-party 32bit VST-2 plug-ins cannot be adjusted at all due to a display issue that hides most or the plug's UI.

Many or my (third-party) 32bit VST-2 plug-ins will not load or are not available in VP21. They worked fine in VP-16 though.

Interesting, may I ask which plugins are not loading / visible in VP21 / build 108?

I mean, I don't need all names 😉 but was just wondering which ones.

For me Loudmax (64 bit / VST 2) is working, but the parent window doesn't adjust to it's size.

Fortunately you can double click in the right bottom corner and reload, than it still fits in.

I want to migrate to VST 3, but I've been working on a single project for about six years now and that one uses VST 2 only.

When I update VST 2 to VST 3 all settings and parameters in the Vegas file are reset to default, so I have to stick with VST 2 for some years (64 bit, phew!).

- update -

Wanted to try out a VST 2 plugin that worked for years, got a instant freeze in Vegas 21 / build 108 (RX 9 / Spectral De-noise plugin).

VEGAS 21 / build 108

VEGAS 20 / build 370

Seems not much is fixed, same plugin crashes in both versions at the exact same file.

It's hard to use audio in a video-editor, I guess.

My "Use High-DPI Scaling" Vegas option was turned Off with my 1080p display, and I am having none of the problems being reported in this discussion, at least with a couple of VST2 plugins I use regularly. Indeed, turning it ON caused interface cutoff of the type described here, including one of the VST2 plugins mentioned in this discussion. @approxostrich @rraud

This is my workaround.

A bit of unsupported speculation: When I started out with VST2s, they used MS Overlay Surface graphics. As we transitioned to 64 bit and high-resolution displays, that support became less reliable, and it may be that the newer versions of Vegas have given it less attention. From this article:

https://learn.microsoft.com/en-us/windows/win32/medfound/hardware-overlay-support

The overlay cannot be shrunk, mirrored, or deinterlaced.

Source color keys and alpha blending are not supported.

Overlays can be stretched if the overlay hardware supports it. Otherwise, stretching is not supported. In practice, not all graphics drivers support stretching.

Each device supports at most one overlay.

Overlay is performed using a destination color key, but the Direct3D runtime automatically selects the color and draws the destination rectangle. Direct3D automatically tracks the position of the window and updates the overlay position whenever the PresentEx is called.

My "Use High-DPI Scaling" Vegas option was turned Off with my 1080p display, and I am having none of the problems being reported in this discussion,

Like this?

I never use HDPI, and the problem still remains.

But this is from Vegas 20 / build 370, because build 4.x.x and Vegas 21 / build 108 are (audio wise) to buggy to use.

So I am stuck with 20/370 until the major bugs are fixed.

You are right- with high DPI scaling off TDR Nova, TB Barricade, etc. look fine on my 1440p and 1080p display. Maybe I'm imagining it but the whole program looks less crisp now, though.