安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
讨论规则及指引
举报此帖
/astronautjonesy.[extension] while they're supposed to be at -/SourceFilmmaker/game/
/[folder]/models/AstronautJonesy.[extension], or the other way around of that.
Garry's Mod reads a model from where the model files are, so it's not an issue for Garry's Mod, but Source Filmmaker can only properly read a model if its model files are where the MDL file says that they must be.
You shouldn't put custom content into pre-existing folders in Source Filmmaker, especially not "usermod" as it's an "important" folder for Source Filmmaker. If you mess up something in there, it may be hard to fix (occasionally to the point of basically requiring Source Filmmaker to be re-installed), and even if you don't, you can still cause problems by doing that.
Instead, right-click Source Filmmaker in your Steam library (in the "Software" or "Installed" categories), and choose "Properties" > "Local Files" > "Browse Local Files...". This will open a File Explorer window in -/SourceFilmmaker/.
Now enter the "game" folder and make a new folder here, named whatever you want (for example "customstuff").
Inside of the folder that you just made (for example inside of -/SourceFilmmaker/game/customstuff/), make folders called "maps", "materials", "models", "particles", and/or "sound". These folders may hold custom content.
Once you've put custom content inside of those folders that you just made, right-click Source Filmmaker in your Steam library again, choose "Launch SDK", click "Edit Search Paths For Selected Mod", and enable the first custom folder that you made while following these instructions (for example "customstuff").
You may optionally move it around in the search path list, such as if it's supposed to override Team Fortress 2 content or such. If a file exists within two different search paths, the top-most search path in the list will be the search path that the file will be loaded from.
I personally suggest having a separate such folder for each franchise or such (for example one for Super Mario stuff, one for Sonic the Hedgehog stuff, one for Overwatch stuff, et cetera). This way, you can mostly disable stuff that you're not currently using, which can be helpful if Source Filmmaker starts crashing due to indexing too many assets.