when the view is zoomed out below 85%, some modules show strange orange artifacts in their interfaces. This is visible in the logo of the modules by Flag, and around the knobs on Hora’s “Detour” module, as seen in the linked video.
Does anyone know if this is a VCV bug, or a bug specifically with these modules, and if it is a VCV bug where do we report such things/check to see if it has been reported?
It’s not just the Flag logo. It happened in various spots around the controls on many of Hora’s modules, too.
I have actually nailed it down to the VCV VCA causing the problem. See this video :
Watch the video in 1080p. you can clearly see the artifacts appearing and disappearing when the meter on the VCV VCA is at 0%. I have used this VCA in many many patches, and this never happened before the update.
Bug has been reported to VCV devs via the email link on the support page.
from my tests, seems specifically connected to VCV’s VCA. None of the areas that were showing the glitch are lit, and the VCA’s display doesn’t have bloom. I tested it further, and it happens no matter what the bloom levels are set to. I just hope they manage to come up with a fix for the issue some time soon, as I don’t really want to have to roll back to Rack 2.1 and re-install all my plugins. Thankfully, though, I do still have the Rack 2.1 installer kicking around.
Yes, this looks like the code that renders the VCA’s level bars is changing the graphics context to paint yellow, but in the special case where the level is zero, it isn’t restoring the prior context when it’s finished.
From that code it looks like if all the gains are zero it begins a path, adds nothing, then sets the fill to yellow and fills
Wonder if the problem would be fixed by only filling if you add a rect at all, kinda like the code above it does? Haven’t tried and it may be the wrong spot in the code, but your comment did make me look!
I’m always doing that in this forum. I mean to go all the way up to the top and reply to the original post. But I usually pick the closest “reply” button. Would be better ux if the link said “reply to joe cool” so it was more obvious.
Without endorsing it as correct or incorrect in this case: The GitHub comment was not that he would not fix the bug for a legal reason. It was that he couldn’t review or accept third part code submissions. There are definitely situations where engineers should not consume information from external sources, including carefully protected IP, patent law, and more.