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








Out of curiosity, have you played The Passing yet? For some people an issue originated from the fact that I used infected populations from the Passing and those model textures weren't precached for the people that had not yet played the Passing. I thought I had removed most of those infected populations in the newest version but if thats the issue it could very well be that I missed deleting a few of them.
Also typical things to check if you haven't done so yet: doing a file verification in L4D2's property settings in your steam library, making sure its not a conflict with another addon by removing all other addons temporarily, and updating your graphics drivers.
GeForceGT630 (but upgrading to GTX1050 soon)
Intel i5 2500
CPU: 3.30GHz
running at a solid 7.96 RAM
as I said, I've already tried disabling addons and lowered my graphics to the lowest settings but it still crashes on the bridge
"too many indices for Index Buffer. tell a programmer (35823>32768)"
maybe too much cars on the bridge, or too much infected spawned in.
either way I may have our answer
Just about any type of resource in the map can fill up indices, such as geometry, textures, scripts, you name it. It's the type of error you would typically get when too many mods are used in conjunction with one another (custom player models, weapon models, and effects are common culprits), and it tends to affect people with older CPUs. (Your six year old i5-2500 processor model may be a contributing factor there.)
That being said, if you've disabled all your other mods and still get that error, that means that there might be something on the map using up just a little too many indices with the map, enough for people with older CPUs to get the error but not those with newer CPUs. Let me know if the error persists after multiple tries, feel free to add me on steam, and I might be able to troubleshoot it further.