Badly view weapons

[edombek]

in all variants graphic settings

[The-Gig]

Could you please provide some more infos? Operating System? Graphic card? Binaries used (e.g. stock 0.8.8, nightly builds, third party fork)? Did you also try using a clean q3config.cfg, or "clean" homepath and basepath (without extra pk3 files in baseoa)?

[edombek]

Could you please provide some more infos? Operating System? Graphic card? Binaries used (e.g. stock 0.8.8, nightly builds, third party fork)? Did you also try using a clean q3config.cfg, or "clean" homepath and basepath (without extra pk3 files in baseoa)?

I check configs and check stock binaries and git version builded this: https://aur.archlinux.org/packages/openarena-git I am usage ArchLinux, NVIDIA GeForce GTX 1650, nvidia driver (535.113.01), but openarena used intel graphics...

[The-Gig]

Some OpenArena packages used by some Linux distros repositories are known to have strange issues. OpenArena Team does not have control over them. Try manually downloading the official package from OA website...

[edombek]

if you download from the site, the same problem

[The-Gig]

Did you get the problem since your very first start of the game? If that's the case, it might be a video card driver problem (try if there is another version you can try to install. But I'm not familiar with drivers under Linux). If it started recently, maybe you autodownloaded some poorly packaged pk3 file (e.g. some third party map) which messed up your game (you can try using a clean settings/autodownload folder by starting OA with "+set fs_homepath [path]" parameter from OS command line.)

[edombek]

It didn’t help... I hope that the drivers are installed and this will be fixed soon

[The-Gig]

You didn't specify whether you experienced the issue since day one or it started later... However, maybe you may try using some other versions of the engine...

[ghost]

I have exactly same issue.

Os: Arch linux, 6.1.68-1-lts Graphics: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] (rev 0c) DE: Wayland+Sway

I haven't launched the game for a long time (I don't remember did I even ever start it on this machine). Today wanted to play and experienced this bug. I tried to reinstall openarena, tried to remove it and instead install openarena-git from AUR. Tried to remove $HOME/.openarena and tried different graphics settings in game. Still same result - some weapon textures like on that screenshot are broken. Interesting what not all of them are broken, so I found:

• Gauntlet - texture broken
• Machinegun - texture broken
• Shotgun - fine
• Rocket launcher - fine
• Grenade launcher - fine
• Lightning gun - texture itself is fine, but lightning effect doesn't show. Didn't check others...

Here is the log (game executed from openarena AUR package): log.txt

[leilei-]

this intel bug is unfortunate but at the same time it intrigues me. I don't have any intel iGPUs relevant nor a linux install that could use them but I do wonder if r_ext_vertex_shaders could be affecting it in some way, or gulp a glibc regression.

The machinegun barrel uses the same texture as the rest of the gun so I doubt it's texture specific. I almost think it's related to the MD3's bounding box (for internal rendering, not collision)

[The-Gig]

Situation recap:

• A change in glibc (important Linux library) triggered a dormant issue with a function apparently implemented in a less-than-perfect way in OpenArena gamecode, causing inability to load secondary weapon models or something. The issue does not affect Quake3-gamceode-based mods.
• A fix has been implemented in OA gamecode: https://github.com/OpenArena/gamecode/pull/346. Problems are 1) who knows when a new official OA release containing the fix will happen and 2) oa-based mods need to backport the fix from baseoa to get fixed (at least Ratmod already did).
• Also people running other ioquake3 forks noticed the issue (example https://github.com/OpenArena-Ioq3/openarena-ioq3/issues/5) and it looks there might be some way to apply a fix through the engine, which should automatically fix all mods, maybe these ioq3 pull requests may be worth looking at: https://github.com/ioquake/ioq3/pull/639 and https://github.com/ioquake/ioq3/pull/659 (at the moment of this writing, they have not been merged into ioq3 yet).

[NoiseByNorthwest]

Making Q_strncpy() working with overlapping pointers is the best solution. I wasn't aware that fixing at this level would save us from having to fix all mods.