Update, even with software encoding the glitching is still present @jdobbs. So it looks like it didn't work (at least not for me), think it can be safely removed again in the next build. Considering i was the only one even persisting in finding a possible cause for this
and a possible solution. Thanks for trying anyway!