![]() ![]() I have the right model file and such, but I think it's because the cleansuit scientist entity is not within my current DLL file, which is a copy of the DLL for the Half-Life base game. Instead, I found this thing called "Half-Life master":īut yeah, I just used the FGD for Opposing Force and tried to experiment by putting in the map a cleansuit scientist. Originally posted by seansdibbun:Not with Notepad, no. As for the code for Opposing Force's entities, they can also be acquired somewhere else in GitHub.īut yeah, I just used the FGD for Opposing Force and tried to experiment by putting in the map a cleansuit scientist. Looking at the inner workings of hl.dll, or in the project files as hl_dll.vcxproj, the DLL is the heart, mind, and soul of the game itself and any mods made. ![]() They are Microsoft Visual project files, which I assume can be converted into DLL. I'm guessing some modders use it to create their own DLLs for their Half-Life mods. Instead, I found this thing called "Half-Life master": After that it reverts to the default behavior.Not with Notepad, no. peers at the time, Half-Life used scripted sequences, which ranged from. I tried editing the config.cfg and creating a macro of: bind z "invnext +attack", to switch to and select the next weapon, but it only works the first time after loading the game. combat tasks and puzzle solving to advance through the game. I don't know how to make it auto switch to the next weapon. When switching weapons without the hud, you need to press the button for the next or previous weapon and then immediately click "fire" to select it, otherwise it can get confusing exactly which weapon you've selected. In half life, when you switch weapons it shows the selected weapon on the hud and then requires you click "fire" to select it. Note about disabling the hud in Half-Life: ![]() The simple answer is: Because I am the hudfreegamer. ![]() Someone asked earlier why I want to disable the hud. It doesn't appear to cause any other problems. Note: When replacing that client.dll file, you will notice that the hud changes color to the default yellow hud color of Half-Life. Now run the game and select Custom Game from the main menu, Select Blue Shift and you can now play Blue Shift with Xash3d in widescreen and the console command to disable the hud will work (hud_draw 0). Rename the old client.dll first in case you want to restore it. then Download Xash Blue Shift or search for Xash Opposing Force on YouTube Have Fun deleted 3 yr. To disable the hud in Blue Shift with Xash3d, you need to copy the Half-Life-Xash3d/valve/cl_dlls/client.dll (also in the extra files needed from the Xash3d install)Ĭopy that client.dll to your Half-Life-Xash3d/bshift/cl_dlls/ directory. Geht the Blue Shift or Opposing force Data to xash and the valve folder too. This causes a bug where the console command to disable the hud no longer works. Now run the hl.exe file in the Xash3d directory to run the game and select from the main menu "custom game". Copy the bshift directory to your Xash3d-half-life directory. Next, go to your Blue Shift installation directory. Run either one of those and select your Blue Shift installation directory. Next, download either one of these two files, which will convert Blue Shift into a mod that can be used with the previous Half-Life Xash3d version (I used the second one): The previous solution I found to run Half-Life in widescreen did not work properly for Blue Shift.įirst, install Xash3d and Half-life using the previous instructions in my earlier post. ![]()
0 Comments
Leave a Reply. |