安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
3 
举报此帖
(Make sure you don't include any spaces at the end of the commands)
This should tell you where GMod is loading this model and its material from. It's possible that the default game content is being overridden by another faulty addon.
Wow, that should have been patched a long time ago, i wonder how the devs haven't even noticed it yet...
error vertex file for 'props_c17/door01_left.mdl' checksum 972034250 should be 145318345
Oh yeah, i also had that error too some time ago...
how did you fix it? quote: some time ago :endquote
it happens all the time that i've gone in but thanks for the help. the lag is no too bad and its not a major issue
Preventing unseen objects from rendering is difficult to pull off effectively in a large, open map running on this engine. The areas where that form of optimization would work (e.g. behind a hill or inside a tunnel) are greatly outnumbered by the areas where the player can see pretty much everything. For that reason, I decided to focus on optimizing for that worst case scenario using LODs and fade distances.
I'm aiming for better performance in my upcoming map. Once that's finished, I might look into updating gm_fork with similar techniques. For now, I recommend using multicore rendering as described in this guide.