Intel 4000/Linux screen flickers :: Wargame: European Escalation Diskusi Umum

Halaman Toko

Wargame: European Escalation

Semua Diskusi Screenshot Ilustrasi Siaran Video Berita Panduan Ulasan

Wargame: European Escalation > Diskusi Umum > Rincian Topik

Dan

27 Feb 2013 @ 7:39am

Intel 4000/Linux screen flickers

Hey I just picked up the game for Linux (on steam) and I have an Intel HD 4000. The game boots up and runs but I'm getting a weird flickering or some kind of weird 3d artifact glitching in and off the screen making it really hard to focus on anything :( Any ideas?

< >

Menampilkan 1-3 dari 3 komentar

早安丶

27 Feb 2013 @ 9:38am

I am not good with tech stuff so I am just going to give you a link to the ♥♥♥♥♥♥♥♥ forum Tech Support http://www.wargame-ee.com/forum/viewforum.php?f=78

Terakhir diedit oleh 早安丶; 27 Feb 2013 @ 9:38am

remm

27 Feb 2013 @ 1:32pm

Same here, highly distracting ... Fedora 18 + Intel 4000. So I think you can report it, it seems reproduceable, but it could be a driver issue (no Mesa 9.1 yet on Fedora 18).

Adam Beckett memiliki Wargame: European Escalation

26 Sep 2024 @ 10:12pm

Eleven and a half years later, this is STILL and issue on Intel UHD iGPUs. (Intel N95 - in my case)

Since it happens to new CPU/iGPU SoCs, it is not a particular driver issue, or any given Linux distro. Seems that a (negative?) value in one line of code creates flickering triangles in OpenGL (native Linux version - not sure, if this same OpenGL issue happens on Windows. Need to check).

I have seen the exact same issue in a completely different game, only happening, with certain (bad) texture files.

As far as I can tell, this happens in Wargame, particularly, when the game is calculating and drawing the direct, dynamic green distance line from your unit to any given enemy (attack vector distance). But, it can also happen with camera rotations, randomly.

Not going to be fixed anymore, since it is a rare, niche case, for an old game everyone already bought, who wanted it.

Game is still playable with this issue, but not pleasant to look at, in the heat of Cold War battles in the year 2024.

A look at the source code could solve this?