atomGit
commented
1 year ago i should note that the current folder hierarchy is...
/source/cstrike/ /source/platform/ /source/valve/ /source/default.fmf /source/fteqw64
Closed atomGit closed 4 months ago
atomGit
commented
1 year ago i should note that the current folder hierarchy is...
/source/cstrike/ /source/platform/ /source/valve/ /source/default.fmf /source/fteqw64
eukara
commented
1 year ago FreeCS is meant to supplement FreeHL, as noted on the Releases page on this GitHub mirror. You place the 'cstrike' directory alongside the 'valve' directory.
You can then run fteqw inside the root directory of FreeHL where the default.fmf manifest is placed. That file is supposed to tell FTEQW how to launch FreeHL and will do so without additional command-line arguments. You can then proceed to select Counter-Strike from the 'Custom Game' menu.
atomGit
commented
1 year ago You place the 'cstrike' directory alongside the 'valve' directory.
right, so the directory structure outlined in my previous post is correct then
however when i use the Custom Game menu, there's an overlay/window that says "installing mod data..." but nothing happens (the progress remains at 0%) - i can load https://frag-net.com/ in a web browser, so i'm not sure what's wrong
eukara
commented
1 year ago I will try to reproduce this on a clean build.
For the time being you may need to pass over -game cstrike as command-line arguments, which should preserve the valve directory as specified in default.fmf - but if you see any missing assets you can ensure it's mounted by passing -game valve -game cstrike.
eukara
commented
1 year ago Fixed the menu bug here: https://github.com/VeraVisions/nuclide/commit/855daac7e7d18f1544d03b2a53d4d3be3fa9079f
Will build new binary archives soon.
atomGit
commented
1 year ago result is the same when passing -game valve -game cstrike - Custom Game menu still says "installing mod data..." and nothing happens
you posted just before i did apparently :)
i'll try the new build when it's ready - thanks
atomGit
commented
1 year ago if you want people to test, i think the install section of the readme.md needs to be better
i'd be happy to submit a step-by-step guide if you want, but i would need your help with some of it
Mailaender
commented
1 year ago To sum it up. Download:
This is how the folder structure has to look like:
FreeCS$ dir
conhistory.txt cstrike default.fmf fteqw-sdl2 installed.lst maptimes.txt platform valveYou need to run both valve/install_shareware_data.sh and cstrike/install_from_archiveorg.sh
This is how you start the game:
./fteqw-sdl2 -game valve -game cstrikei got if figured out on my own, but if you want people to test you might consider updating the readme.md
this is what i came up with if you care to use it...
eukara
commented
1 year ago I've built new release archives just now. Still trying to get everything streamlined and auto-pushed to GitHub - which I will get to but I am at this second pretty busy still. It'll also include the QuakeC sources now, to make things more portable and easier to tinker with.
Should I get rid of the (e.g.) valve-xx-xx-xx sub-directory within the zip archive? Asking for feedback as it may help people set it up easier and that may come off as annoying to deal with.
And @atomGit I would not recommend extracting any pk3 or pk4 archives. We need archives to help enforce purity and separate content with copyright on it. For example anything that starts with pak[...] will not be distributed to clients. I set up the archives very deliberately.
In theory, you grab FTEQW for your platform, put it into an extracted release archive of FreeHL where the default.fmf is, and run it.
The Configuration > Update menu can be used to get the same demo data as the install_shareware.sh script does. I've added multiple ways to add data because people have different needs and desires of obtaining the content.
atomGit
commented
1 year ago I would not recommend extracting any pk3 or pk4 archives.
the only way i could get CS to run was either by renaming the 'valve' folder, then renaming the 'cstrike' folder to 'valve', or by extracting the pk3 archives (and running fteqw64 -game cstrike) ... and if i only renamed 'cstrike' to 'valve', i believe there were missing textures (running fteqw64 -game valve -game cstrike loaded HL, not CS)
so again, i think the install part of the readme.md needs an overhaul - for example, if someone lands here and follows the instructions verbatim, they will not have installed FreeHL
it's also unclear what to do with Configuration > Update in game - in the readme you have "Run the engine and when in-game download the needed content", but i believe the needed content refereed to (particularly the 1.1.1.0 patch) is already packaged with FreeHL
eukara
commented
1 year ago FreeHL itself doesn't come with any content. It comes with a few scripts that assist in getting it (because there was a time in which the in-game updater did not exist). Wrangling the filesystem to make it 'work' although it won't connect to any game servers properly is not the right way to go about it either.
I did leave multiple ways of getting the content open because that seemed helpful, but if it causes confusion I may have to dictate more explicit means of obtaining and installing said content. I may already have to do that anyway for other reasons (sv_pure and all that) so let me just formally announce that everything is going to change.
Theuaredead
commented
1 year ago Hi @atomGit!
Unpacking the PK3/PK4s are not recommended to do to avoid conflicts with SV_Pure.
I followed your install guide to see if I could replicate your missing assets issue by skipping the steps in which you unpack the archives and I had found that the game was functioning as intended with the archives intact. I have the following questions:
@eukara and myself will look into streamlining the install process and readme for FreeCS and other Nuclide-based projects.
atomGit
commented
1 year ago @eukara - i'm not ignoring your questions, rather i'm starting all over and have gotten different results this time
still, a clear guide is needed because it is not clear what to do after one has extracted the archives - here's where i'm at...
do we run the install scripts in the cstrike and valve folders, or do we run fteqw and install updates from there, or are both necessary?
i got cs to work without using the .sh scripts which leaves me wondering if the content on archive.org is the same as that downloaded from fteqw
here's console output after running fteqw and installing the valve and cstrike updates from within fteqw and nothing more...
eukara
commented
1 year ago I can explain why the scripts work and the in-game updater no longer does. I've started making changes to the updates offered on the in-game updater the past couple of days to address confusion and complaints from here and on Matrix. The following things are going on right now:
pak0.pak that ships with the original, disc version of Half-Life. That's the way it will have to be. That's the only thing I can really support going forward.When this is complete, the readme file will be updated to reflect the exact requirements. There will be a disclaimer stating that while you can provide the data files via various different means, it is unreasonable to expect it to function as intended.
How one can help
Valve and Sierra offered many different types of downloads over the lifespan of the original Half-Life release. We have Half-Life: Day One, Half-Life: Uplink, the respective patch archives (without install checks) as well as dedicated server files. There's also games like Sven Coop on Steam, that offer some of the data files for free. They all can be used to construct enough data files to make FreeHL run.
As I stated earlier, @Theuaredead is currently researching some of the above so one can put together a CRC matching pak, but it still needs to be put together. One help would be finding means of extracting data files from installers without the requirement of Microsoft Windows or Wine. That way people can obtain the files without possibly breaking EULAs and to automate the content extraction process. That's out of the scope for this project. Even better would be to create a project akin to LibreQuake that will replace the data files with ones we can share freely and add exceptions for those pak files within purity checks.
An example set up
When the changes go through, one will be able to install the original 1.0.0.5 data from Half-Life in a read-only location.
On a Linux system, this may be in a place such as /usr/share/games/halflife:
eukara@m75q:/usr/share/games/halflife$ find . -type f -print | grep -v bshift | grep -v gearbox
./valve/xeno.wad
./valve/liquids.wad
./valve/settings.scr
./valve/decals.wad
./valve/music/track17.wav
./valve/music/track05.wav
./valve/music/track28.wav
./valve/music/track25.wav
./valve/music/track06.wav
./valve/music/track24.wav
./valve/music/track04.wav
./valve/music/track23.wav
./valve/music/track15.wav
./valve/music/track19.wav
./valve/music/track16.wav
./valve/music/track10.wav
./valve/music/track11.wav
./valve/music/track26.wav
./valve/music/track21.wav
./valve/music/track08.wav
./valve/music/track13.wav
./valve/music/track07.wav
./valve/music/track12.wav
./valve/music/track27.wav
./valve/music/track09.wav
./valve/music/track18.wav
./valve/music/track22.wav
./valve/music/track20.wav
./valve/music/track14.wav
./valve/music/track02.wav
./valve/music/track03.wav
./valve/server.cfg
./valve/spraypaint.wad
./valve/halflife.wad
./valve/pak0.pak
./valve/woncomm.lst
./valve/profile.lst
./valve/liblist.gam
./valve/mapcycle.txt
./valve/gfx.wad
./valve/media/launch_dnmenu1.wav
./valve/media/valve.avi
./valve/media/sierra.avi
./valve/media/launch_select2.wav
./valve/media/launch_glow1.wav
./valve/media/launch_select1.wav
./valve/media/logo.avi
./valve/media/launch_deny1.wav
./valve/media/launch_upmenu1.wav
./valve/media/launch_deny2.wav
./valve/cached.wad
./logos/camp1.bmp
./logos/gun1.bmp
./logos/8ball1.bmp
./logos/chuckskull.bmp
./logos/skull.bmp
./logos/lambda.bmp
./logos/splatt.bmp
./logos/chick1.bmp
./logos/smiley.bmp
./logos/v_1.bmp
./logos/tiki.bmp
./logos/devl1.bmp
./logos/andre.bmpAnd with only the static data in place, one can run their system version of FTEQW with the parameter -halflife and it should give a minimal menu in which to install a release of FreeHL.
And FreeHL will support this version as is. It will run and function as expected.
The patch to version 1.1.1.0 can be installed then through the updater, if one desires the extra content.
The install_from_cd.sh script will probably be updated to rip the content in such a manner that it will output the above, or discarded entirely. I do not know yet.
For Microsoft Windows users, they are most likely comfortable having it set-up like the original version. Therefore you'll install Half-Life (any disc version will do, including Game Of The Year), then merge FreeHL on top of it, and place a FTEQW binary in the same place as the hl.exe launcher.
TLDR: Users will have to provide a CRC matching pak0.pak from a disc version of Half-Life. I will no longer offer shareware/demo content, as it makes compatibility impossible and it will avoid a lot of other headaches along the way.
The Counter-Strike content should not be a cause for problems.
atomGit
commented
1 year ago wow, you have a lot on your plate!
I can explain why the scripts work and the in-game updater no longer does.
i used the update menus in fteqw to install the HL and cstrike stuff and that seemed to work, or at least i know something was downloaded (i saw the progress bar complete) and fteqw indicated the patches were installed (the indicators changed to green)
One help would be finding means of extracting data files from installers without the requirement of Microsoft Windows or Wine.
i use an arch-based OS and i remember spending quite a bit of time looking in the official and AUR repos for a tool that could extract those files and i never found anything
siredmar
commented
1 year ago I'm struggling to install freehl and freecs. I have an very old copy of half life and cs 1.5 on an external drive. I've read through the issue. I don't own a cd drive anymore - who needs CD these times anyway :) But i have my installed copy.
It would be great if anyone could tell me which files i need to copy from my installation to what paths in valve and cstrike directories. @eukara i could provide a install_from_installation.sh if this is in your interest.
eukara
commented
1 year ago If you want to do it the quick way, you can move the entire valve directory into the FreeHL valve folder as install.pk3dir and repeat the same with cstrike.
Depending on your operating system and the filesystem you're using, case sensitivity may be an issue. In which case you can pack the contents of your valve directory from Half-Life into a .zip archive (you can compress it too if you want) and place it inside of the FreeHL valve directory as install.pk3 for example.
atomGit
commented
4 months ago given the recent changes i think this can be closed ???
hi again
./fteqw64 -cstrikebut that doesn't work (i tried with the cstrike folder next to the valve folder, as well as within the valve folder)