Ironkrieg.2056

If I understand VPN correctly, your system talks to the VPN provider, then they talk to the GW2 servers. Thus, your system would not be talking directly to the GW2 servers. That may explain why the VPN works to eliminate the disconnect issue. 🙂

POSSIBLE FIX FOR GW2 STORYLINE INSTANCE DISCONNECTS Ok. Going to go out on a limb here and describe a set of changes I made that have (so far) allowed the game to play without any further Storyline Disconnects. I had a situation during the instance in Sparkfly Fen, the one where your Asura team destroys three towers with explosives. That one had failed on me over and over for the past year+. Every couple of months I would reinstall the game, try a few things, and see if it helped. Nothing worked. Thinking about it, I analyzed that it must be a combination of something in the GW2 system and something on my system. If it was just GW2, then a whole lot of folks would have the problem. If it was just in my system, more MMOs with instances that I play would have the problem (no others do). So, I think it is a combination of something on my system and something in the GW2 code that is conflicting. So, I decided to do some deep research on improving network performance. Two promising lines of change showed up. After having made these changes, the system completed the Sparkfly Fen instance and has completed dozens of further instances without issue. I was going to wait longer for more instance play throughs but decided to post the information instead of waiting. Here are the changes: * Open up the Network Adapter Properties dialog * Have <only> the following enabled: - Client for Microsoft networks - File and printer sharing for Microsoft networks - Internet Version Protocol 4 (TCP/IPv4) Some systems may need more than the above three enabled, but mine does not. So, I set everything else to off. * From the same Network Adapter Properties dialog select the "Configure..." button * From the Connection Properties dialog that comes up, select the "Advanced" tab * Find "Interrupt Moderation" and DISABLE it. The "Interrupt Moderation" is what I suspect to be causing the disconnects. The articles I found say that Interrupt Moderation should be disabled for gaming. So, I disabled it. So far so good. If the above changes allow anyone to proceed past a Storyline Instance Disconnect fail point, please post back and let others know to try the changes. If it does not help, post that back as well. Good Luck

This bug has been around for a long, long time and the developers will not or cannot fix it. The bug does not affect everyone, but if you have it, there is no fix for it. Might as well move on to a different game. Sorry to give the bad news, but better now than spending hours and hours attempting to work around it and ultimately failing. Like I did. I check back here every once in a while to see if there is an announcement that the developers have fixed this. Still waiting. By the way, you are not really 'disconnected'. The system is unable to return you to the main instance from the story instance, but you are still fully connected to the game servers.

What can it hurt to delete the .dat and Cache files and see if the failures still happens? Especially if you have a 100% fail point to test it out on, like I had. I have just completed the Lvl 50 and Lvl 60 story lines without a hitch. I was having these end of cut scene 'disconnects' quite regularly until I deleted those files and forced the game to recreate them fresh. It could be those files somehow just get corrupted. Once corrupted, that would be it, since the game cannot fix them automatically and they are not deleted during the uninstall procedure.

Please, folks . . . if you are having these sorts of disconnects, delete the .dat and cache files as detailed in these instructions (Posted by Silent6173): "What I would suggest is look at GW2's troubleshooting page. Also, search wiki for solutions such as this. Searching there is usually more productive." After deleting those files, my own disconnect issues seem to have been resolved. Just uninstalling/reinstalling will NOT do anything as uninstalling does NOT deleted these files! If they are out-of-date and/or corrupted, they will STAY corrupted until they are MANUALLY deleted.

Update on the story line instance disconnect issue. As I posted a few above, I deleted the .dat and Cache files as recommended in the advice quoted in my post (from a few posts above mine). That fixed the 100% failure point that I had been trying every few months for two years to see if it was ever fixed by the developers. I now believe I know why it was never 'fixed' and they could not replicate the failure. When you uninstall GW2, it does NOT delete that .dat file nor does it delete the Cache file! In my case, I had returned to the game after over a year away. I believe that the code had made several updates and conversions to one or both of those files, but the code was NOT able to successfully update from my old version to the current. Thus, there was an incompatibility left that crashed the story instances. Uninstalling did no good, as those files were left in place to fail on any future installs. I have since started a new character and have been doing all the personal story instances as I progressed. I have now completed the level 10, 20, 30 and 40 story instance chains without a single failure. I know that a negative result does not 'prove' anything definite. But is a very clear indication that it just might be one or both of those files, which the game never deletes, that may be the source of these problems. I would certainly like to recommend to the developers that they modify the uninstall code to delete these files during the uninstall process. I will update this thread when I either finish the level 80 story line, or I have a disconnect failure. Until then, I would recommend anyone having story line instance disconnects to follow the instructions in the previous post and delete the .dat file and the Cache file. Good Luck!

This information fixed the problem for me! A bit of background. I was sometimes having the storyline 'disconnect' events at the end of the mission. Then, I had one with 100% failure rate. Just left my character there for the last year or two and just tested it every few months. Based on the two sets of above instructions, I deleted the Local.dat file and the “gw2cache...“ file. Then, a fresh install. I changed nothing with the default setups other than to lower the dialog sound a bit (but not totally off). Scenario successfully finished! Don't know if it was a 'random' success. Or if it was something that ArenaNet did in the code. Or if deleting the cache and dat files did the trick. I am going with the file deletion and fresh install, but will post back if it fails again. Thanks for the information and some hope! 🙂

I am not buying it (own HoT and PoF) because of the story instance disconnect defect. Simply won't play a story based game if the story system is broken.

This is a defect in the system since HoT. The developers refuse to devote any time to finding and fixing the problem, even though the location of the problem is well known and documented. I quit the game a year ago because I started a new character and could not do the instances. I check back every so often to see if it has been fixed. Apparently not.

Having experienced this myself a number of times, I eventually quit GW2 as the instances are a major part of the game for me. I check back every once and a while to see if there is some fix that has been implemented. But I guess the cost to fix this issue is much greater than the number of customers being lost contributes in GEM purchases. So, nothing gets done. Be back in six months to check again.

"...fix can only happen if the bug can be reproduced reliably..." This developer position is total garbage. As a 20+ year career Software Engineer, I have tackled many, many issues of software defects that could not be reliably reproduced. It takes knowledge and perseverance to put in the logging and examine the code to figure out what is happening. Something the developers are simply not willing to do, apparently. Even given that, the simple work around to this issue is to make character progress in these instances persistent so a player can go back in after a DC and continue. Hell, they might even be able to see a reproducible failure if going back in does not actually reset the defect! It is just disgraceful and the developers should be ashamed of themselves. And the managers should do a self-check on their own professionalism. I bet if they had a car, or phone, or whatever that failed in this way they certainly would not put up with it for long!

And, I am done with GW2. Having completed a Story step, on exiting I was disconnected on entering the main game world. On (immediately, still logged in and at character select on getting booted) re-entering the game, I found myself standing in front of the instance star with the Story step uncompleted. On re-entering the Story step, yeah, not even anything done with it. Would have to do it ALL over again completely! Uhh, no. Won't be buying Gems. Won't be buying EoD. Won't be playing this broken game at all anymore. I advise anyone that is seeing this topic to think long and hard about investing time and money into GW2. And look how long this problem has existed, and been ignored by the developers.