Multiple special characters are no longer displayed properly [since v1.15]

---

@REDRA-11 wrote:

Product: F1 23
Platform:Xbox Series X
Please specify your platform model. Microsoft Xbox Series X
Summarize your bug Multiple special characters are no longer displayed properly. After you save a setup that contains these characters, they are now displayed as squares instead. I use special characters when saving setups as indicators for various testing results obtained with it. It happens in all game modes. It happens in both singleplayer and multiplayer.
What is your 16 digit Report Code? JACE-AJRJ-ATGT-GTJG
Can you please provide the name of your current internet service provider? -
Which area is the bug/glitch in? Single Player
Steps: How can we find the bug ourselves? Go to TT or any game mode where you can save a setup. Save a setup that contains special characters. Some of them will be displayed as squares instead. See the attached demo screenshot(s) / video(s) for reference.
What happens when the bug occurs? Some special characters are displayed as squares.
What do you expect to see? All special characters should be displayed properly, as before.

‌

Demo screenshot(s) / video(s):
- Screenshot - 1st setup is the result of entering the 1st and 2nd rows of special characters on the Xbox keyboard - 2nd setup is for the 3rd and 4th rows: https://1drv.ms/i/s!Ahnxpj614XMbibd5sYTNpf2cR2Ty0A?e=G8Wn7g

Last update: 10-Apr-2024 - v1.20

---

Don't use special characters. It's been known to cause issues in previous games. I agree it is a bug, but it's to do with multi-language I think that the error trapping is going to be an issue.

I've always been using them as indicators for things such as whether a setup was tested with equal or realistic performance, or in a GP qualifying or race session, because of the fairly low character limit. It's never been an issue in any game until update v1.15, when my entire setup list of ~100 setups started being displayed with squares instead of whatever I actually labelled them. I had this report ready months ago when that update was released, but I just forgot to post it at that time.