From what I can see in my transfer window the launcher locks up while getting the patch manifest. So basicly he freezes while still getting the file which tells him what he should patch.
I opening the "Transfers" Window (ctrl+X) and it showed I was caught on the manifest as well, but by having the transfers window open it seemed to work it self out.
Same issue - at first the patching just froze at about 41%. Had to force close the launcher and now each and every attempt to patch Tribble just freezes it completely.
Deleting shaderCache.hogg file didn't help. The launcher just freezes and doesn't even attempt to re-download it.
I tried forced verify, deleting the contents of the Playtest/cache and even disabling on-demand patching and waiting for it to do a long download, each time it would get to a certain point then lock up. The only way I could resolve it was to overwirite the playtest folder with a copy of the contents of my live folder and then log in and let tribble patch it over again and this time it patched successfully.
If something is not broken, don't fix it, if it is broken, don't leave it broken.
Had these problems with it stopping after stopping at a certain point and the Launcher freezing up anytime after that while trying to patch Tribble, but deleting the playtest folder and reinstalling it worked. Only had to download about 1 Gig worth instead of the 8.5 Gigs. Might not work for everyone.
The only way I could resolve it was to overwirite the playtest folder with a copy of the contents of my live folder and then log in and let tribble patch it over again and this time it patched successfully.
^^^^^^^^^^^^^^^^^
This here worked for me and is what I would recommend doing.
Nitpicking is a time-honored tradition of science fiction. Asking your readers not to worry about the "little things" is like asking a dog not to sniff at people's crotches. If there's something that appears to violate natural laws, then you can expect someone's going to point it out. That's just the way things are.
Decided that since the manifest was causing a problem I would delete it. Found it in the folder "Playtest/.patch", and wiped the contents of the folder just to be sure I got it. and then ran the patcher again and it completed in seconds.
Seems the manifest is getting corrupted somehow and removing it fixed my issue.
CPU and Memory usage did spike while it was patching though. CPU usage shot to 25% and memory usage shot to over 500,000k for awhile before settling down.
Just compared the contents of the folder that I deleted with the patched contents and found there is a file missing in the patched version. A file named "headers.hogg" was not downloaded again. Ah, the file was generated when I started logging into the game. Although the file "patch_trivia.txt.bak" was deleted when the "headers.hogg" file was generated.
EDIT: the .bak file was generated again while it was loading so seems that should be there.
People might want to try wiping the contents of the ".patch" folder and see if that works. Its a fairly small folder and should redownload quickly.
Tried clearing my .patch folder, which got the launcher to download about 15MB before locking up again. I think I'm just going to give up and wait for another patch.
Tried clearing my .patch folder, which got the launcher to download about 15MB before locking up again. I think I'm just going to give up and wait for another patch.
Bah, was hoping I had found the issue. Since a full copy will wipe those files as well and no one reported trying that before and it had worked for me.
I had done a forced verify before that and had it freeze as soon as it got to the patching. You can try the wiping/overwrite of the folder method. It should pull most of the data from the live version and just download the 1gb or so of new stuff.
It's dead JIM! You would think this would be priority fix issue number one, but it does not look like anybody have any rush to get this fixed.Well, there's always tomorrow
interestingly same thing happened on Neverwinter for me. seems to be more widespread than just sto
Was curious so I checked. Same thing happened patching Owlbear. I wiped everything in the ".patch" folder for Owlbear and after it did some reconstruction it patched fully.
Although the patcher looked the same as the broken freeze, with nothing happening, task manager showed the difference in a lot of CPU and increasing amounts of memory in use. Once it finished a reconstruct it was back down in memory usage.
The broken freeze the memory usage went to about 440MB and CPU usage went to 0% and stayed like that.
Easy there, angry villager. You can put your pitchfork and torch down. Arc is not the communist witch you're looking to put on trial for this instance.
The problem is in the launcher, it's not specific to Steam or Arc. I've tried both (also, Arc uses my pre-existing steam install). This has happened on each patch that has had season 9 content on it so far. I have been able to get through on each build by clicking TRIBBLE on the launcher before it automatically verifies the HOLODECK build, but since there's only been 3 TRIBBLE patches with Season 9 content so far I don't think there's enough there to establish a pattern.
It would be nice to get some acknowledgement from the dev team that they're aware of this issue and are looking into it.
Easy there, angry villager. You can put your pitchfork and torch down. Arc is not the communist witch you're looking to put on trial for this instance.
The problem is in the launcher, it's not specific to Steam or Arc. I've tried both (also, Arc uses my pre-existing steam install). This has happened on each patch that has had season 9 content on it so far. I have been able to get through on each build by clicking TRIBBLE on the launcher before it automatically verifies the HOLODECK build, but since there's only been 3 TRIBBLE patches with Season 9 content so far I don't think there's enough there to establish a pattern.
It would be nice to get some acknowledgement from the dev team that they're aware of this issue and are looking into it.
What I meant is, it could be indirectly to blame on Arc cause of some code changes / patch changes that are being made to facilitate Arc. Just a thought.
What I meant is, it could be indirectly to blame on Arc cause of some code changes / patch changes that are being made to facilitate Arc. Just a thought.
*sharpens pitchfork*
Much as I would love to get on the blame it on Arc bandwagon, I don't think that's the case. I overwrote my playtest folder with a copy of my live game then logged in and Tribble was able to patch it fully. I'm more inclined to believe there might be a problem in the previous patch that's messing with updating than any outside influence. Something that might be hardware sensitive given how inconsistent it's been affecting people, a lot of people can't patch the game, but many have been able to, some with no problems, some with minor workarounds, etc.
If something is not broken, don't fix it, if it is broken, don't leave it broken.
yeah kind of a bummer, i was gonna open a JHAS, my first one. I copied the character yesterday was hoping today i could test out this JHAS
yeah its still not working, TRIBBLE upload that stuff to ftp server so we can download it old school.
a word of warning to everyone, the same problem exists in the new patch, so even after getting it to work, ive hit the same problem again when trying to patch the march 19th update.
Comments
I opening the "Transfers" Window (ctrl+X) and it showed I was caught on the manifest as well, but by having the transfers window open it seemed to work it self out.
(This was after 6 Force quits, and 3 Verifys)
Deleting shaderCache.hogg file didn't help. The launcher just freezes and doesn't even attempt to re-download it.
^^^^^^^^^^^^^^^^^
This here worked for me and is what I would recommend doing.
e.g.
Win7 Ultimate x64
ATI Radeon 4870 1GB; catalyst 13.9
12GB DDR3
Intel i7 940 quad core; 2.93ghz
500GB free space on hard drive
UAC and AV disabled for testing
STO launched and patched through launcher (or steam or Arc)
etc.
And I have no issues with patching.
Joined January 2009
Doing the copy of Live over to Playtest now. It seems to be patching again now. Crossing fingers this goes to 100%.
Update - It patched to 100% and I was able to get in.
Find us at CovenantofHonor.com. My Twitter handle; @jmattmiracle
Decided that since the manifest was causing a problem I would delete it. Found it in the folder "Playtest/.patch", and wiped the contents of the folder just to be sure I got it. and then ran the patcher again and it completed in seconds.
Seems the manifest is getting corrupted somehow and removing it fixed my issue.
CPU and Memory usage did spike while it was patching though. CPU usage shot to 25% and memory usage shot to over 500,000k for awhile before settling down.
Just compared the contents of the folder that I deleted with the patched contents and found there is a file missing in the patched version. A file named "headers.hogg" was not downloaded again. Ah, the file was generated when I started logging into the game. Although the file "patch_trivia.txt.bak" was deleted when the "headers.hogg" file was generated.
EDIT: the .bak file was generated again while it was loading so seems that should be there.
People might want to try wiping the contents of the ".patch" folder and see if that works. Its a fairly small folder and should redownload quickly.
Also Fleet mate just signed up for Tribble making this his first patch and he had 0 freezes. So some kinda conflict with our old data?
[SIGPIC][/SIGPIC]
One of many reminders that i'm not a REAL Romulan. >_<
Bah, was hoping I had found the issue. Since a full copy will wipe those files as well and no one reported trying that before and it had worked for me.
I had done a forced verify before that and had it freeze as soon as it got to the patching. You can try the wiping/overwrite of the folder method. It should pull most of the data from the live version and just download the 1gb or so of new stuff.
Was curious so I checked. Same thing happened patching Owlbear. I wiped everything in the ".patch" folder for Owlbear and after it did some reconstruction it patched fully.
Although the patcher looked the same as the broken freeze, with nothing happening, task manager showed the difference in a lot of CPU and increasing amounts of memory in use. Once it finished a reconstruct it was back down in memory usage.
The broken freeze the memory usage went to about 440MB and CPU usage went to 0% and stayed like that.
So then we can safely put the blame on Arc, yes?
I don't use Arc. So no, you can't.
Easy there, angry villager. You can put your pitchfork and torch down. Arc is not the communist witch you're looking to put on trial for this instance.
The problem is in the launcher, it's not specific to Steam or Arc. I've tried both (also, Arc uses my pre-existing steam install). This has happened on each patch that has had season 9 content on it so far. I have been able to get through on each build by clicking TRIBBLE on the launcher before it automatically verifies the HOLODECK build, but since there's only been 3 TRIBBLE patches with Season 9 content so far I don't think there's enough there to establish a pattern.
It would be nice to get some acknowledgement from the dev team that they're aware of this issue and are looking into it.
Raptr profile
What I meant is, it could be indirectly to blame on Arc cause of some code changes / patch changes that are being made to facilitate Arc. Just a thought.
*sharpens pitchfork*
yeah its still not working, TRIBBLE upload that stuff to ftp server so we can download it old school.