sunnyssk

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: i7-7800X | GPU: GTX 1080 | RAM: 32 GB (It could be more of a feature request than a bug report so please consider moving/merging this topic if necessary.) It's been a long time that I have noticed that the fonts are not rendering correctly in KSP2 for its Chinese version. This is a common pitfall for games involving a Chinese version which is not developed by a Chinese company. Short background: east asian countries share a large set of Chinese characters (Han characters; Hanzi/Kanji/Hanja) in common. However in China(Mainland/HongKong/Taiwan)/Japan/Korea, there are differences in writing styles. The differences here are not about simplified/tradition versions of Chinese characters, but about how the same character looks like in different regions, see figures in: [https://en.wikipedia.org/wiki/CJK_Unified_Ideographs] and [https://en.wikipedia.org/wiki/Han_unification]. What's happening: The Chinese characters for the Simplified Chinese (SC) version are rendered in a way which is used either by Traditional Chinese (TC) or Japanese (JP), which means the game is not using the correct font or font subset for the desired language. An example would be the word in the main menu "设置" (Settings). The character "置" should only have a horizontal line at its bottom end in SC, while in TC or JP styles it has an additional vertical line at the bottom-left corner, which is happening to SC in current games. Possible mechanisms relavant to the issue: The fallback font for CJK(China/Japan/Korea) characters now seems to be Google & Adobe's Source Han Sans (also known as Noto CJK Sans). The font family contains a subset of fonts with different suffixes (SC/TC/JP/KR), see [https://en.wikipedia.org/wiki/Noto_fonts]. Each of the fonts with a specific suffix contains the right shapes of the characters used by the group of people in that language. If the font family is incomplete, or the fallback is just directed to one of them, it might be producing an incorrect shape of CJK characters for the target language. To resolve this issue, you might need to bind each existing east asian language to a font from this family. Note that this does not involve any modifications in the translation strings. It has nothing to do with how characters are encoded but about how they are displayed. Included Attachments:

Some of the errors I can find in the settings menu: Under "Input", section "global" is translated as "全球" (globewide), while it should be "全局" (general). Under this section "escape menu" is translated as "逃逸菜单" (flee menu). This should be "ESC菜单" (just leave the name ESC untouched). Under "Input", section "audio", "mute" is translated as "禁音" (sound forbidden). The meaning is not wrong, but should be "静音" as the latter word is the exact translation for "mute" and is widely used. Under "Gameplay", "joint" is translated as "关节" (orthopedic joints). This should more be "节点" (nodes), as the enhanced joints are not something expected to move. Under "Audio", section "advanced", "laptop speakers" is translated as "复制当前拿起或选中的组件" (copy the part that is currently picked or selected). Should be "笔记本电脑扬声器". For the single player mode, the word "campaign" is translated as "战役" (war/battle). "挑战" (challenge) could be a better choice for this scene as we are not really fighting against something. In VAB, when exploring details of engines, there is a label "FLAG". This is translated directly into Chinese (旗帜), however, depending on the context, you might want translations like "特点"(features), "局限"(limitations), etc. This is an example I find where the original text is adding difficulties to localizations because it's not fully self-explanatory. In general, the new translations are obviously improved, but some of the existing problems are still there, especially considering it's been 10 months after the first release of the game. Please ensure your localization team is actually having some appropriate persons doing the proofreading & in-game QA jobs for the earlier entries.

For the issue #2 above, one of the possible solutions I can come up with would be removing the commas between years, dates and hours.

There would always be controversies against this topic, but I would still like to share some of my thoughts as a part of the community who knows little about the details of the development ... I could be wrong but I don't think these thoughts could be completely nonsense: It is everyone's goal to eliminate the unexpected behaviors before publishing something, but in large systems this can be unrealistic. KSP 1 has been released for about 8 years from now and there was still a patch/bugfix last November. Presumably if you want to make KSP 2 perfect it would be another 8 years - no one can wait a single patch for such a long time. A more practical way might be updating in a more frequent manner and optimize iteratively. In KSP 2 we have much more features on the way, and thus we can expect more bugs ahead. By sending out patches every several weeks it can be hard to imagine this game leaving the EA stage within several years. There are different levels of bugs. The most serious ones at present are significantly degrading the gameplay experience: orbit is unstable upon time warp / EVA, velocities are predicted incorrectly upon exiting SOI of some celestial bodies ... for bugfixes against these issues every minute counts. No one can expect a complete journey to & from Minmus without S/L after a week of the release, and this is even just a satellite around Kerbin. It's okay if we don't have every single string translated correctly in the first week, but it can be lethal for a simulator if it does not have its physics working in a proper manner for a week or more - which is happening. The community is way larger than a QA team. It certainly cannot do whatever a QA team could do, but on certain aspects it's way more efficient - that's why we have EA. But to fully utilize this property you would be in need of active responses to it. No player would stay 24/7 in the forum waiting for a solution or update for a single bug uncovered. Nor will a player report similar things to you twice - until a new release is available and the issue still unresolved. If the input from the community is of importance, then please consider more communications and updates. We don't have IT tickets, so the only way to confirm the problem is really being solved is by seeing it eliminated in the coming updates. Speed is not everything but it is at least not weighed less than quality - at least for significant bug fixes. Comments are welcomed towards my words above.

