2017-01-18, 01:32 AM
After some testing, it appears these errors occur only when the interface is set to auto resolution and renders in 4k, not in 1080p.....and they happen when a screen with a new custom backdrop is called upon. Will stick with 1080 I guess