3.7.1, r4209: Screen flashes during startup

[tomreyn]

When I start up the game on 3.7.1 or r4209, the screen flashes shortly with white stripes on an otherwise black background on my atibox. It looks like this can be due to some initialization taking place there.

I've had this issue with 3.7.1 and still have it on r4209, but it's not prevent on 3.6.0.3. 3.7.0 has a similar issue, there the main menu screen shows during this initialization (and before the intro starts).

Here's a video of head of trunk. A screenshot of the frame with the flash (roughly at 1 sec playtime) is also available. It's really short, so not a big issue, but it wasn't present in old versions.

[tomreyn]

This issue persists in r4246.

I'm wondering whether this can be related to initialization of the libvlc video support. It does not happen when I start the game with --starthost.

[softcoder]

Try setting:

GammaValue=0.0 in glestuser.ini and see if that solves it?

[tomreyn]

No, it doesn't help, this (mostly) white "flash" is still there.

[softcoder]

I've minimized the game assets loaded on startup. Please try git HEAD and tell me if you are able to reproduce this?

[tomreyn]

I'm afraid it still happens on intelbox (can't test on atibox now).
Since I've reported this issue here, I've learnt that what happens there is the following sequence of events:
You start the game
The monitor switches to full screen without any artifacts
The "flashing" takes place
The first into text displays

When the screen "flashes", it does not just show a white screen, but it actually displays a "random" screen which was previously displayed at some point after my last reboot  for ~ half a second. When I tested today, the screen which "flashed" was an image of my Desktop, i.e. showing several folders on my XFCE4 desktop on top of my desktop background.

I just tested again, and this time I got to see this forum post I am just writing. Then I tried again, and there was no flash, and on yet another try I got the Desktop again. So this feels like it can be a mix of Mesa (which powers both systems I see this artifact on) and libvlc initialization issue.