First of all, I know there was a warning given out in the December TWAB but this goes beyond that.
I have no issue connecting to any other service in the game, I have no issue with system requirements, and or any connectivity issues with ANY other game.
99% of the time, I get in fine to gambit, then all of a sudden since opulence's release the load times have been ridiculous, at first I thought it was my net, ran tests. nope. Next logical step was hardware issues, check, Nope. Then I start randomly getting booted back to orbit after 45 seconds to a minute giving me an abandonment notice. this has happened several times over the last few days and now i have been issued with a suspension from gambit.
To be fair, this is obviously an issue with YOUR servers Bungie. Not an issue on my end. and now due to the fact you refuse to provide adequate local servers im suspended?
Not on Bungie, poor form.
Battlestate games, a developer based in Russia with a player base 1 100th of yours has Sydney servers with less than 15ms latency in a game far more technically advanced, and I know for sure they dont have the resources you do. This is just poor infrastructure on your end.
Do something for your OCE player base and work on these issues. and or at least pool us together with ping limitations like you did with Halo. id rather much longer wait times than be suspended over BS like this.
My entire clan is irate over this. we are tired of the slow load times when grouped, and we want something done. rather a review of your systems and the way you load players into games or an overhaul of your servers in the OCE region.
The fact I'm left in the dark over an issue that is clearly just poor server performance on your end is appalling.
Hoping to have the suspension lifted and or all quests requirements that require gambit to be auto-completed, only fair if you're going to suspend me for trying. a full paying customer, and guardian since d1 beta, one that hasn't had issues till now.
-
2 Antworten"at first I thought it was my net, ran tests. nope." what 'tests'? "Next logical step was hardware issues, check, Nope." again, what did you check?
-
4 AntwortenWhat servers?
-
1 Antworten2 questions for you: 1. When were you suspended and how many times have you been? 2. Were you booted with any sort of error code?