Game unplayable both OPEN and SOLO, Frontier please fix your game!

IIRC almost everyone agreed that rubber banding is probably caused by Frontier, while stuttering, freezing and lock ups could be related to the local machine. Your reply to that was always sarcasm, irony and snark, suggesting that every issue must be caused by Frontier and we shouldn't even imply that people could try to look for other solutions while waiting for an update.
Still love you though! ;)

Rubber banding is definitely down to people with bad connections.

In deciat loads of players no issues, one fella jumps in everything starts rubberbanding then stops immediately when he drops out at the engineer.
 
Rubber banding is definitely down to people with bad connections.

In deciat loads of players no issues, one fella jumps in everything starts rubberbanding then stops immediately when he drops out at the engineer.
Sometimes, but not necessarily always.
 
Rubber banding is definitely down to people with bad connections.

In deciat loads of players no issues, one fella jumps in everything starts rubberbanding then stops immediately when he drops out at the engineer.

Also NPC in SOLO are affected by rubber banding. So it's not due to the network in this case (below is a NPC).

148006
 
Similar experience (sans rebuys:)) and we shared the same instance a few times too o7

The rubber banding is AWFUL though. At some stage I exited through the mail slot in my Cutter, while another Cutter zig zagged and jerked along at the same time. Not sure how we managed not to get stuck. I've never seen it this bad and it's very consistent i.e. it happens almost always now especially if another player is around. Really hope they fix this soonish.
Are you Obi Wan Shenobi? When I saw this name I thought about you actually
 
Your reply to that was always sarcasm, irony and snark, suggesting that every issue must be caused by Frontier and we shouldn't even imply that people could try to look for other solutions while waiting for an update.
Fake news - go back and read ALL my posts in this thread instead of snipping out soundbites to construct your false narrative. Any snark I have is towards the people who insist a problem shared by numerous CMDRs that appears immediately after an update from Frontier is NOT a bug in the game, but rather overheating CPUs or faulty RAM. It's this silly victim-blaming that birthed my "dirty router" snark to begin with.

Now as for finding ways to triage the things that Frontier's updates break, I'm cool with that, but this doesn't let Frontier off the hook, especially when we have to jump through a ridiculous amount of hoops to fix something that worked perfectly fine before the update. And no matter what magic concoction you conjure up to patch this problem on PC, that doesn't fix the utterly rubbish performance on my PS4 (not that I care, but it further serves to prove my point).

Babbling fish... GRRRR!!!!
 
Fake news - go back and read ALL my posts in this thread instead of snipping out soundbites to construct your false narrative. Any snark I have is towards the people who insist a problem shared by numerous CMDRs that appears immediately after an update from Frontier is NOT a bug in the game, but rather overheating CPUs or faulty RAM. It's this silly victim-blaming that birthed my "dirty router" snark to begin with.
Actually it's the other way around. When I suggested that lock ups might be caused by issues on the PC you made fun about people having faulty RAM when they experience rubber banding.

Now as for finding ways to triage the things that Frontier's updates break, I'm cool with that, but this doesn't let Frontier off the hook, especially when we have to jump through a ridiculous amount of hoops to fix something that worked perfectly fine before the update. And no matter what magic concoction you conjure up to patch this problem on PC, that doesn't fix the utterly rubbish performance on my PS4 (not that I care, but it further serves to prove my point).

Babbling fish... GRRRR!!!!
Some people don't realise that what appears to be the same issue might have different causes. Stigbob appears to be such a candidate.
 
When I suggested that lock ups might be caused by issues on the PC you made fun about people having faulty RAM when they experience rubber banding.
That's called SARCASM, something you Brits invented IIRC. Do you actually take me seriously when I suggest people vacuum their router?

As for replying to your post, perhaps I was using your post as a springboard, a launchpad of sorts, to fire my Rocket Of Delicious Sarcasm (RODS) at those who do believe the update is fine and that hundreds of players suffer from hardware defects.

We've been married for how long, and you still don't know me? Oi!
 
That's called SARCASM, something you Brits invented IIRC. Do you actually take me seriously when I suggest people vacuum their router?

As for replying to your post, perhaps I was using your post as a springboard, a launchpad of sorts, to fire my Rocket Of Delicious Sarcasm (RODS) at those who do believe the update is fine and that hundreds of players suffer from hardware defects.

We've been married for how long, and you still don't know me? Oi!
I guess that's why I called it sarcasm. 🤷‍♂️
PS
I am German by the way, I guess that explains my lack of humour. ;)
 
I hope it's just coincidence and your issue will come back, otherwise a certain Duck will need to eat some hats.
He did bet against the possibility of any issue ever being not Frontier's fault. But it's optimistic to think he would accept such an outcome.
 
Has the troubleshooting fixed any of the reported issues?
I turned off IPv6, and then visited the CG and experienced no zig-zag or rubber-banding. Obviously this is not a big enough of a sample, so I'll need to try a few more times to verify it's not just coincidence.

Strange that, since I never had a problem before the update, nor does my router or ISP support IPv6. Perhaps the new update doesn't play well with IPv6, which would still make it Frontier's fault, na na na na na. That said, I don't like having IPv6 on anyway, since I have no use for it and it just steals bandwidth.

Oh, I need to be more precise - I turned off EVERYTHING except IPv4 on my network adapter. I don't need QoS or Print Services or any of this rubbish.
 
yep its gone, even with our one wingman who has a terrible connection, its not engineered yet - he will get FTTH next year
 

Deleted member 182079

D
Will also check my router settings later. Does switching back to ipv4 pose any noticeable drawbacks? Am a networking noob.

Edit: checked my router settings (I don't have the password for admin access, router belongs to my ISP) and can't find any options re IPV6. Guess I'll have to live with it until/if fixed. It's definitely not something I've come across prior to the September update.

Edit 2: disabled it in Windows now. Will see how it goes tonight.
 
Last edited by a moderator:
Back
Top Bottom