Resolved Screen Tearing?

[Spawn Of Achilles]

Summary: Vertical and horizontal screen tearing that is just noticeable enough to make the graphics look bad. I took a screenshot with reduced resolution to amplify the lines so you can see them better. Particularly evident on character faces, but also visible in scenery. Noticeable on menus or walking through the world. I have tried dozens of graphics fixes, including all forms of V-sync both in game and with Nvidia control panel to no avail. Just started a couple of weeks ago with 1.6.4. Also attached screenshot of current graphics settings as optimized by Nvidia.
How to Reproduce: Unknown
Have you used cheats and if so which: WeMod trainer, however the graphical errors appear with and without using cheats.
Scene Name (if related): Any
Media (Screenshots & Video):
Computer Specs:
OS: Windows 10
GPU: Geforce 1070Ti
GPU Driver Version: 30.0.14.9649
CPU: Intel i5-8600K
RAM: 16GB
Motherboard: TUF Z370-Plus Gaming
Storage Device (HDD/SSD): 1TB SSD

 

[MArdA TaleWorlds]

Forwarded to the QA team for further investigation. We will reach out again if we need more information. Thanks for reporting and sorry for any inconvenience!

 

[MArdA TaleWorlds]

Could you try to switch to the 1.6.5 and check if the issue still happening? Also, on which resolution are you experiencing this issue?

 

[Spawn Of Achilles]

On 1920x1080 resolution.

Beta 1.6.5 seems to be running fine graphically, the bug doesn't appear in any shape that I've noticed and I have the same settings. I did notice a slight bit of FPS drop in sieges with large armies that wasn't present before though, but that might just be a result of the graphic improvement.

 

[MArdA TaleWorlds]

Forwarded the info. Thanks!

 

[Henricos]

I seem to have the same issue.
Screenshot:

OS: Windows 10 Home 64-bit
GPU: 2047MB NVIDIA GeForce GTX 1060 6GB
GPU Driver version: 496.49
RAM: 16 GB
MotherBoard: ASUSTeK COMPUTER INC. PRIME Z370-P (LGA1151)
Storage device: 3726GB Seagate ST4000VN008-2DR166 (SATA )

 

[MArdA TaleWorlds]

Could you guys switch to 1.6.5 and check if the issue persists there too? We believe there is a fix on 1.6.5 that could also fix this issue.

 

[Henricos]

Yep switching to 1.6.5. seems to work thanks

 

[MArdA TaleWorlds]

Thanks for the update. Have fun playing!