BUG: Unspecific missing surfaces

[dsvensson]

ezQuake version:
3.6.4

OS/device including version:
Windows and macOS at least, likely not OS-specific.

Describe the bug
Sometimes some surfaces (few, most of the map is drawn) are not drawn. The error is stable when moving around if I understand correctly. Not enough reports to draw any conclusions on if it's a specific texture that's missing on all places across the map or if it's missing geometry somehow.

Happens both in modern and classic renderer.

To Reproduce
No pattern identified yet. Fairly rare.

Expected behavior
Correct drawing.

Screenshots
See screenshots in comments.

Additional context
Started in 3.6.4, no bisect made, not yet seen by any dev, vid_restart fixes the issue. Possibly a free'd texture that has been a bug, but was first exposed with newer 3rd party deps that came with 3.6.4, a bisect will help here.

Would be great if the people experiencing this can compare their hardware and configs and see if they have something in common. Has been known to happened with modern Nvidia hardware and updated drivers.

[dsvensson]

from xero,

[dsvensson]

from nikke,

[dsvensson]

from er,

[dsvensson]

from gnz, on macOS so old renderer,

Update: This particular issue has got a workaround now. It's isolated to macOS arm64 based on the current level of understanding.

[hoffarn]

Sometimes if i load a cfg during a game i get this bug when the map is reloaded. I havnt been able to reproduce it but it occurs a couple of times a week.

I use Win 11 with latest nvidia drivers. In nvidia control panel i have changed some settings specific to ezQuake, Power management mode: Prefer maximum performance, Texure filtering anisotropic: ON. Texture quality: High performance. Texture filtering - Trilinear optimasation - ON.

Some settings in my config:

//Texture Settings
gl_externalTextures_world "0"
gl_max_size "16"
gl_texturemode "gl_nearest_mipmap_linear"

//xero

[dsvensson]

Something lacking here from everyone experiencing this issue is frequency of it happening. Has it happened once since release, does it happen a few times a week, does it happen daily, does it happen first after client has been running for a few hours or can happen first map after a fresh start?

I can prepare a couple of different builds to easily find the issue, but that requires attention to detail and not launching the wrong client and marking a working build as broken. Perhaps I should figure out a way to hardcode a message in the UI when running such a build so it's guaranteed to end up in screenshots.

[dsvensson]

None of the above screenshots use the new gl_outline, are perhaps all above screenshots from the old renderer?

[marffinn]

I recreated the glitch where the ceiling and floor textures are waving on entire map, dm4, dm2, aero eveywhere. And after reconnect it persists.
Steps I did on ezq running for about 20 minutes <-- so not that long to trigger that strange warning "that the machine is up super long and what not" <--- someone on forum said it might be a culprit, but in this case it's not.

first i typed in:
cl_maxfps 1001 <-- previously I had 1155,
vid_conwidth 600 -> vid_restart
vid_conwidth 480 -> vid_restart
vid_conwidth 320 -> NO vid restart -> instead /map aerowalk
after map loaded -> vid_restart
vid_conwidth 800 -> vid_restart <--- after this one, the textures go crazy
my ezq is 3.6.4 win64:gl
here's my cfg if it helps
https://github.com/marffinn/QuakeWorld-Server-Browser/blob/main/config.cfg
have fun not finding the bug :D

[dsvensson]

Always include GPU model, driver version. As the original description says, talk to the people mentioned in this thread to see if you have more similarities in your hardware/OS setup.

Probably also worthwhile running https://www.memtest86.com/ over the night to rule out broken non-GPU hardware. It's free, and you just write it to a usb stick (tutorial video on download page) and boot and start the test and it'll start copying data in and out of ram in various ways. Good at detecting faulty hardware.