Open TacoDeBoss opened 8 years ago
It's strange. Is this bug appear in other games on your PC?
No, I've never seen it or anything like it on any other game.
I caught it on a log, it happened at about 03:03:54, a few seconds before I typed 'quit'.
Update: I saw it happen on Windows 10 as well, just now. Still no idea what causes it...
Still happens on the latest Linux build. Kernel 4.8.4, GTX 1080, Intel Core i7-3770k, Xash3D Build 592, Nvidia driver 375.10.
As I said above, still happens on Windows 10 as well. Same specs obviously, not sure of the driver version. It's happened across every Nvidia driver I've tested.
When I can, I'll test on my AMD laptop and try to reproduce this.
Still present on Windows 10 and Linux, I've even seen it on Android on my Alcatel A30 Tablet.
It is much less visible on a lower framerate. At 30, I did not see it occur, nor at 60, but at ~70 or above, it became visible, and my preferred framerate for Xash3D at fps_max 142, it was visible nearly constantly.
I think, we need to implement gl_debug. Maybe driver has some debug messages about that
As an aside, I can confirm this does occur for me on my openbsd/amd64 builds of xash3d as well. I've been too happy that I can play single player at all to bother making a report up until now, but seeing as it affects many platforms why not.
For me, it seems mostly on the patches that are drawn for things like blood splats or burn marks from explosions. The flicker tends to happen when moving the mouse to look around -- if I stop moving the mouse the flicker stops, though it can sometimes stop with the patches in the not-drawn state.
What if switch r_vbo, r_studio_drawelements, r_dynamic?
And gl_extensions
Sometimes while playing the game, I can spot what I can describe as a 'flicker' or 'flash' in the game. This has only been tested on my Debian Sid machine (Debian Sid amd64 Intel Core i7-3770k, GTX 1080) but it may affect others. I've spotted this bug on this native build of Xash3D and when playing the Windows build of Xash3D through Wine. I haven't seen it on Android, and I don't recall seeing it on Windows. It's also happened on various Nvidia proprietary drivers, I haven't tested it with open source ones.
I couldn't get it to happen while recording a log, but I'll keep trying. I did catch it on a video, though. This video was recorded in Build 520 but occurred in earlier builds and occurs in later builds. I'm running Build 540 now.