*bump*
Back from Code investigation and further tests, I see a little clearer now BD.
Fact is that this issue has always been there, it's not related to any Patch Pack (rather opposite, but more below).
It's definitely a client setting on your side, If I had to put my money somewhere, it'd be the name you've defined in the "Pilots" roster.
I can say so because I tried it myself, opened the "Pilots" Menu, clicked "New" to create a new slot, removed the russian crap left and right and entered "BalDaddy" in the center.
I swear I didn't add a Tab, however... it turned out that a tab was added automatically to whatever reason.
Retried with Plain 4.10.1 game, same issue.
The difference is extremely subtle when you look at it in the main menu.
This is the "good" one:
This is the "bad" one, note the tiny enlarged space between the last "y" and the apostrophe:
Only when you open the Pilots Roster page again, it will scream right in your face...
For those who are interested, a funny background story is that this issue was actually supposed to be solved on server side already.
There's a flag "filterUserNames" that can be set on server side (and in fact it was set on our server), which causes all characters which aren't "valid" to be stripped from usernames.
"Valid" characters are generally all readable characters of the ASCII set plus russian characters.
Spaces, Tabs etc. are not "valid".
Therefore this issue should not have happened as the names should be filitered on the server. And in fact they are.
What the IL-2 Developers forgot however is the fact that in a dogfight server environment, certain Event Log messages are forwarded to the Server for local logging.
These Event Log entries are generated on Client side (hence they don't have their usernames filtered for "invalid" characters, since the Client is no Server) and then forwarded "as is" to the Server and written to the Event Log there "as is".
Now that FBDj parses the Event Log for stats generation, the issue started to arise, since for a User "BalDaddy<TAB>" the Event Log entries are completely out of sync, partly with tab (Client generated, forwarded messages), partly without (Server generated).
That's why.
And of course it's fixed now and will be uploaded to the server in a split second
Best regards - Mike