All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Jelten <jelten@in.tum.de>
To: intel-gfx@lists.freedesktop.org
Subject: [BUG] Minecraft graphics issues
Date: Wed, 07 Dec 2011 19:15:25 +0100	[thread overview]
Message-ID: <4EDFAD3D.90106@in.tum.de> (raw)
In-Reply-To: <CAC7LmntVUpk3qc1p3T7=z49mcd=-0qrjx2wcXU_Wfs=OW9sw3Q@mail.gmail.com>


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

Hi!

What about adding Minecraft to the officially tested games list for the
released graphics package?
It's one of the most played games on Linux i think, and a lot of users
are experiencing graphical problems that don't occur in windows or mac.

Two screenshots of my Minecraft graphics issue:
http://img7.imagebanana.com/img/5900nd4k/20111206_08.34.06.png
http://img6.imagebanana.com/img/2pl3w1ky/20111206_08.39.38.png

The color of the error equals the skybox color.
After taking the screenshot, the errors are gone for ~10 seconds and FPS
increase noticeably. Then it comes back and looks awful again.
The error occures in fullscreen and windowed mode.

Maybe this is the relevant bug in launchpad:
https://bugs.launchpad.net/mesa/+bug/829086

Another thing is that my Minecraft on view distance short has about
20-30 fps, a friend's Macbook Pro (core i5-2420M) renders Minecraft at
40-50 fps with view distance far. (We have both the exactly same
graphics chip (HD3000) and my CPU is even better)

My system:
core i5-2520M with HD3000 IGP
8GB RAM (how much graphics memory is shared then?)
1366x786 LVDS IPS display


Software:
linux 3.1.4-1
mesa 7.11.2-1
xf86-video-intel 2.17.0-2
libdrm 2.4.27-1
libva 1.0.15-1
libva-driver-intel 1.0.15-1
Minecraft 1.0.0


Jonas Jelten

On 12/06/2011 02:03 AM, Eugeni Dodonov wrote:
> Hi,
>  
> We'd like to announce Intel 2011Q4 graphics package, focused on
> performance and stability improvements in the Intel Linux Graphics stack.
>  
> Please check http://intellinuxgraphics.org/2011Q4.html for the
> recommended stack, list of new features and known issues.
>
> I'd also like to thank all the developers, community, our users and
> testers for helping us to improve the drivers. Thanks a lot for all
> your work, help and support!
>
> And as usual, if you find any new issues, please let as know by filing
> bugs following the
> http://intellinuxgraphics.org/how_to_report_bug.html guidelines.
>
> Thanks,
> Eugeni Dodonov
> Intel Open Source Technology Center
>
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx



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

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

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2011-12-07 18:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06  1:03 Intel 2011Q4 graphics package Eugeni Dodonov
2011-12-06  3:29 ` Alan W. Irwin
2011-12-06  7:55   ` Jin, Gordon
2011-12-06 11:14   ` Eugeni Dodonov
2011-12-06 19:58     ` Alan W. Irwin
2011-12-07 18:15 ` Jonas Jelten [this message]
2011-12-07 20:57   ` [BUG] Minecraft graphics issues Eugeni Dodonov

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=4EDFAD3D.90106@in.tum.de \
    --to=jelten@in.tum.de \
    --cc=intel-gfx@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.