[Mesa-dev] [RFC PATCH 1/1] st/dri: add a new driconf option override_glsl_version for ARK games

Marek Olšák maraeo at gmail.com
Fri Feb 10 15:01:17 UTC 2017


On Mon, Feb 6, 2017 at 9:26 PM, Samuel Pitoiset
<samuel.pitoiset at gmail.com> wrote:
>
>
> On 02/06/2017 04:45 PM, Eero Tamminen wrote:
>>
>> Hi,
>>
>> On 05.02.2017 15:19, Samuel Pitoiset wrote:
>>>
>>> On 02/03/2017 07:48 PM, Bas Nieuwenhuizen wrote:
>>>>
>>>> As far as I can see[1], when the game detects GL 4.3+, the engine tries
>>>> to load a different set of shaders from disk, but the game developers
>>>> have not enabled the right flag during building, so the shaders for
>>>> GL4.3+ are not actually distributed with the game, which results in a
>>>> failure to load the game. From my POV this is entirely the fault of the
>>>> game.
>>>
>>>
>>> I can confirm that these ARK games fail to start with a 4.3+ context.
>>> But from my point of view, I'm not really *sure* it's a game fault
>>> because as you said in the related ticket, the game starts correctly
>>> with AMDGPU-pro because it returns the right context. Maybe we should
>>> just do the same?
>>>
>>>>
>>>> That said, the bug contains a report from someone else that it works on
>>>> intel with GL4.3+.
>>
>>
>> That was me.  The game is still early access and has been updated many
>> times since.
>>
>>
>>>> I never got to test that or look deeper into this, so
>>>> it could very well be that I overlooked something during this analysis.
>>>
>>>
>>> It would be interesting to get a confirmation, but I don't have any
>>> intel hw here.
>>
>>
>> Results from quick try on Ubuntu 16.04 with today's version of the game
>> (ARK: Survival Evolved)...
>>
>> With (Ubuntu 16.04 default) Mesa 11.2, game starts to the game main
>> menu, but when one starts from that a single player campaign, it will
>> crash before the real game begins, after few minutes of loading (when
>> game RAM resident set size has grown to ~10 GB):
>> ------------------------
>> Thread 1 "ShooterGame" received signal SIGSEGV, Segmentation fault.
>> 0x0000000001369f9b in _start ()
>> (gdb) bt
>> #0  0x0000000001369f9b in _start ()
>> ------------------------
>>
>> With latest Mesa (with or without the patch), game will just show a
>> small dialog with few garbage characters and exit.  I have no idea what
>> it wants to complain about.
>
>
> That patch is actually wrong for intel (it doesn't override anything).
>
> Maybe you can try this one?
>
> https://cgit.freedesktop.org/~hakzsam/mesa/log/?h=override_glsl_version_v2

FYI, I'm OK with this version of the patch.

Marek


More information about the mesa-dev mailing list