Trying to get a general idea of how many people are experiencing Kick to Orbit (KtO) and Kick to Login (KtL) errors. [u]Please, post any missing error tags so I can add them[/u]. Then, hopefully, Bungie will see how many people are getting these errors and realize that they've got to fix this problem right now...
Feel free to share your experience with the frustrating errors here, but more importantly [b][u]VOTE SO BUNGIE CAN SEE HOW BAD THIS REALLY IS!!![/u][/b]
[b][u]EDIT 7:30 PM (CST):[/u][/b]
Added new tag(s): #Zebra
Keep the discussion coming so Bungie will get their shit together.
-
Had the same weasel errors as everyone else (before that previously known as centipede) to be honest been getting problems pretty much since launch although not as often as I once did it's still bloody annoying Few things I have noticed though other might find helpful!! 1. Achievement lag seems to cause a boot 2. Tuesday reset day where players seem to on different versions causes issues I.e cannot join 3. Xb1 and ps4 maintenance periods always hurts destiny more than other games 4. Those resetting their routers in frustration be aware of direct line management (uk anyway) this won't be helping your connection stability I was doing this it's a ball-ache for days after (until I researched its impact) go easy on your ISP Beucause in UK all ISPs, with exception of Virgin, use their exchange and the DLM is run through then most ISPs have no control over it!!! 5. I requested my isp to turn my interleaving switch off my ping is 10 to London now get a consistent 74 Mbps down and 19 Mbps up although this might not be an option for most unless you have a pro package. 6. If you are on xb1 take the detailed network stats with a pinch of salt, it's getting data from the Microsoft Seattle centre not one from the local azure server to you 7. Port forwarding did nothing for me and to be honest The standard UPNP should be enough for most especially if you have a few devices connected! This should be reserved for people on campus or some other shared site most domestic users need not apply! 8. Obviously a no brainer but if you can connect to your router via Ethernet cable rather than wirelessly do so. if it the latter play around with the channels using speedtest.net until you find the best channel most routers set this to auto 9. I have found a hard reset(holding xbox button for 8 seconds) helps also before turned off kinect which also seemed to stabilise for a time 10. Most routers have detailed network statistics check for noise margin and attenuation stats. Below a 6 is not good for most again research both of these, if anything you might squeeze a bit more speed out of your line when you do, will also give you ammunition with your isp 11. In uk those using fibre or adsl who are non virgin and wired to their router, look into using a splitter faceplate rather than filter with the master socket you will see more reliable connection. BT have just released mk3 VDSL filtered faceplate look this up as a first start point and go from there. 12. My ISP is sky don't for a second Believe the bullshit they come out with, its clear after week or so of research I am now able to have a full debate and break down their poor scripting arguments with ease and this is with their supposed "pro team" and I don't profess to be an expert in any sense. They also have very little in the way of diagnostics tools to help you, again the monopoly BT have in the uk by owning pretty much everything! Now if it's none of these sorry boys and girls your shafted like me :) ..... can it be anything other than bungie servers? Although some of these have seen me get fewer errors. Whether that's a result of my antics or Bungie who knows? The silver lining though is you might have learnt a bit along the way like I have:)