Receiver 2: spotlights have lines showing their bounding edges, when Anisotropic Filtering is set to Full

[UNHchabo]

Checklist [README]

• [X] Device is not undervolted nor overclocked
• [X] Device is using the latest drivers
• [X] Game is not cracked, modded and use the latest patch

Game [Required]

Receiver 2

Game Platform [Required]

• [X] Steam
• [ ] Microsoft Store
• [ ] GOG Galaxy
• [ ] Ubisoft Connect
• [ ] Battle.net
• [ ] Epic Games
• [ ] Rockstar Games Launcher
• [ ] EA app
• [ ] Amazon Games app
• [ ] Other (please specify)

Other game platform

No response

Processor / Processor Number [Required]

i9-14900K

Graphic Card [Required]

Arc A770 Limited Edition

GPU Driver Version [Required]

32.0.101.5972

Other GPU Driver version

No response

Rendering API [Required]

• [ ] Vulkan
• [ ] OpenGL
• [ ] DirectX12
• [ ] DirectX11
• [X] DirectX10
• [ ] DirectX9

Windows Build [Required]

Windows 11 23H2

Other Windows build

No response

Intel System Support Utility report

igcit_ssu.txt

Description and steps to reproduce [Required]

When Anisotropic Filtering is set to Full, on all spotlights in the game, including the blue light shown by turrets, the lines at the edges of the cone show up visibly. When the setting is turned down to Partial or None, the lines disappear and the game looks as it should.

https://github.com/user-attachments/assets/7dfda13d-874a-439b-a7f5-760d1629f703

Game graphic quality [Required]

• [ ] Low
• [ ] Medium
• [ ] High
• [X] Ultra

Game resolution [Required]

1920x1080

Game VSync [Required]

Off

Game display mode [Required]

• [ ] Fullscreen
• [ ] Windowed
• [X] Borderless Windowed

Detailed game settings [Required]

I used max settings, as shown in the video, except when turning down Anisotropic Filtering to work around the issue.

Device / Platform name

ASRock Z790 Riptide Wifi

Crash dumps [Required, if applicable]

No response

Save game

The attached video shows the opening of the tutorial, this can be replicated on a fresh install of the game.

[Vivek-Intel]

@UNHchabo thanks for reporting the issue. We are setting up to simulate this issue internally and let you know if more information is required.

[Vivek-Intel]

@UNHchabo we have submitted issue to our engineering team (internal id for your reference only - 16025552829). Please know that we can not commit on the fix and estimated time to fix the issue. I will update this thread if we have more information.