Jacksongol

First check the game files in Steam (if you haven't already) by right-clicking on War Thunder in the Steam game library -> go to properties -> local files -> verify integrity of game cache as a 'workaround' you may be able to start the game by running the launcher.exe directly in the War Thunder game folder (you can open the folder in the above.

reader comments

If you play games on PC, where God intended them to be played, chances are you’ve got Steam installed. Since its troubled launch in 2003, Valve’s publishing platform has gone from a thing we had to grudgingly put up with in order to play Half Life 2 to the most popular digital game distribution tool on the planet. Most of us—me included—interact with it pretty much daily.

Left 4 Dead Demo Includes Linux Steam Client. The demo for L4D was removed from Steam the day the full game launched. CCI Power 6/40: one board, a megabyte of. Steam client or server issues. /r/Steam Weekly Community Support Thread. My guess is that your drive is full. When I replaced the win64 file in Starbound folder with the download_depot win64 file and altered the appmanifest acf file to keep Starbound from being updated by Steam, the Starbound exe in the folder won't be launched by Steam. When you subscribe to a mod through the Steam client (make sure it's through the Steam client itself), you.

But as game distribution was shifting from physical to digital, ISPs also began implementing data caps—usually under the guise of “network management” (though anyone who thinks caps aren’t a pure revenue play should send me an e-mail, because I’ve got a bridge to sell you, cheap!). Steam is fast, Steam is easy, and Steam is ubiquitous—but if you’ve just rebuilt a PC or reinstalled an OS and you need to reinstall your games, Steam will obligingly help you put a giant dent in your cap—very quickly.

But there’s an alternative to having to re-download all your Steam games from the Internet: you can set up a local Steam caching server, so that once you download something, you’ve got it on your LAN instead of having to reach for it across the net and incur usage fees.

How this works

The idea is simple: when your computer’s Steam client needs to install or update an application, it contacts one or more of Valve’s SteamPipe content distribution servers. Valve has partnered with ISPs across the world so that most folks have SteamPipe content servers near them (“near” in terms of both physical distance and also network hops). This saves ISPs money on transit and peering.

SteamPipe is used to deliver what the client needs, be it a whole game or just an update, in roughly megabyte-size chunks. (Chunking like this allows developers to publish updates without having to push a whole new game package—they just invalidate old chunks and upload new ones.) As Valve points out on the SteamPipe developer community page, SteamPipe uses plain ol’ HTTP rather than a proprietary protocol. And that gives us the opportunity to stick our fingers into the process and mess with it.

Recall for a moment how a caching Web server works: a user hits a page, and the server checks its cache to see if the cache has what the user needs in it. If the cache does, the server delivers those objects directly. If not, the caching Web server forwards the request to a backend, retrieves whatever the user needs from that backend, and delivers it. Then the Web server stores the objects in cache for next time so it doesn’t have to bother the backend again.

What if we turn that process sort of inside out? What if we set up a caching Web server like Nginx locally? What if, instead of using the server as a reverse-proxy to cache responses for incoming requests from the Internet for a particular Web site... we use it as forward proxy (or just a regular proxy, I suppose) and cache the responses to our outgoing requests for Steam content?

It sounds like we’re inverting what a reverse-proxying Web server is supposed to be for and using it like a normal Squid-style proxy—but as it turns out, this actually works great.

Did I say “great”? I meant “almost great.” There’s another piece of the puzzle. We need to screw around a bit with DNS for this to actually work. Steam doesn’t have a “check my local server first” option to make this caching thing an automated process, so we’ll need to add DNS entries to fake Steam into thinking that its SteamPipe content server actually is the local cache server we’re going to build.

All roads lead to Rome, but this is our road

Fortunately, none of this is actually as complicated as it sounds—and, as we’ll see, there are pre-built Docker images to do all of this for you, if you don’t want to get your hands dirty.

But before we proceed any farther, we need to go over exactly what you need for your local Steam cache server. As with so many projects, you can take a huge variety of paths to get to the destination; you can do this with nothing more than Windows and your gaming PC, or you can use a Windows or Linux virtual machine, or you can use an actual physical Windows or Linux server. You can keep your Steam cache on local disk or on a network share. You can use whatever application you want, provided it can forward and cache HTTP requests.

For this guide, we’re going to look at two specific configurations: Linux (specifically Ubuntu 16.04 LTS Server) with Docker for the easy way; and Linux (again, Ubuntu 16.04 LTS Server) on bare metal for the DIY way. Both configurations will store the actual cache depot on a network share—I set my depot up using iSCSI for a number of reasons external to this guide, but there’s nothing wrong with NFS (or even Samba, I guess). If you have a few terabytes of disk space, you can also put your depot local on your server. It’s all up to you and what works for you, but this guide will talk about putting your depot on a NAS and accessing it via a mounted NFS share.

The star of our show in both configurations is going to be Nginx, a fast and powerful Web server that runs a significant chunk of the World Wide Web (it’s second in popularity only to Apache, the Microsoft Word of Web servers). Nginx’s ability to maintain its own local content cache from an upstream source is what makes this entire process work. If Nginx sounds familiar to you, it’s because we’ve written about using it at great length with our Web Served series (and, yes, those articles are in dire need of update—that’s on my 2017 to-do list!).

Other tools could be employed here, too—most notably, a standard proxy server like Squid. And, in fact, guides are out there that tell you how to configure Squid for just that. But we’re going with Nginx primarily because of all the documentation out there to do it this way, and also because there are Docker images of working configurations we can pick apart and use.

