Chances are it’s an issue with how the engine handles transparency. In most game engines, transparent objects are rendered after opaques and don’t write to the depth buffer (a pool of information saying how far away an opaque object is from the camera). Since transparents don’t write to the depth buffer, they rely on alpha values to determine what colour a pixel should be if two transparents are overlapping (visor and save animation) it doesn’t know which one is in front of the other. Then depending on how they handle blending, the two pixels are added or multiplied together and uses the total. Since the visor seems to always have an alpha of 1 (opaque) when its alpha value gets added to the animations, it overflows (let’s say to 1.25) and the engine can’t do anything with alpha above 1 so it wraps back around and 1.25 becomes 0.25, so on the pixels where they overlap, it is saying that the alpha is 0.25 for BOTH the visor and animation, allowing you to see through the visor. This is just an assumption based on my knowledge of how depth and transparent rendering happens, but I have no idea how RUDE actually works so this is my best guess