|
|
| (33 intermediate revisions by 18 users not shown) |
| Line 1: |
Line 1: |
| {{stub}}
| | #redirect [[SteamPipe]] |
| '''SteamPipe''' is Steam's new content distribution system. It changes the way games (including dedicated servers) are downloaded, updated and stored. More information can be found on the [https://support.steampowered.com/kb_article.php?ref=7388-QPFN-2491 Steam Support page].
| |
| | |
| == Benefits ==
| |
| | |
| === Players ===
| |
| | |
| The benefits to players are:
| |
| *Faster and smoother downloads
| |
| *Faster game boot times and map load times
| |
| *Easier distribution, installation, and management of mods
| |
| *Smoother dedicated server distribution and update rollover
| |
| | |
| === Server administrators ===
| |
| | |
| Instead of a proprietary delivery protocol, SteamPipe uses HTTP, which allows datacenters hosting multiple servers to set up a caching HTTP proxy, necessitating only a single download of an update from Valve's servers.
| |
| | |
| === Game developers ===
| |
| | |
| Game developers using SteamPipe can [http://garry.tv/2012/08/16/approved-updates/ issue updates themselves]; the previous system required manual intervention by Valve when an update was to be published.
| |
| | |
| == Changes ==
| |
| | |
| * Downloads are performed using HTTP instead of a proprietary protocol.
| |
| * Data files are no longer placed into [[GCF]]s but directly into the file system.
| |
| ** To counteract the performance issues with accessing many tiny files (the reason why GCFs were used in the first place), [[Source]] games distributed via SteamPipe store their assets in [[VPK]] archives.
| |
| * Data generated before/during gameplay is no longer stored in user-specific subdirectories of ''SteamApps''; instead, the ''common'' subfolder is used.
| |
| * Dedicated servers are no longer updated using [[HLDSUpdateTool]] (known as <tt>steam</tt> on Linux) but using [[SteamCMD]] (a stripped-down version of the full Steam client).
| |