As of yesterdays patch, today is the 12/08/26, my custom user sights have stopped working though weirdly enough not entirely. Yes i am aware of the new changes, how to set them up properly, blah blah as i said they stopped working as of yesterday.
The weird thing is is that they will sometimes randomly start working. Sometimes after i rebooted the game a couple of times, sometimes after ive played a couple of matches. The point is i cant seem to fix the issue and i have to reboot the game or just pretend i never had them to get them back. I cant seem to fix the issue either as they eventually just stop working so i have no idea what is the matter. Is anyone else having this problem?
Im currently on steam, i did a file validation run and that actually fixed my issue till i came back after dinner, rebooted the game to which the issue had returned… in addition further file validations havent fixed the issue. I have no idea what up… the snail is snailing me it would seem.
Because the sight sometimes returns after several matches or restarts, this looks more like an intermittent loading/state problem than permanently damaged sight files. File validation temporarily helping supports that possibility, but it does not identify the cause.
I would test one vehicle with a newly generated current-format sight and temporarily remove duplicate or old definitions for that vehicle. Then select the built-in sight, restart, select the custom sight again and check whether the setting survives another restart. Also verify that the game can write its configuration and that cloud synchronization is not restoring an older setup. If the failure returns, capture the exact vehicle/sight name, client version and a .clog from a session where it changes from working to broken. That would be much stronger evidence for the existing issue tracker than repeated validation alone.