Similar things happed to me once when I loaded the saved file with a spacecraft landed on Mun. I watched it dropped below the ground. But that was not reproduced. Not sure what is the major contributing factor.

Instance on wrong velocity prediction during a returning trip from Laythe is also available on Bilibili (language: Chinese): https://www.bilibili.com/video/BV1nv4y1a7yH (by ReachStar) At 11'56'': -- "最终，在利用引力弹弓返回时，出现了弹射后显示轨迹和实际轨迹不一致的 bug，飞船 dv 耗尽" -- Finally, when trying to return by utilizing gravitational slinghost, a bug emerged, where the predicted trace does not match the actual orbit after the slingshot. The spacecraft runs out of its dv (thus the returning attempt failed). Though the returning trip is not shown with its full details, it seems that this issue is happening on exiting Jool's SOI.

The systems now seems to hire new Kerbalnauts automatically & instantly once you fill some into the command pods to make the total number available at KSC equals to 10. I'm not sure whether there is also an upper limit, but if there is then perhaps they are simply missing because KSC does not have enough capacity. Also in this version we do not have the Astronaut Complex so we can't hire or fire by hand.

I have been playing KSP 1 for 3 years but I haven't realized the existence of this forum until the release of KSP 2. But anyway we are coming now! Greetings Kerbals!

KSP Version: 0.1.0.0.20892 Localization bugs below are for Chinese (Simplified). [Some words before error reports] I am with 050644zf that the Chinese translation is way from satisfactory at this moment. Large texts such as part descriptions are generally nice, but tons of short strings are incorrect or untranslated. They are literally EVERYWHERE which strongly degrade the experience during playing. Please give the community some more efficient ways to report or contribute to the translations as there are simply too much to report on this forum. There are also many instances of machine translations where further polishing should be applied. This latter case is most obvious in subtitles for tutorial videos. Besides please be careful on the selection of regional versions of CJK fonts for Chinese (Traditional/Simplified), Korean and Japanese languages (see Wikipedia page [https://en.wikipedia.org/wiki/Han_unification]), which is currently not implemented in a correct manner. [Bugs on Navball: Error locations are on the Navball] English Error: translation missing for "Full Control" and attached texts. Your Language Correction: 完全控制 (or "完整控制") 有控制单元且已接入通信网络。所有控制功能都可用。 Screenshot: English Error: translation missing for "Heading Dial". Your Language Correction: 航向仪 Screenshot: English Error: translation missing for "Navball". Your Language Correction: 导航球 Screenshot: English Error: translation error for SAS direction "Normal". Current translation means "alright". Your Language Correction: 法向 Screenshot: [Bugs on craft & map viewport] Translation error location: time warp tags English Error: translations are missing for popup tags when time warp speed is changed. Your Language Correction: N/A (haven't checked out what the English version should be) Screenshot: Translation error location: App Bar in the spacecraft view English Error: "App Bar" is incorrectly translated into "应用进度条" (application progress bar). "Kerbal manager" (or "Kerman manager"?) is incorrectly translated into "坎巴拉人经理" (Kerbals managing officer), "Action group manager" is incorrectly translated into "操作组合管理工具" (Operation combination managing tool). Your Language Correction: "App Bar" ->"小工具" "Kerbal manager"->"乘员管理" "Action group manager"->"动作组设置" Screenshot: Translation error location: "Skip countdown" button on launch English Error: "Skip countdown" is incorrectly translated into "跳过冷却时间" (skip cool down time) Your Language Correction: 跳过倒计时 Screenshot: [Bugs in VAB] Translation error location: Tooltip for catelog "UTILITY" in VAB English Error: "Utility" is translated into "效用" (effect), "parachutes and quality of life" is translated into "降落伞和生命质量" (parachute and (human) life quality). These are not completely wrong but are not satisfactory. Your Language Correction: (this one is more of a suggestion) "Utility"-> "装备" (as in KSP1) or "实用装备" (useful equipments) "parachutes and quality of life"->"降落伞与品质生活" (parachutes and quality of (daily) life) Screenshot: Translation error location: Catelog tag "Methalox" under fuel tanks in VAB English Error: "Methalox" is translated into "甲氧基" (methoxy), which means -OCH3 functional group in molecules. This translation could be seen very rarely in some recent news but it is not recommended as this is casual and can be misleading in chemistry. Your Language Correction: 液氧甲烷 Screenshot: Translation error location: Confirming message box when trying to delete a workspace in VAB English Error: The text in the popup window is untranslated. Translation for "Don't delete" button is missing. Your Language Correction: Text: 你确认要删除这个工作区吗？ Button: 不删除 Notes: What's the difference between "Cancel" and "Don't delete"? Screenshot: [Bugs in Settings menu] Translation error location: Texts for input settings English Error: All translations for functions and descriptions are missing. Your Language Correction: N/A. Please just finish them. Screenshot: Translation error location: Texts for graphic settings English Error: translations for environmental prop & prop density are missing. Your Language Correction: N/A (The original text description does not seem to be complete.) Screenshot: