From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 98693] Mad Max: Long lags when VRAM full Date: Thu, 17 Nov 2016 10:24:25 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0024179628==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 037296E2BB for ; Thu, 17 Nov 2016 10:24:25 +0000 (UTC) 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 --===============0024179628== Content-Type: multipart/alternative; boundary="14793782640.46F5BC26A.24876"; charset="UTF-8" --14793782640.46F5BC26A.24876 Date: Thu, 17 Nov 2016 10:24:24 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D98693 --- Comment #4 from Jani K=C3=A4rkk=C3=A4inen -= -- (In reply to Michel D=C3=A4nzer from comment #3) > Assuming your card has 1GB of VRAM, the fundamental problem is that the g= ame > wants to use more VRAM than is available. Maybe you can try reducing the > game's graphics settings such that the 'requested VRAM' number drops below > 1GB. Indeed. The game's settings are at the minimum, and the resolution is @ 720= p. I hoped the lowest setting would alleviate the lags, but unfortunately it did= n't. However, just by reading the links from the article I linked in my original message, I thought that it should be possible to play with less VRAM than w= hat is needed, as per: "The game I'm testing needs 3.4 GB of VRAM. Setups: Tonga - 2 GB: It's nearly unplayable, because freezes occur too often. Fiji - 4 GB: There is one freeze at the beginning (which is annoying too), after that it's smooth. So even 4 GB is not enough." Also the descriptions of the problem seem to match mine. A problem in memory handling? Thanks for the suggestion though, anything that could remove or at least re= duce the lags would make the game from mostly playable to very playable (for me = at least). --=20 You are receiving this mail because: You are the assignee for the bug.= --14793782640.46F5BC26A.24876 Date: Thu, 17 Nov 2016 10:24:24 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comment= # 4 on bug 98693<= /a> from Jani K=C3=A4rkk=C3=A4inen=
(In reply to Michel D=C3=A4nzer from comment #3)
> Assuming your card has 1GB of VRAM, the fundamen=
tal problem is that the game
> wants to use more VRAM than is available. Maybe you can try reducing t=
he
> game's graphics settings such that the 'requested VRAM' number drops b=
elow
> 1GB.

Indeed. The game's settings are at the minimum, and the resolution is @=
 720p. I
hoped the lowest setting would alleviate the lags, but unfortunately it did=
n't.
However, just by reading the links from the article I linked in my original
message, I thought that it should be possible to play with less VRAM than w=
hat
is needed, as per:

"The game I'm testing needs 3.4 GB of VRAM.

Setups:
Tonga - 2 GB: It's nearly unplayable, because freezes occur too often.
Fiji - 4 GB: There is one freeze at the beginning (which is annoying
too), after that it's smooth.

So even 4 GB is not enough."

Also the descriptions of the problem seem to match mine. A problem in memory
handling?

Thanks for the suggestion though, anything that could remove or at least re=
duce
the lags would make the game from mostly playable to very playable (for me =
at
least).


You are receiving this mail because:
  • You are the assignee for the bug.
= --14793782640.46F5BC26A.24876-- --===============0024179628== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0024179628==--