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








The game doesn't freeze indefinitely. Depending on how long I play the map (or lets say, how many balls I pop) It takes longer for the game to become responsive again, upon exiting the map.
The experience of this will most likely differ from hardware to hardware.
my rig:
CPU: AMD Ryzen 7 5700G (8/16 cores @ 2.6GHz)
GPU: GeForce GTX 1650 (4GB)
RAM: 32 GB DDR4
OS/Client: Linux
Sounds to me like the instances of popped balls are not properly destroyed. You either need to make sure they are destroyed or maybe handle ball popping different. I.e. don't destroy the instance but rather hide it, or move it.
I can recreate it on my end but sadly I worry this might be an issue within the engine itself. looking at edicts after 30 minutes of playing shows no left overs. ball destruction is handled entirely by the game. though i doubt that poped balls aren't cleared properly since if that was the case you could see ram usage steadily go up which it doesn't do. atleast not on my end.