<COLOR> <SHIP>: FDev, please explain. *SOLVED* lol

Stonn Mrogg

Stonn Mrogg
Blue Cobra
Orange Sidewinder
Magenta Krait
Crimson Krait
Mauve Adder
Black Adder <- fond of this one
Taupe Cobra

and all the rest I forgot or have yet to experience.

What... does it all mean??? Other than being pulled of out Elite Dangerous Space. I figured out Mauve Adder is a connecting issue on my end. Orange Sidewinders seem to be a server-side fail, but is there anything more to glean?
 

Northpin

Northpin
Error codes.
If you're going to report an error, it's easier to remember the mauve adder instead of 0x000046294b7
 

Northpin

Northpin
Commdor said:
customersupport.frontier.co.uk

What does the connection error I am seeing mean? - PC

CONNECTION ERROR MESSAGES Error message What does it mean? What can I try? Orange Sidewinder This is a generic error which means that you cannot connect to the server. This most often happens ...
customersupport.frontier.co.uk customersupport.frontier.co.uk
Click to expand...

Yea, right...
I've got my share of errors and none had anything to do with something on my end. It was always at FD's end or maybe on the route there.

For example, to recover from the Orange Sidewinder, most of the time it's enough to quit to desktop - that is exit the game completely, then restart the game. It usually solves it, if not the first time, then after the second quit to desktop.
 

Factabulous

Factabulous
Northpin said:
For example, to recover from the Orange Sidewinder, most of the time it's enough to quit to desktop - that is exit the game completely, then restart the game. It usually solves it, if not the first time, then after the second quit to desktop.
Click to expand...
Hmm. If it ever takes multiple restarts then surely that points to a "just wait 5 minutes" solution, and the restarts are just "what people did while waiting"? (Still not a client issue I agree. Not sure I ever needed a double restart :unsure: )
 

Northpin

Northpin
Factabulous said:
Hmm. If it ever takes multiple restarts then surely that points to a "just wait 5 minutes" solution, and the restarts are just "what people did while waiting"? (Still not a client issue I agree. Not sure I ever needed a double restart :unsure: )
Click to expand...

My theory is the timer is needed for them to start another node in the server farm, but apparently the client is not redirected to the new node unless a full client restart is performed and the previous connections to the not responsive node (overcrowded one) are not closed.

And they do look like the standard support bullcrap - sometime i put out this stuff myself. 🤷‍♂️
The customer calls, and you make him go through a series pointless checks (culminating with: when was last time you performed a restart of your computer) to give you enough time so solve the server/infrastructure side cause of error. And by the time they finish the restart the problem is solved. And they also come to the conclusion that they should restart their computers more often :)
 

Jmanis

Jmanis
I don't normally get these errors, or if I do, it's a painfully obvious issue on my end. But tonight, damn, getting a heap, all adjudication server errors, and codes I don't normally see like Blue Cobra. Something's hinky.

@Factabulous , of note, no "long range delivery" missions tonight >.>
 
You must log in or register to reply here.
Back
Top Bottom