source-sdk-2013
source-sdk-2013 copied to clipboard
ValveSoftware
Engine binaries are significantly out of date
Despite last being updated in 2015, the singleplayer branch code still requires 'upcoming' binaries on steam to run, which introduces a bit of trouble for the end user who wishes to play mods, and doesn't really make sense considering it's been "upcoming" for nearly 7 years.
The multiplayer code does work out of the box with the multiplayer base, however the particle files included with the base are of the wrong DMX encoding and need to be opened and saved using that engine's tools mode. As this is more of an annoyance to the development side of things and only really needs to be done once, the multiplayer branch seems to be the way to go for the time being, and even includes some improvements that aren't even in Alien Swarm.
With the recent additions to the rest of the Source 1 games to add the gamepad ui and vulkan support, this makes the SDK even further behind, and not really compatible with the Steamdeck.
Furthermore, with the announcement that engine code is no longer being licensed, it would be useful for the official SDK to be updated with the latest binaries and compatible code (if applicable). This would create a much more stable starting point for community updates to the SDK.
Another request I would have is to finally push the 'upcoming' branch's binaries into the 'public' branch on Steam so that players can start mods without having to manually select the branch.
For some amount of context in the event @kisak-valve (Apologies for the ping in advance) ever comes back around here, this quoted line refers to the Mapbase Source project found here: https://github.com/mapbase-source/source-sdk-2013 .
Singleplayer games built off of Mapbase Source will run off of whatever is the latest build version of Source SDK 2013 Singleplayer that is exposed to developers. In this case, it is the severely out of date Upcoming Beta Build version 2422905, compared to the latest Singleplayer versions of HL2, Episode One, and Episode Two all using Build version 5377866.
Pushing the Upcoming Beta Build version 2422905 to Stable would resolve a small amount of headache when trying to run mods using Mapbase, such as Entropy: Zero. However, it would be even more ideal if the Build version 5377866 code was pushed to the Singleplayer SDK instead, and also moved to here as well.
Another request I would have is to finally push the 'upcoming' branch's binaries into the 'public' branch on Steam so that players can start mods without having to manually select the branch.
For some amount of context in the event @kisak-valve (Apologies for the ping in advance) ever comes back around here, this quoted line refers to the Mapbase Source project found here: https://github.com/mapbase-source/source-sdk-2013 .
Singleplayer games built off of Mapbase Source will run off of whatever is the latest build version of Source SDK 2013 Singleplayer that is exposed to developers. In this case, it is the severely out of date Upcoming Beta Build version 2422905, compared to the latest Singleplayer versions of HL2, Episode One, and Episode Two all using Build version 5377866.
Pushing the Upcoming Beta Build version 2422905 to Stable would resolve a small amount of headache when trying to run mods using Mapbase, such as Entropy: Zero. However, it would be even more ideal if the Build version 5377866 code was pushed to the Singleplayer SDK instead, and also moved to here as well.
The issue isn't specific to Mapbase, it also applies to the stock code on this repo.
I understand that. However, Mapbase Source projects are a use case where this is most obvious.
I understand that. However, Mapbase Source projects are a use case where this is most obvious.
This inconvenience applies to the majority of Source 2013 mods today and has existed since long before Mapbase. Mapbase is just another mod which falls under that umbrella and has no reason to be associated with this in any way.
The regular Steam version of Entropy : Zero also does not use Mapbase, although I think it does technically use the Upcoming build.
yeah i've been messing with source since around 2015-16 and this has always been an issue
Updated the title and description to make it more clear, as #359 is already about a code update, and this is about binaries