IGCIT / Intel-GPU-Community-Issue-Tracker-IGCIT

IGCIT is a Community-driven issue tracker for Intel GPUs.
GNU General Public License v3.0
117 stars 4 forks source link

Quake (and Quake 2) rereleases by Nightdive: Texture smoothing is forced on, even if it's off on Vulkan renderer. #632

Closed yawnbunny closed 7 months ago

yawnbunny commented 11 months ago

Checklist [README]

Game / Application [Required]

Quake & Quake 2 (rereleases by Nightdive)

Game Platform [Required]

Other game platform

No response

Processor / Processor Number [Required]

Ryzen 5600

Graphic Card [Required]

A750

GPU Driver Version [Required]

31.0.101.5074

Rendering API [Required]

Windows Build Number [Required]

Other Windows build number

No response

Intel System Support Utility report

n/a

Description and steps to reproduce [Required]

Both the Quake and Quake 2 rereleases by Nightdive default to the Vulkan renderer, however, on Vulkan even if you turn Texture Smoothing off, it does nothing and remains on. It works as it should on DX11 and the textures revert to the classic nearest neighbor look.

It appears that the option to change the renderer in the Quake 1 rerelease was removed from the Video Settings menu, but you can still change between the two by editing "seta r_rhirenderfamily" to either "d3d11" or "vulkan" in kexengine.cfg in C:/Users/[user]/Saved Games/Nightdive Studios/Quake. In Quake 2 it is still available in the same menu you change resolution in.

Game graphic quality [Required]

Game resolution [Required]

n/a

Game VSync [Required]

On

Game display mode [Required]

Detailed game settings [Required]

vulkan 20231210073618_1 20231210073632_1

dx11 quake2ex_steam_2023_12_10_07_49_03_009

Device / Platform name

No response

Crash dumps [Required, if applicable]

No response

Save game

No response

freak2fast4u commented 10 months ago

Reproduced here on A770 with 5081 driver with the Q2 version from GOG (version 5984 of the game, as reported by GOG Galaxy). Swapping out my GPU to cross-test ... brb.

Edit : Texture smoothing effectively disabled with Vulkan when set to Off using my old RX 5700XT, contrary to the A770 where it's forced on regardless of the setting, so it's an Intel Vulkan driver bug from my perspective indeed.

Ilya-intel commented 10 months ago

Hey @freak2fast4u , @yawnbunny , I also tested it with Nvidia and the option is working as intended. Give me some time to collect all the data and pull it to the dev team.

Ilya-intel commented 10 months ago

Issue reported to developers. The BUG ID for reference: 18035938389. I'll keep you posted here @yawnbunny

yawnbunny commented 10 months ago

Great. I neglected to test other games before, but this behavior appears to be present in all Vulkan games, GZDoom does this too on Vulkan but not OpenGL. But I'm sure the team is aware now so it will probably get fixed in other games too.

dorian-apanel-intel commented 9 months ago

@yawnbunny Thank you for reporting it. I tested it on Quake 1 rerelease by Nightdive and it looks like game always sets anisotropy filtering and I see no GUI option to disable it. Unfortunately, we cannot mix those (aniso and harsh textures) in our hardware, so currently we default to smooth textures with anisotropy.

We're looking into favoring VK_FILTER_NEAREST (harsh textures) instead of smooth anisotropic textures if both are set.

In the meantime, you can use this command in quake console: seta R_rhimaxanisotropic "0" (Mentioned in this topic) Together with Texture smoothing disabled in Quake options, it should give you harsh textures in close proximity, but can introduce artifacts on distant surfaces at sharp angle.

yawnbunny commented 9 months ago

Yeah, that does solve the problem. The nearest neighbour PSX style is common in many indie games today, so doing something about it now is prophylactic and would assure games in the future look the way they should.

I confirmed this in GZDoom also. Even with filtering on nearest, and anisotropic filtering off in options, it still shows up smoothed. But if I did "gl_texture_filter off" in console it worked as it should.

Ilya-intel commented 7 months ago

@yawnbunny This is now fixed on 101.5379 driver.

freak2fast4u commented 7 months ago

@Ilya-intel Fix confirmed on my end, thanks guys !

Ilya-intel commented 7 months ago

@IGCIT Could you close as resolved?