loftar wrote:For anyone curious, the concrete recent change that suddenly made the render bug so reproducible was adding outlines to avatars. This specifically, when the combat relation list expanded to need scrolling (so that at least one avatar view didn't actually render to the screen) made the VAO tracking mismatch cause an indexed drawcall to ba called without an index buffer set, which caused the crash. This usually wouldn't happen since there are usually many drawcalls in between that accidentally resynchronized the VAO tracking.
When we tried to debug the previous so-called "nVidia bug" (so called since I only got it reported from nVidia owners, making me think it was a driver bug), the combat-relation list didn't switch to scrolling mode at all, and avatars didn't have outlines, so my suspicion is that it only happened in fights that were large enough that the list overflowed the bottom of the screen, and where at least two consecutive characters in the list had hats with "lens flare" effects on them (which also render index-lessly), explaining why it was almost impossible to find how to reproduce the problem.
I see. But that's not certain. I think many people guessed it was related to portraits. The question was more likely, "Why did this bug appear?" – it felt like it appeared quite recently after an update, but there didn't seem to be any updates related to it.
The main thing is that it was fixed. I hope no one died from this bug.
