@jon_valdes This is so frustrating! We had something similar like this recently at work as well which led me to implement a renderdoc style texture debugger (in my hobby project at least for now). Because obviously the issue *never* reproduced in renderdoc 🙃