Launching tools directly: Difference between revisions
Jump to navigation
Jump to search
m (added "s" to "Window") |
(badly moved multipage) |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{ | {{LanguageBar}} | ||
Most SDK tools, including {{hammer|1}} and its compilers, {{hlmv|1}}, and {{hlfaceposer|1|nt=0}} do not work properly when run by double clicking on them as an EXE. A quick way to solve this issue is to create a shortcut or a batch file that runs the EXE with the parameter <code>-game ../yourmod</code>. Depending on the game, <code>-nop4</code> may also be required to prevent crashes. | |||
Furthermore, since the {{src13|1}} and with the {{src13|1|nt=0}}, the Source SDK launcher no longer works. In order to launch these tools for that branch, double click on the .BAT file on the {{code|(game directory)\bin}} folder instead. | |||
[[Category:Source SDK FAQ]] | [[Category:Source SDK FAQ]] | ||
[[Category:Tools]] | [[Category:Tools]] | ||
Latest revision as of 05:31, 14 July 2024
Most SDK tools, including Hammer and its compilers, HLMV, and Faceposer do not work properly when run by double clicking on them as an EXE. A quick way to solve this issue is to create a shortcut or a batch file that runs the EXE with the parameter -game ../yourmod. Depending on the game, -nop4 may also be required to prevent crashes.
Furthermore, since the Source 2013 and with the Source SDK Base 2013, the Source SDK launcher no longer works. In order to launch these tools for that branch, double click on the .BAT file on the (game directory)\bin folder instead.