All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103300] Tear rendering bug in Bioshock Infinite
Date: Wed, 12 Sep 2018 05:04:16 +0000	[thread overview]
Message-ID: <bug-103300-502-HyqHwKLw0m@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103300-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 789 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=103300

--- Comment #5 from Timothy Arceri <t_arceri@yahoo.com.au> ---
(In reply to Ian Bruene from comment #4)
> I tried today and was unable to get a trace I'm afraid.

Looks like the game is 32-bit so a 32bit build of apitrace is needed. 64bit
distros usually only ship a 64-bit version of apitrace. For 32-bit you need to
build from source [1].

If you manage to build it the you can just try loading steam like so:

LD_PRELOAD=/ ...path to apitrace git repo... /build32/wrappers/glxtrace.so
steam

Then just launch the game and you should end up with a trace.

[1]
https://github.com/apitrace/apitrace/blob/master/docs/INSTALL.markdown#linux

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1738 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-09-12  5:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 19:21 [Bug 103300] Tear rendering bug in Bioshock Infinite bugzilla-daemon
2017-10-16 19:22 ` bugzilla-daemon
2018-09-10  3:19 ` bugzilla-daemon
2018-09-10 12:45 ` bugzilla-daemon
2018-09-11  4:37 ` bugzilla-daemon
2018-09-12  5:04 ` bugzilla-daemon [this message]
2019-02-12 12:12 ` bugzilla-daemon
2019-02-17 20:58 ` bugzilla-daemon
2019-02-18  0:11 ` bugzilla-daemon
2019-09-25 18:00 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-103300-502-HyqHwKLw0m@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.