From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 80419] XCOM: Enemy Unknown Causes lockup Date: Fri, 05 Feb 2016 14:21:37 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0913220159==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 41E0E8A2BB for ; Fri, 5 Feb 2016 06:21:37 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0913220159== Content-Type: multipart/alternative; boundary="14546820972.0b9d1417a.10396"; charset="UTF-8" --14546820972.0b9d1417a.10396 Date: Fri, 5 Feb 2016 14:21:37 +0000 MIME-Version: 1.0 Content-Type: text/plain https://bugs.freedesktop.org/show_bug.cgi?id=80419 --- Comment #112 from Kamil Páral --- (In reply to Nicolai Hähnle from comment #111) > However, if I recall correctly, XCOM issues DrawRangeElements calls with > ranges that are larger than necessary. My understanding was that exactly the opposite was the issue - the game sends indices outside of the specified bounds. Quoting Jose [1]: "the application is giving a hint to the OpenGL driver that indices are between 0 and 215, but in fact in call 21933, the index at position 164 is 216, and more later." [1] https://github.com/apitrace/apitrace/issues/407#issuecomment-166619366 -- You are receiving this mail because: You are the assignee for the bug. --14546820972.0b9d1417a.10396 Date: Fri, 5 Feb 2016 14:21:37 +0000 MIME-Version: 1.0 Content-Type: text/html

Comment # 112 on bug 80419 from 
(In reply to Nicolai Hähnle from comment #111)
> However, if I recall correctly, XCOM issues DrawRangeElements calls with
> ranges that are larger than necessary.

My understanding was that exactly the opposite was the issue - the game sends
indices outside of the specified bounds. Quoting Jose [1]:
"the application is giving a hint to the OpenGL driver that indices are between
0 and 215, but in fact in call 21933, the index at position 164 is 216, and
more later."
[1] https://github.com/apitrace/apitrace/issues/407#issuecomment-166619366

You are receiving this mail because:
  • You are the assignee for the bug.
--14546820972.0b9d1417a.10396-- --===============0913220159== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0913220159==--