old foes return

[mintTea]

following the release of final shape

Error Guitar
Error Beet

All server side.

[DM]

im getting the Guitar error too, annoying as ♥♥♥♥

[ThVIIIKonradCurze8]

last mission and get the middle finger to orbit

[Galaxia_VII]

Babooned

[нιт◈ᴘᴏɪɴᴛ]

Raid release maintenance. 1h downtime.

[mintTea]

Error Bat

and about 90 seconds of black sreen

[mintTea]

Error bee......

[mintTea]

there is a difference between participating with the events as opposed to joining the events.

i cannot join the events, although when I can join strikes nightfall or gambit it all progresses as usual,.

I believe the Destiny client is not connecting correclty or in a timely predictable way as previously with a Destiny server, and therein lies the problem,.

100k+ users is a situation bungie must have considered but seems failed to adequately plan comtingenies.

How many companies subject their clients to this type of ritualised abuse?
Bungie have no real excuse for the current situation.

Every time it seesm that stability has appeared i am tempted to buy a season pass.

However I spend hours tryging to connect instead.

[mintTea]

aftter several hours of not playing destiny i launched and queued for gambit.
Straight in no issues.
interface snappy and all as usual, internet traffic and connection client server communicated well.
i did notice the destiny client slowing as i navigated various pages afetr the gambit match.

this offers that the DEstiny Client is fatally flawed and should be reworked or rewritten with a previous version.
the connection and issues i face are not related to hardware which beet error offers as explained incorrectly by bungie.

i had prevoiously also encountered Error Watercress.

the guily party in this is bungie.