Allocating Space forever is a joke! No choice but to uninstall :(
HI!
I really wanted to try this game out, ive heard some good things from people who have been able to get it to run unfortunately im one of the many who ran into the brickwall of "allocating space" for hours im sorry but this is just too long to wait, 3 hours now ive waited and its only like 60% done yeesh i have like 90 gigs free on my HD, id rather DL the 4 gig file in under an hour as opposed to waiting 3 hours for nothing... and i made sure my firewall wasnt blocking the client i really wish you the best with the game, perhaps ill check it out later on when you have some way of making the game playable too bad :( |
![]() |
We can't help you if you don't give us information.
What OS are you using? What type of system? Perhaps also post a dxdiag in a spoiler tag so we can check the rest of your hardware and drivers. |
![]() |
I installed 1.0.3c this morning, around 11 hours ago or so. I played PoE for a good half an hour, maybe 45 minutes. Then I went to work. Now I came back, fired up the launcher, and I'm stuck in "Allocating Space..."
This has never happened to me before; not in the beta, not in live. You guys must have done something in the past 10 hours to make this happen, or the 1.0.3c patch broke the game for me after a reboot, as it worked fine without a reboot this morning. I'm on 32bit WinXP Pro SP3, GeForce 9800 GTX+, Intel Core 2 Duo E6600, 4G RAM. I've had no issues before, except for some .ogg crashes, but they've been gone since the game went live. Now, however, I can't get past the launcher. And, like I said, I installed 1.0.3c, the game worked fine, I shut down my PC, went to work, came back, started up my PC, the launcher hangs. Doesn't take a rocket scientist to figure out that either 1.0.3c broke it (after a reboot), or you've done something else to it during the past 10 hours. Anyways, maybe you'll fix it, maybe you won't, who knows. EDIT: Starting up the client straight from Client.exe gave me the loading screen, although now I'm stuck in that, and my HDD is screaming in agony. EDIT2: After a much longer than normal load, I'm now in the game. Like I said, straight from the Client.exe worked, the old shortcut didn't, tried twice. Maybe this'll help someone. Last edited by Sydänyö#0821 on Dec 19, 2013, 10:52:28 AM
|
![]() |
Hi there,
I'm sorry to hear there are some of you having issues with your patcher. For all of you whom are having issues with your patcher being stuck on 'Allocating space' Could you please first confirm that you are running the launcher as an administrator, you have added an exception to, or disabled your firewall, and disabled antivirus software? Kind regards, Simon GGG Support No longer works at GGG
| |
" FYI: Client.exe is just a proxy application that runs the PathOfExile.exe for you. There is no actual difference between running Client.exe manually and running PathOfExile.exe manually. Any change in behavior is merely coincidental. The biggest thing is to ensure you're running as administrator so it has access to patch the files (since the default install location is a protected folder, and most systems have UAC enabled preventing access). |
![]() |
" Well, whatever Client.exe is, and whatever PathOfExile.exe is, I don't know, but when I started PoE from the shortcut, I got the launcher and got stuck, and when I started Client.exe straight away without using the shortcut, I got straight into the game, passing the launcher. Knowing from a couple decades of experience how illogical and irrational Microsoft software can be, I just thought it might be worth mentioning. However, my friend told me he had gotten these Allocating Space -messages before quite often, and that they sometimes had taken minutes. Well, I had gotten them exactly never, which is why after Googling and finding threads like this one, I thought the game had broken somehow. I suppose I would've gotten into the game had I waited a bit longer, but meh. All I can say is there really should be some sort of "working" -indicator while it's "allocating space", as now there's nothing. It's working from the launcher again, though. Had an .ogg crash again, will have to see if they become a regular event. Also, I never install anything in the "default location"; my games are on a separate HDD from the OS HDD, and I always run my OS as the administrator, so that's not an issue. Still, I guess there's nothing wrong, but perhaps someone else reads these and gets their answer that way. |
![]() |
Let me explain a little bit about the patching process and maybe that will help you understand what's going on and why it might be causing problems.
The main "content" file (Content.ggpk) is just an archive format file. It is like a zip file or any other type of archive, except that it is exclusive to GGG in this case (and I don't think there is any internal compression). Think of this file like a mini-hard drive (filesystem). The actual patching process starts by checking if you already have this Content.ggpk file. If so, it does a "Checking Resources" where it calculates which files need to be changed (downloaded) and which ones don't. It marks the "Changed" files inside the Content.ggpk as "deleted" so it can free up that space. All this is done during "Checking Resources". Once it finishes with this, it knows which files need to be downloaded, and how large they are. This moves onto the "Allocating Space" phase where it attempts to "grow" the Content.ggpk file to make room for the downloaded files. It attempts to fit the downloaded files into the "free" space, but doesn't always accomplish it (and you might not always have room), so it has to add extra data to the end of the Content.ggpk file to make more room for the larger content. In most cases, this goes pretty quickly, and only allocates whatever is left for download. In the case of a HIGHLY fragmented Content.ggpk file, it can take longer (as it can on bad quality slow HDDs or on Linux). It then moves past the "Allocating Space" phase and begins downloading all the content and stuffing it into the available storage inside the Content.ggpk. So going back to the Allocating Space.. this can be slow for a LOT of reasons.. in most cases it is because the Content file is corrupted, you're not running as Administrator, you don't have permissions, you don't have space, or you're using a FAT32 filesystem. There are other fringe cases as I mentioned due to the hardware the drive is using, or Linux problems (which should mostly be fixed in later versions of Wine). I'd recommend, if you haven't done so recently, a Content.ggpk file defrag. There is actually an application you can find on these forums that will "defrag" the Content.ggpk file by going through the internal file list and copying the files out into a new file where they can be contiguous. This not only makes the files contiguous for better performance (less seeking and piecing together the files), but it also makes the Content.ggpk file smaller because it can remove all the waste space inside the file where the files don't quite meet the boundaries. The added benefit is it makes "Checking Resources" and "Allocating Space" usually go much more quickly. My Content.ggpk file is 4492937278 bytes ... yours should be somewhere around there (give or take). If it is MUCH larger, then you have a VERY fragmented Content file. Good luck. I hope that explains some stuff. |
![]() |
Well, happened again.
Started from shortcut, got the launcher, got Allocating Space again, let it be there for like 5 minutes, decided it's not worth it. Started from Client.exe, game started straight away. Shortcut is to \Path of Exile\Client.exe" -swa, not sure if the software audio switch is causing this. Starting from shortcut gives the launcher though, and starting straight from the .exe doesn't. How's that even possible? :) This was after a shutdown though, that might have something to do with it. Also, didn't run the ggpk defrag yet. Still, I'm finding it hilarious that the .exe itself starts up the game without a launcher and without the space allocation, while a shortcut to that very same .exe does the aforementioned. Last edited by Sydänyö#0821 on Dec 21, 2013, 1:15:13 PM
|
![]() |
are they both pointed to the same path? could be that the shortcut is configured wrong. right click the PathOfExile.exe and create a new shortcut. drag it to your desktop and try it instead.
|
![]() |
" Yeah the shortcut is the original one, except with the -swa switch, which I put there because I started getting .ogg crashes in beta a lot, most likely due to my Audigy 2. I can't play without it though, since my MB audio is completely worthless. The shortcut has no special configuration on it; no compatibility modes or anything like that, besides the -swa. The original shortcut points to Client.exe, but you're telling me to create a shortcut out of PathOfExile.exe, why is that? I can try of course, but it'll have to wait until the next time I hit this snag, as now I'm able to play, and that's what I'm going to do. |
![]() |