Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Game is way too dark (Arch Linux 64 - intel i915 / mesa) #2830

Closed
ghost opened this issue Apr 1, 2017 · 6 comments
Closed

Game is way too dark (Arch Linux 64 - intel i915 / mesa) #2830

ghost opened this issue Apr 1, 2017 · 6 comments

Comments

@ghost
Copy link

ghost commented Apr 1, 2017

Hi all,
Supertuxkart 0.9.2 has been showing very dark graphics for about two months on my machine. My computer is running Arch Linux (64 bits) with i915 graphics and Mesa 17.0.2 (see attached file regarding glx info). The intel driver is up to date and so is STK.

See attached picture showing the game options and track brightness.

Anyone facing the same issue?

Regards,
Chris

glx.txt
image
image

@Benau
Copy link
Contributor

Benau commented Apr 1, 2017

I think you somehow enabled legacy pipeline, can you post stdout.log of stk?

@deveee
Copy link
Member

deveee commented Apr 1, 2017

You can remove version number from FramebufferSRGBCapable in graphical_restrictions.xml. It was set to 16.0 IIRC?

@ghost
Copy link
Author

ghost commented Apr 1, 2017

Hello Benau and deveee, thanks for your very quick replies.
I have just removed the version number for FramebufferSRGBCapable. It was indeed set to <16.0.

The file I modified is /usr/share/supertuxkart/data/graphical_restrictions.xml

Now the brightness is back to usual.

Thank you very much!
Regards,
Chris

@Benau
Copy link
Contributor

Benau commented Apr 1, 2017

Good, i should speed up my code for a new release

@Benau Benau closed this as completed Apr 1, 2017
@deveee
Copy link
Member

deveee commented Apr 1, 2017

Just to make it clear, I already removed the version number from graphical restrictions some time ago:
7e4dfdb

I reported it to intel rather long time ago and I though that they will fix it. IIRC they made a fix, but they eventually reverted it, because it broke something else.

And actually STK can work without srgb framebuffer, which would allow to remove this hack (GLES renderer already works in this way, though I don't want to introduce any regressions, so I have to look at this much more carefully).

@ghost
Copy link
Author

ghost commented Apr 1, 2017

Though I am unable to understand what it is about (I'm no expert at all at graphics issues...), if there is any test that needs to be performed on my machine, I'll give a hand gladly.
Thanks everyone
Chris

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants