Catweedle

Yes, it will, unfortunately; cf. this thread wrt. the color issue: LMV psychedelia. To be honest, I myself switched back to the original as well. For other reasons than that, though.

Greetings, in first person view (unbottoned TC/gunner) the Ulan is showing shadows for seven mounted soldiers (counted while spinning around); not visible in 3rd person view.

Put your tracer.dds into 100% view and check out the right side of the tracer ball -- pixels for red glow has been cut off. Never mind -- won't be too prominent ingame.

:confused: Edit: Oh okay, I see now. A bit of redundant work I did there then. Any reason for the cutoff of the image to the right, Tacbat?

Greetings, I've made some missile.dds (the image file used for tracer rounds) to "theme" the tracer visual(-s) to my liking -- as far as possible. Maybe someone has also use for it, so I'll throw it in here. One version (1) is close to the original, a bit smaller, less orange, more colors towards red/purple, mipmap fade to color (gray) removed. Version 2's glowing edges are a bit fuzzier, amount of R glow dominating. Backup originals before overwriting. Remove the .vn. of the desired version beforehand. trace_orig.jpg shows the original tracer round graphics. tracer.zip

Your answer is partially the source for my initial confusion. The 1A5 and 2A4 display the info box for TC override-mode no matter what setting is chosen -- the Leo 2A5 (and E, I suppose; not tested) only does it on easy settings (or medium, as you suggested, also). I am just curious to know, same goes for the inconsistencies for salvo rate and length messages -- the game still plays great.

Greetings, I've noticed the Leo 2A5 and -E versions do not display any visual aid/confirmation as to which override mode the TC is currently in, i.e. no message or boxed graphics (in periscope view). I am aware of the red bulb and the light on the TIM (2A5+) indicating modes -- is this the reason why the 2A5+ versions do not display any additional ingame information (boxed graphic, message)? Similarily, the rate of fire for e.g. the M3 is displayed textually when changed, whereas the salvo length for e.g. the Pizarro is not confirmed textually (message) -- it only says that the salvo command has been issued, but not the length. Those examples are actually the only ones I have. I assume simulation of real life conditions and processes in most cases -- just wanted to clarify/verify it here. Thanks, and best regards ... CW