I play on PC with Vulkan. My current game version is 14858381.
Since the last big update (Y5S3) some operator weapon skins and weapon attachments keep resetting to default ones when I'm browsing the operator preview window. This happens every time I play the game. I didn't have this bug before Y5S3.
For example: When I'm browsing Ela's or Valkyrie's operator window it shows their equipped weapons with the default weapon skins and holo sights. In reality they both have different weapon skins and reflex sights equipped. When I open their respective loadout screens, it shows the weapons equipped with the correct skins and sights. Everything seems to be OK in the weapon loadout screen. But when I return to the operator window, the weapon skins and and attachments are reset back to the default weapon skins and holo sights.
This seems to happen randomly on different operators. For example in Kapkan's window the equipped black ice skin for 9x19VSN and 1.5 sights turn into the weapon's default skin and Russian holo sights. Still, when I look at Sledge, who has the Crawling Morass skin and 1.5 sights on his L85A2, it show's the weapon skin and attachments correctly. Sidearms are also affected by this, any other skin than default ones don't show up in the operator preview window.
The problem can be "fixed" temporarily by switching the operator's main weapon to another and then back to the one you want to use. After that the preview screen works OK. The bug returns when you log on the next time, so it's not a permanent solution.
When I get into a match the weapon skins and attachments are the ones that I have really selected. So everything's fine in matches, it's just the operator preview screens that are broken. I'm glad that this bug doesn't affect the real gameplay.
This is a mild annoyance, but I know the game shouldn't be broken this way. Before Y5S3 the operator preview screens did show the weapon skins and sights correctly. I talked about this bug to a friend of mine and he said he has the same bug. I searched the forums and Reddit, but didn't find any reports about this same bug.
Are you aware of this bug and if you are, what can be done to fix it?
Thank you in advance.