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






For those crashing, I crashed simply because I wasn't fast enough, you need to press the elevator straight as you spawn in, jump on the machine gun and then console command +attack. It will seem like nothings happening however rest assured, you are firing and it will clear after a minute or so.
Don't even own a Deck to try it myself, but I'd assume that this map is definitely not "healthy" for the Deck, it's a very resource intensive map because it spawns a horde (15-20 zombies) every 2 seconds or so, that's a massive entity count and AI processing power needed.
It's weird that it gives you errors, but it might've been a slight config change by Valve to ensure L4D didn't kill Decks when commands would request far too much from the device?
PD: Runing on Intel I5 8-400f, RTX 1650 Super, 16gb(monochannel) and HDD
40k kills in about an hour. Also got Beat the Rush
I legitimately only found that it crashed after releasing the map due to comments, because it never happened to me, I'd grab the minigun instantly.
Other maps that I tried before I released this one were crashing due to command overload or game update incompatibilities, as all were inferior in zombie count and spawn speed. I made my own because no other was good and was crashing (Hence the, apparently false, advertisement).
As for hardware, unless you're using 12Gb or less of RAM, there should be no motive for crashing due to slow load times or something of the sorts. I released this using a i5 6600k, RX480, 16Gb and a 5600RPM HDD. Anything post 2015 should beat my setup back in the days easily.