Jump to content
Sign in to follow this  
You need to play a total of 10 battles to post in this section.
benlisquare

[0.4.0] Bug Report: Erroneous Serif Chinese Fonts

2 comments in this topic

Recommended Posts

Super Tester
1,177 posts
4,099 battles

 

1. Description

When the Chinese locale of the public OBT game client is installed, sans serif Chinese font should be used for all Chinese-language text, at all times. However, purely at random, incorrect serif Chinese fonts are displayed. Theoretically, serif fonts should never be displayed by the game client, which means that the program is having difficulty loading the correct sans serif fonts, and as a result it is resorting to a default fallback font. This is likely a memory access problem.


2. Reproduction steps

None, these errors occur at random. Sometimes they happen, sometimes they don't, however the errors appear very frequently. There is no fixed series of steps which guarantee a correlation that the error will occur.


3. Result

The following screenshots depict the erroneous serif fonts used to display Chinese text:

 

VMw0GMr.jpg

 

In the above image, "等待玩家" (waiting for players), "一般戰鬥" (standard battle), and the text at the right hand side are written in a non-antialiased serif font. Notice the "blur" effects on the right hand side? That looks absolutely terrible with serif fonts.

 

IMURnHv.jpg

 

In this image, the description text on the left hand side explaining the benefits of premium ships is written in serif font with no anti-aliasing.

 

b6CXpeQ.jpg

 

In this image, the ship class names (below the numbers), description for "random battles" (at the bottom, above the button), and "您的艦艇" (your vessel) is written in serif font, with no anti-aliasing. Furthermore, within the line "在您範圍內的玩家" (players within your range), the text is correctly displayed with anti-aliased sans serif font, with the exception of "內", which is written in anti-aliased serif font.

 

g5BzFf1.jpg

 

The ship type ("主力艦", battleship), the words for "tier" and "ship experience" in the upper right corner are written using serif font without anti-aliasing. Furthermore, the display of premium days remaining, server (伺服器), players (玩家), remaining time for mission updates (更新時間), buying gold, exchanging credits, and converting free XP are also in serif font without anti-aliasing. Also pay attention to the mouse hover tooltip below the "join a division" area, which also has the same font problem.


4. Expected result

The following screenshots display what the UI should appear like (i.e. correct sans serif font usage):

 

8kWo9XG.jpg

 

All of the following are displayed in the correct anti-aliased sans serif font: The ship type ("主力艦", battleship), the words for "tier" and "ship experience" in the upper right corner; display of premium days remaining, server (伺服器), players (玩家), remaining time for mission updates (更新時間), buying gold, exchanging credits, and converting free XP.

 

Ilj2zi2.jpg

 

All text is displayed in the correct anti-aliased sans serif font, and the "blurring" effect on the right hand side does not look stupid and ugly, because it correctly displays behind the text.

 

ohJsCdF.jpg

 

All text is displayed in the correct anti-aliased sans serif font. The line "在您範圍內的玩家" (players within your range) has a uniform font with no odd characters which stand out.

 

5. Technical details

These screenshots were taken using the public OBT WoWS game client, version 0.4.0, on the Asia server, using the Chinese-language locale.

 

Client was run on Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1, English system language, Japanese locale. Dxdiag: http://pastebin.com/P2qnR9S0

 

Edited by benlisquare

Share this post


Link to post
Share on other sites
Beta Tester
2,718 posts
1,988 battles

Oh yeah +1 to this.

 

I've seen this since CBT - but I thought it's just my connection - apparently not.

 

This seems only happening after a period of time or a couple of games. Also, It cannot display "VII" (Tier 7) correctly after this bug and will only display "...".

 

So this is a bug after all.

 

Edited by Alvin1020

Share this post


Link to post
Share on other sites
Sign in to follow this  

×