安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
basically the calendar and simulation speed stop lining up. more days pass , than you have effectively simulated in TC. this can be tested by setting a waypoint , traveling at a certain speed, and calculating how long it should take to travel. by the end of the trip , a different number of days will have passed than should have.
there were instances back in the B131 days where this could get as low as 0.3 simulation rate. but it often would hover at 0.5 during max Time compression. hence the reduced values. while optimizations have been done , It would be a process to figure out if this is needed.
Otherwise a patch mod (anyone can make this) to revert the values to vanilla
Revert game back to 2024.1
This mod doesn't change logic of how the game works neutrality rules are the same as vanilla
Time compression values could be returned to vanilla with a datasheet patch, applied after UBE in mod load order, I have doubts that the game can still handle the increased volume of data at the original TC values. but some machines may fare better than others. I believe this is written in General.xlsx/Settings
If not, is this something that could be handled by a manual edit of the files on the user side?