Skip to content

[RAPPS-DB] Add Xash3D FWGS engine - #403

Open
PavelCheloveckov wants to merge 1 commit into
reactos:masterfrom
PavelCheloveckov:xash3d-engine
Open

PavelCheloveckov wants to merge 1 commit into
reactos:masterfrom
PavelCheloveckov:xash3d-engine

Conversation

@PavelCheloveckov

Copy link
Copy Markdown

Xash3D FWGS - Compatibility engine for Half-Life and old GoldSrc games
Tested on ReactOS 0.4.16 environment.

image

Comment thread xash3d.txt
@julenuri julenuri changed the title add Xash3D FWGS engine [RAPPS-DB] Add Xash3D FWGS engine Sep 22, 2026
@julenuri

Copy link
Copy Markdown
Collaborator

I have a deep internal debate to approve or not this PR.
In one side, it's an interesting project of an open sourced famous videogame engine. Moreover it is in active development and it's compatible with ReactOS. That's great.
But in the other side, I have doubts about to add it. You still need the assets and some files of the original and breaks the "out of the box experience" of the rapps-db base. You will click to download and you will lack files to make it run, and we won't provide them...
Correct me if I am wrong, because I haven't investigated or tested the game enough, but if the statement is like that... I highly doubt to approve it.

@PavelCheloveckov

Copy link
Copy Markdown
Author

I have a deep internal debate to approve or not this PR. In one side, it's an interesting project of an open sourced famous videogame engine. Moreover it is in active development and it's compatible with ReactOS. That's great. But in the other side, I have doubts about to add it. You still need the assets and some files of the original and breaks the "out of the box experience" of the rapps-db base. You will click to download and you will lack files to make it run, and we won't provide them... Correct me if I am wrong, because I haven't investigated or tested the game enough, but if the statement is like that... I highly doubt to approve it.

@julenuri Yes, it requires original game files to run, but that's a standard practice for all source ports (like Doom, Quake or OpenMW) in package managers. Users just copy their own game data into the installation folder. It's a great addition for the ReactOS gaming ecosystem. If needed, I can simply add a note to the description field that original game assets are required. What do you think?

@julenuri julenuri left a comment •

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@PavelCheloveckov If you have a way to script the game to self download the needed assets and it's legal to do it, I will approve it without any doubt. Actually I like this project.
Right now, you can't work with the package as is...
Also, it's important for us to provide a stable version that doesn't change the SHA1+SizeBytes.
There are dozens of open source engines: The Sims, Lego Island, The Simpsons hit and run, Mario 64, Windows's pinball... Etc.

@PavelCheloveckov

Copy link
Copy Markdown
Author

@PavelCheloveckov If you have a way to script the game to self download the needed assets and it's legal to do it, I will approve it without any doubt. Actually I like this project. Right now, you can't work with the package as is... Also, it's important for us to provide a stable version that doesn't change the SHA1+SizeBytes. There are dozens of open source engines: The Sims, Lego Island, The Simpsons hit and run, Mario 64, Windows's pinball... Etc.

@julenuri Xash3D is a portable application that doesn’t have a registry search mechanism for the installer, unlike OpenMW. As for the stable version: the last official release of Xash3D was in 2019. It’s quite outdated. The FWGS continuous build is currently the only viable and actively supported option for running the engine. So, to be honest, I don’t know what to do. Perhaps Xash3D will get an installer someday.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants