Opinion : ARX update is a failure

Ok, so I'm not alone in having issues with this patch. But a week where only 1 attempt in 4 resulting in usable game has one side effect that leads me to conclude that ARX has failed as a revenue stream increaser, at least with me.

Pre-patch I'd have periods of time where I'd play other games, then come back and play ED. When playing I'd fly my ship and enjoy it, maybe get a new ship and often once a week, on Friday mostly, I'd treat myself to something. A ship kit, new paint, some commander customisation, whatever. The point is, after playing I'd spend money buying something.

I'd fully expected to translate that into "Buying some ARX" to spend on things. But it didnt work that way.

I have a frustrating experience getting in and playing that almost always resulted in my saying 'frak it, I'll play something else' . Ok, patch day bugs are not unknown I'd thought that the 'Black Adder' fix would solve it. But I keep getting disconnected, and not in the say way each time either.

So , post patch my experience is : Attempt to play , disconnect, retry , fail or get in for a few minutes then disconnect again. Then get frustrated and give up. No inclination at all to spend any money.

Conclusion: The September update has reduced if not removed my inclination to spend money. It is thus a failure.

(Linked to latest issue : https://issues.frontierstore.net/issue-detail/5294 )
 

sollisb

Banned
Thanks ! I made those changes and played this morning and was able to play without disconnecting . Of course I can't tell if that actually fixed it or it's a coincidence.

Turn off the Port Forwarding and see it return to bad mode..? If it still plays ok, remove the Port Forwarding entirely.
 
Nonsense. You don't need port forwarding or UPnP to run a stable game. I'm playing with closed ports in Open and also see other players. It most likely would be more with open ports (as my machine could act as host when no other host is available) but other than that it has nothing to do with OP's experiences. I've never seen this black adder thingy in Open on PC and my game runs pretty stable.


Definitely not. And that's not just from hearsay...

But maybe I should try port forwarding and see if I'd run into the same issues? If that's (port forwarding as 'solution') really not just a strange coincidence, it must be something odd with OP's router or local network settings, but it simply can't be port forwarding as such, as in this case I would run into the same issues.
The one thing I learned after working with (or against) computers is: You never know. :)

I could give you countless examples where something didn't make any sense but it worked.
 
Nonsense. You don't need port forwarding or UPnP to run a stable game. I'm playing with closed ports in Open and also see other players. It most likely would be more with open ports (as my machine could act as host when no other host is available) but other than that it has nothing to do with OP's experiences. I've never seen this black adder thingy in Open on PC and my game runs pretty stable.
I had severe connection issues after every major update, just as OP. Matchmaking error happened once in a while between those, although most of the time I could play fine.
Couple of moths ago I had problems connecting to servers and I couldn't start the game, while everybody else seemed to be unaffected.
I've looked around for possible solutions, set up Port Forwarding, issue was gone and last update went smoothly for me in that regard. I also haven't seen any of those new errors with cute code names.

I have no doubt you can run stable game without going through all that. Nobody said you couldn't. I have no idea how your network is set up. Like it's written on the page I linked:
"Port forwarding is commonly used to resolve problems encountered when connecting to the Frontier Servers, or to other players. It is especially important to enable port forwarding if UPnP is disabled or unsupported by your router."
Nobody says it's required to play.
 
But maybe I should try port forwarding and see if I'd run into the same issues? If that's (port forwarding as 'solution') really not just a strange coincidence, it must be something odd with OP's router or local network settings, but it simply can't be port forwarding as such, as in this case I would run into the same issues.

The network is Virgin Media fibre connection with connection to the PC routed over a pair of powerline network adapters. Other than the port fowarding and changing the default admin password (which you should always do) theres nothing unusual about it. In fact the only unusual thing is that I'm in charge of it and I'm a software developer with past experience in Windows, Linux, Novell, Amiga and Sinclair networking.

I echo the sentiment of others that this shouldn't be necessary, but then you can never tell what causes issues like this.

It's a shame there wasnt a beta test I could have taken part in to check all this and report the error.
 
I'm behind a double NAT, have no port forwarding, UPnP is disabled and have no connection problems with ED.

But that still doesn't mean that your router is good.
 
I wasnt able to connect the day it came out, but i havent had problems after tye first couple days. This sounds like an issue with your stuff
 
So in summary, “It may or may not be necessary, nobody knows, but Frontier suggest that UPnP might be necessary for some unspecified reason.”

Ok, then 😜🙂

I’ve had UPnP disabled on my router since it arrived, but I’ve not had any difficulties. Hopefully it stays that way!
 
Query for those that disabled UPnP and don't use Port Forwarding: does Multicrew work with you inviting other CMDRs into your ship?
 
Query for those that disabled UPnP and don't use Port Forwarding: does Multicrew work with you inviting other CMDRs into your ship?

Regrettably, I can’t answer that myself, as I’ve never let anyone on board :) I’m just anti-social like that ;)

Now you mention it, I wonder if CQC would work, too. Again, I’ve never tried that either.
 
Back
Top Bottom