Isssue with transparent assets when bilinear filtering is selected.

[R.I.P]

Perhaps I haven't searched using the correct terms, but I'm not finding any mention of this on forums, or seeing evidence of it in older/recent You Tube videos...

When bilinear filtering is selected in the "sunglasses menu", there is a visible reduction in the menu font. This doesn't surprise me, but the heavy "erosion/shrinkage" of vegetation, window grating and other semi-transparent textures, most notably, losing the "rings" of the barbed-wire entirely, is more than was expected...

I'm running Win 10 with a GTX 960, and I have tried disabling most of the graphics options in the game config file/launcher, game settings, and Nvidia Control Panel.

Can anyone tell me if this is a known issue, or if they've seen it mentioned previously?
Maybe someone has dealt with a similar issue?

I'm running the game with only Joy to Key and the 2,3,4 Widescreen Patch; also tried using Sardoc's ultimate Tomb Raider 3 level files also due to:

"Revised transparency data of every level (TR3 and TLA), so that some textures which were opaque before modding would no longer have transparent pixels or slightly changed shades.
(not sure what this fixed).

Thank You.

Edit: Switching to "software mode" in the launcher, allows the textures to render as normal, but the framerate suffers with the bilinear filtering option enabled.

Tried February 2018 drivers... did not help.

Edit:
Newer videos on You Tube, are starting to show the phenomenon (Sep-2018).
Visible "reddish line" (Peixoto's Patch fixes this) in the menu, bushes and barbed wire, mansion gates and window frames reduced.

Note: The issue does not appear in the #1 installment of the playthrough, until about the 2:08 mark, when after texture dropout, the player launches setup and switches to hardware mode


https://www.youtube.com/watch?v=6kfhM8TToDE&index=6&list=PLz1L4i4wOVAcNf9JuJyXfiu_k-EVo7_4e


Speedrun which features the issue:
https://www.youtube.com/watch?v=r2vfxehHdLY

[Lord Tony]

im also having same issue with invisible barb wire

[R.I.P]

I assumed that eventually Arsunt, or Peixoto, would be made aware of the issue and likely provide a fix.

I just now found a reference to the problem in Peixoto's patch thread:
https://www.vogons.org/viewtopic.php?f=24&t=53121&start=500

They claim that it's been mentioned previously on the TRforums, but I haven't found anything yet.
(cant find a "search" button)

Edit:
Found some old threads that mention the issue as far back as 2015. Seems to be related to Nvidia graphics drivers and cards; using dgvoodoo seemed to be the most common solution.