安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
讨论规则及指引
0 
举报此帖
An FGD file is basically a recipe book for entities, it tells hammer "this is entity is called this, has these keyvalues that can be set, and these are the inputs and outputs it has".
FGD doesn't determine assets, that's all taken care of by the gameinfo.txt for the game/mod.
You can open up an fgd file in a text editor like notepad++ and take a look at it if you want to see what entities it adds. The halflife2.fgd for example includes all the information for hl2 entities like npc_combine_s and npc_citizen. If you're not going to be using any HL2 entities then you don't need to use it and just using the CSS one should be fine.
The only reason I can think of that would crash hammer from an fgd is if there was for some reason an entity conflict between two fgds and even then it should just revert to mount order.
Setup image[i.gyazo.com] (I renamed the old halflife2.fgd as DONTUSE)
Hammer message[i.gyazo.com]
Also, thank you for explaining fgd files for me, they make a lot more sense now.