For the DNS portion, you can fall back on old-fashioned host file editing or more modern (and flexible) actual DNS configuration. If you have a local instance of dnsmasq or bind running on your LAN—say, on your NAT router or something—that’s where you’ll be working. If this sounds scary or complicated, fear not—the “easy way” method we’re about to describe will take care of everything for you. In the DIY section, we’ll be setting up bind and using that.

Let's say I have a game bought on retail/other digital download and installed on my hard drive. I buy the same game (or a minor variant of it, say the GOTY edition) on Steam. It should be possible to use the existing installation to avoid the generally big downloads. This is very useful as it saves both bandwidth and time.

Previously, as far as I understood, Steam downloaded the game files directly to steamsteamappscommon<game_name>. Since this folder would be created on starting the download, pausing and closing steam, copying the game files to this folder and then validating game files would make Steam absorb as much as possible and just download the missing files.

Currently, Steam downloads the files to steamsteamappsdownloading<game_id> and then moves them over to the aforementioned folder once the download finishes. So first of all, what the final folder would be is not clear. So what would be the correct way of doing the same thing, that is, make steam use as much of the existing files as possible? Should the files be copied to downloading*, or should I figure out the actual folder (say via googling) and copy the files to steamappscommon*?

More specifically, I had a retail copy of Arkham City installed and I just bought the GOTY version on Steam. Now I tried both of the above things, in either case, the validating does not seem to do anything. Assuming I have the correct folder name steamappscommonBatman Arkham City GOTY, according to this, if I copy the files there, Steam seems to just continue with its 17GB download. If I copy it to steamappsdownloading200260 then the download keeps stopping every few seconds with 'Disk Write Error' after modifying 1 or 2 files, and I have to keep hitting resume.

6 Answers

I think the following is the correct way to currently do what I wanted:

1. Ensure that Steam thinks the game is not installed. Close Steam just to be sure.
2. Copy the game files to SteamAppscommon<game_name>, where <game_name> is to be found out via googling/equivalent. In my specific instance, this was Batman Arkham City GOTY.
3. Launch Steam and install the game. The installation will go through a 'Discovering existing files for _' stage.
4. Watch and wait as it downloads only the missing parts.

I still have to download 9.8 GB though (instead of 17) in my specific case.

Actually you can bind a steam app folder simply from the steam gui!

view -> settings -> download -> steam library folder

and then choose your shared steam folder. Also now steam let you choose where download games; i hove NOT tested cross-gaming (using the same folder on windows and linux), but just relinked my folder (somehow steam lost track of my external HDD) and everythings work fine.

Tested having game in different HDD/partition and works fine. If you Start up steam without external HDD, a reboot of steam is needed to let it 'see' the folder

This solution should work if the game is displaying in the library folder in Steam with the words 'update required' written next to it but the game won't recognize the existing game files on the hard drive.

-Pay close attention to these steps!!!-

1. -Important- First go to your games folder either in SteamSteamAppsCommon or whatever folder you've already copied the game to and make a copy of the game to a different destination on the hard drive other than in the Steam folder or copy it to a external hard drive as a back up. The next step will delete the game folder in the SteamSteamAppsCommon directory. So this is why this is important.

2. Go to your Steam library and right click on the game that is causing the issue and then click 'delete local content'. This will delete the game file from the Steam library and from the Steam directory on the hard drive.

3. Now copy the games folder back into the common folder located in SteamSteamAppsCommon from the location we had copied it to before in step #1

4. Finally open Steam, the game title should now be grey-ed out in the Steam library and when you right click on it, it should say 'install game...' click on install game and choose the games directory for installation (usually the the default one) is the one to choose, click next, Agree... now it should say discovering existing files... (this is a good thing) and click finish. Now it should work.

If so congratulations! if not idfk what will work but this seemed to work for me. If it did work for you please leave a comment so i can be sure this is a solution that others can use.

Issue solved:

Hope this helps you guys.

1. Go to View > Settings > Downloads
2. On STEAM LIBRARY FOLDERS add the folder on the unit where you want to have your games (must be empty, Steam will prompt if not) and close.
3. Go to that folder and you should have the following structure:
   • new_folder>
   • • SteamApps> <- create this folder! (no '>'...)
   • • common> <--- create this folder! (where games go)
   • • downloading> <--- won't exist unless are downloading something
   • • appmanifest_xxx.acf <--- copy all the appmanifest_xxx.acf files you have
4. Copy all the games folders from your old .../common/ folder to the new location (into the new .../common/ folder you just created).

At this point games will not work. This will make your Steam recognize your games...

5. Copy all appmanifest_xxx.acf files from from the old .../steamapps/ folder into the new one. THIS IS WHAT MAKES STEAM SEE THE GAMES. For each game there is one manifest.

6. Play the game.

Full Steam Band

Regards,

efezeta12

Tried everything and this worked:

Full Steam Durham Nc

Step 1: go to settings/backup or restore | game on a computer that has the game ---> choose game to backup and where to back it up to.Step 2: go to settings/backup or restore game ---> choose file to restore on the computer that you want it on. Click install and you are all ready to go.

If you cant understand what I have said just watch the youtube video

Hope it helps

Rose With Full Steam Drawings

protected by Frank♦Mar 27 '15 at 16:45

Full Steam Band Maryland

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?

Full Steam David Gray

Not the answer you're looking for? Browse other questions tagged steam or ask your own question.