-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Guide] How to succesfully compile and run on windows. #356
Comments
But it can be succesfully built by VS2022, why we need VS2017? |
from what i've seen, vs2022 gives errors. did you really manage a succesfull vs2022 build? if yes, please share the details. |
|
that's very interesting... could it be because i was using vs 2022 proffesional? there were other people with the same problem - not being able to build with vs 2022. i've also seen a lot more warnings in your build. |
If my memory serves me, that warnings were even with VS2017 compilers |
Don't think that different types of VS provides different compilers |
I have compiled CSS dedicated_server for Windows 32-bit, but I am unable to use metamod and sourcemod properly.SdkHooks and CStools cannot load properly, and many plugins cannot be used. Can you provide assistance in fixing this issue? |
oh yeah, you might need to use an older version of these. |
after i fixed my path and added a shit-ton of arguments it works? |
updated it a bit |
Any idea on how to build a solution file? (nevermind, you need to use |
what? we use waf. vpc got replaced years ago. |
Nope. It generates solution for the last version of VS on your PC |
|
as much as I would like to admit waf is better, unfortunately it doesn't have intellisense |
IntelliSense is Visual Studio, not |
After successfully building the project in Windows, is the hl2 directory the root directory? For example, my build directory is C:\Users\Administrator\source-engine, so the hl2 you mentioned is in the directory C:\Users\Administrator\source-engine\hl2, right? Then put the steam css file C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Source directly into C:\Users\Administrator\source-engine\hl2. If you encounter files with the same name, don't choose to replace them, right? I tried it and it kept giving me an error. |
@WZL203 Let me clarify it. You build the entire engine. What you should do is grab |
Looks like Can you check if there's everything required is in your build? |
I did copy everything in hl2. Maybe I need a different version of the game? But this engine is pretty new, I would expect it to work with the recent game, since there weren't any major updates before the 20th anniversary (and everything else in-game seems to work well). |
This issue no longer appears to exist. Does anyone know how to do what this is referring to? |
In HL2:DM, there was a black screen in main menu. |
Pre-20th anniversary steam version is required.
False. There's a rendering issues with new assets |
Figured out my issue from before, it's because I didn't copy the The same procedure works on Raspberry OS perfectly, you just have to figure out a couple dependencies to |
@FlamedDogo99 i am the original creator of that Issue(tm) but it was hl2 |
This guide will tell you how to prepare, compile and run build game.
a. clone with git: git clone https://github.com/nillerusr/source-engine.git --recursive
b. clone with github desktop.
waf.bat configure -T release --prefix=hl2 --build-games=hl2 --disable-warns
waf.bat build -p -v
waf.bat install
OTHER IMPORTANT THINGS
hl1 = Half-Life 1: Source
hl2 = Half-Life 2 // Default - This will be selected if you don't specify a game
episodic = Half-Life 2 Episode 1
ep2 = Half-Life 2 Episode 2 // Do not build for ep2, use episodic instead.
hl2mp = Half-Life 2: Deathmatch
dod = Day of Defeat
cstrike = Counter-Strike: Source
portal = Portal
The text was updated successfully, but these errors were encountered: