https://bugs.freedesktop.org/show_bug.cgi?id=80419 --- Comment #94 from Roland Scheidegger --- Created attachment 120734 --> https://bugs.freedesktop.org/attachment.cgi?id=120734&action=edit apitrace patch for honoring range in DrawRangeElementsX commands So you'd want something like this (totally untested) patch for apitrace? Makes sense I guess that the specified range not only means the supplied indices have to be inside that range, but it also works the other way round (driver can rely on the specified range being accessible) - otherwise the driver would still need to scan the actual index buffer. (Albeit since for this app the ranges seem to be pretty bogus who knows if the memory inside the specified range but not used in the actual indices is really always accessible.) I am actually wondering if it would be legal if the memory isn't accessible below the start value (apitrace surely couldn't handle that)... -- You are receiving this mail because: You are the assignee for the bug.