Sorry, but I can't do anything about it. You can just try to update VEGAS Pro to a possible latest version and see if this issue has been fixed. As I've said before Voukoder Pro is just a pure file output exporter plugin to VEGAS and should not interfere with any UI functionality.
I'll write a further email directly to their CTO now. If I still don't get a reply anymore I have to accept the consequences.
Edit: Perhaps it has something to do with Magix's insolvency in 2024.
I' ve tried to completely uninstall Vegas an Voukoder. I' ve manually deleted all remaining files I could find.
After that I' ve reinstalled the latest version of Vegas.
There were no issues.
Then I installed the latest Voukoder version. => the UI issues appeared
After that I deinstalled Voukouder => the issues were instantly gone!
No other plug-ins are installed.
should not interfere with any UI functionality
But it definitely does.
Voukoder not installed: clean UI
Voukoder installed: UI is corrupted
Perhaps it has something to do with Magix's insolvency in 2024.
Sorry, that is blatant nonsense!
What effect should the insolvency two years ago have to UI issues, when a plug-in is installed?
Unfortunately, I also have to say that these issues with Voukoder occur in the new Vegas 2026 from Boris FX. The Master Bus control next to the preview window also seems to stop working quite often. - Is there no update or solution available?
BorisFX Vegas 2026.0 (Build 66)
Voukoder Pro 3.1.3
Country: Italy.
Any news please? 
Thanks!
No, unfortunately no news or updates. I investigated this again. As far as I know this should have displayed the FPS of the project. I checked the code again, even did an analysis with the "Claude" (Amazon Q and GitHub Copilot) AI. No success.
I also wasn't able to get in contact with anybody of BorisFX for around 6 months. I don't have a good feeling about these bugs getting fixed or about future VEGAS Pro support in general, but - we will see.
In the Magix time I was in contact with the developers, with the project lead and even with their CTO.
Hello Vouk, I work for this project. We had a similar issue with other plugins. The problem occurs, when any external plugin changes the applications global language settings. Because we enumerate the the plugins at startup, the expected default language is then broken. This has been worked around for the upcoming Vegas releases, but not for the older ones.
To fix this, make sure not to change the application wide locale setting (setlocale() or similar). For further support, feel free to drop me a private message/email.
Thanks for your feedback. I have sent you an email.
Hi Vouk, any news after our new friend VegasSteve replied?
Thanks!
Does this build help?
VegasSteve I found out Boost changes it in its logging library.
😃
It works!
👍️
