-
Notifications
You must be signed in to change notification settings - Fork 5
Home
Welcome to the Half-Life-Scripts wiki!
Click on the side panel to the right to learn how to write your own scripts.
-
unknown command bxt_append: Bunnymod XT is not injected. -
couldn't exec userconfig.cfg: The file isn't on the correct mod dir (valve, valve_WON or similar).
Mod directory is basically the directory the engine works with, launching hl.exe with -game <dir> parameter. Counter-Strike for example uses "cstrike".
While scripting (and running this game in general), the computer must be running stable at a given frame rate at all times. This is hard to maintain ideally, however certain measures can help to achieve such thing. Note for AMD/Intel graphics users: OpenGL support on AMD is noticeably bad compared to NVIDIA's, and Bunnymod XT relies on this backend. D3D support is no more on steampipe and software mode only supports up to 72 fps.
- If you experience a 60 fps cap, disable vsync using your graphics card's control panel.
- For Windows 7/Vista, you may set hl.exe priority to "High" using the Task Manager (CTRL+ESC+SHIFT).
- Using the console "~" set
r_dynamic 0andr_decals 1, the first command disables dynamic lighting such as explosions, flashlight and environment, the second will limit the amount of decals like blood and dust. - Launch the game at a lower resolution like 800x600
- If your Half-Life build dates from 2013 or later, you may enable "Low video quality" under video options.
- Certain Half-Life builds may run better on your hardware, you can try using latest from your steam account, GoldSource Package 2.1 (2009) link or Half-Life 2005 link
- If you're capable of setting thread affinity for Half-Life, you may notice improvements, somehow on more than capable machines the game can't run properly.
- Check if the game is using your dedicated GPU instead of CPU's integrated graphics with
gl_dump.
The memory manager allocates certain assets dynamically from the disk into memory such as speech, explosions, maps, etc and you may notice freezes when AI speak and or longer loading screens on a first encounter. It's possible to increase the memory size using -heapsize <value in kilobytes> but I personally noticed no real improvement, the default value is more than enough. The best thing you can do is to load a few save files through the game and play a bit so the game can load some of these assets.
Writing saves into disk may cause a long freeze up to 1 second on worst cases, one common fix is to give the folder writing permissions to the user(?). Steampipe builds are known for having inconsistent loading times from saves. Previous releases have consistent/predictable reload times. Running the game without steam seems to fix the issue.
When a mod is running such as cstrike, gearbox, valve_WON, etc, and a asset is required and not found, the engine looks for it under valve which is the default game, it increases lag since it's an extra task the engine must do. It's known to be awful on linux, level transitions can easily take 5 seconds instead of a few milliseconds. As for windows, it's quite noticeable on steampipe (engines builds from 2013 to present) but passable on older builds. If you seek for maximum performance, you may merge your mod into valve dir, preferably only valve_WON, the others may crash or malfunction.
Half-Life's client.dll between release and pre-steam (via WON patches) has cmd, and from Steam port circa 2003 up until 2013 has special, both work as a way of parsing stuff into the end of the command buffer from within a script, which allows looping scripts and receiving player inputs at the same time. Valve in 2013 decided to patch these altogether at engine level¹ so no cmd, cmd name, special nor _special can be used. That's why Bunnymod XT's bxt_append is used to cover any engine version or mod. ¹citation needed