安装 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(越南语)
Українська(乌克兰语)
报告翻译问题






Hehehehehehe!
but it's probably a weird side effect of my math work.
(I'll still fix it of course)
https://discord.gg/wrXqJcwS
You can find instructions on the Discord about recovering an older save file.
You should report this on the Discord server or the Github issue tracker.
Each time i play and complete a mission it wont save the next time i go on teardown
Mods don't have access to the entire savefile. Only their own little sector.
Did you do anything recently? Such as reinstall the game or such.
At 50 this is still relatively manageable at 2.500 rays.
Going to 60 already raises this to 3.600.
At a 100 you are shooting 10.000 rays each frame.
I wish I could improve performance. But currently this mod is only possible with such a crude technique.
But I will see if lowering the render distance gives some improvement.
If we get access to the framebuffer at some point, performance should be not a problem because I can just go through the screen data without any raycasts.