[WTF went wrong_Andre Cremers] What happened?

It’s traditional to use github to report bugs in VCV. And avoid acronyms for “obscene” words?

What happened? Maybe some Photoshop action. This is obviously not a screenshot from the official build of VCV Rack.

I suspect the “merge” module went rogue and infected the whole system :wink: @stoermelder : Gut erkannt

From my perspective, the questions are: What happened before? Did you zoom in/out? What’s your OS? Do you use a dedicated GPU? And at last: Please tell us more about the vertical ‘rack’ on the right side of the screen.

What is the added value of this post/thread?

Oh people, i never thought this would be taken so seriously… The original title of this post was: “(censored acronym) went wrong ???” I must inform you that there is nothing wrong with my computer, or VCV for that matter. There are no alternative menu’s or vertical rackrails. There’s no modules name…

If you have a feature request for VCV Rack, see Bugs and Features — VCV Rack documentation to properly post your idea. Clickbait threads are not welcome here and will be removed/locked. (There’s enough of that stuff on the internet already.)

VCV Community

Graphical Issues with VCV

VCV Rack

stoermelder (Ben) February 21, 2021, 10:56am 7

Artefacts in FramebufferWidget Development

This issue is not @stoermelder’s issue in the OP. I’ve posted a comment in that issue to clarify. This will not be necessary as this has been fixed in Rack v2.

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled