That's true. Before 2.4 I never (or perhaps once) had a game crash or disconnect, but now, I think I've had one at least once a week. But if the crash opens up the reporting tool, I'm sure it's logged as a crash and not mistaken for a clog.
PvP An Investigation Into Frontier's Actions on Combat Logging, Part 2
- Thread starter Rinzler o7o7o7
- Start date
Yep, crash thing only opens for a full on crash though. For the most common transaction server errors you just get booted to the main menu with no crash report being generated and the online options being greyed out for 15-20 seconds.
IMO Fdev could solve a lot of issues simply by:
1-Increasing menu logout timer to 45 seconds and removing the yes/no option at the end of the countdown
2-Leaving our ships in place for up to 3 minutes following any kind of disconnection other than the menu option.
Boom, problem solved, fdev can move on knowing they made everybody happy and hardly had to lift a finger to do it.
You clogged than f you. You suffered from some crummy internet connection on your end? Too bad, get better internet or play in a different mode where it doesn't matter as much. Please tell Rinz and the boys that I have solved the problem and we can move on to other issues.
1-Increasing menu logout timer to 45 seconds and removing the yes/no option at the end of the countdown
2-Leaving our ships in place for up to 3 minutes following any kind of disconnection other than the menu option.
Boom, problem solved, fdev can move on knowing they made everybody happy and hardly had to lift a finger to do it.
You clogged than f you. You suffered from some crummy internet connection on your end? Too bad, get better internet or play in a different mode where it doesn't matter as much. Please tell Rinz and the boys that I have solved the problem and we can move on to other issues.
Last edited:
Good point before it gets even more out of hand.
A question I have though is how clogs are supposed to be reported. Right now, correct me if I'm wrong, but they're handled by the other party who witnessed it and send a "Report a Player" in the game. Right?
So if this issue of clogging (as some posters have pointed out) isn't just in PvP or Open, but is also a serious cheat in PvE and in PG/Solo, how would a players clog be reported to FDev? We can be pretty sure no NPC in the game will do it, so how would it become known to FDev that someone is cloging during combat with NPCs in Solo?
Goose4291
Banned
Issues I can see...
1: 'Jason I dont have time to press escape then one click to exit the game... my kitchen was on fire and the baby was trapped in the chimney. Of course, I still had.time to press alt+F4 though'
2: Genuinely mate, its P2P. I dont think a solution like you describe can work on such a network. We used to have this issue with mission editing in Operation Flashloint if people wanted to host their own games rather than running it on a dedicated server :/
I got disconnected, game froze, and crashed about 5 times in one single day once. It was when our Dead End Circumnav Expedition did the first mass jump. We tried to jump some 80 people, I think. Suddenly, we got an NPC pirate or bounty hunter in our midst as well. Now, my problems started when I just clicked my button to switch to outside camera. Crash. And after that, every time I tried to get into the instance, things happened. It was quite frustrating. If there was any automated clog system, I'm sure I would've been on the list because of this, but it wasn't my fault.
Now, the good thing is, I wasn't alone having the problem, probably 50 other players had the same issue. And no one, of course, reported anyone for disconnecting involuntarily.
The point is though, things like this happens in the game, and I can imagine if there's a larger battle of many players, this might look like clog while it's not.
1:natural selection at work
2:for real? Because of p2p we can't leave a ship in place after a log out, it's a technical impossibility?
Hey guys, hold off on calling Rinz and the boys...
I think that has happened to me once or twice as well. It wasn't this bad Q1-2 this year, but has gotten slightly worse this fall.
It's likely not particularly feasible with the infrastructure Frontier has in place...which is why I'd be content with simply punishing those who seem to be doing so repeatedly and deliberately.
That's not considered clogging though, is it? I thought clog was like Alt-F4, removing network cable, or simply turning off computer. Exit the game is an approved "clog".
Besides, I get interrupted a lot at home. (Wife, kids, dogs, UPS, neighbor, you name it), so I have to quit the game about once or twice every hour for something, and it's usually something that has to be done this second (wives... you know, can't wait one minute to get the trash bags out the door
), so having too long exit of the game would be a bit of bother.One minute would be enough I suspect, but yeah, why not.
Sometimes it's not the internet per se, but the game itself. I've had the game just quit completely on me once or twice. No bug report dialogue, nothing. Just complete kill switch. Not a big problem though, since I'm rarely ever in combat, but just saying.
Effectively.
That's not to say a solution cannot be found, and ED is a unique kettle of finish in that there is a server in between us all - it just doesn't host our actual gameplay sessions.
Would be interested to know if, with the correct networking magic, the BGS servers can start hosting a player's session temporarily when they disconnect without logging out. As someone that works in networking, even I don't want to touch that question with a bargepole though; only someone with an innate understanding of ED's networking can answer.
Someone once proposed the session of someone that CLogs moves to the nearest viable host - e.g. if you combat logged against me, your session would likely be hosted by my for a few seconds following your departure - but this is worse than doing nothing about it. Latency issues aside, with the right networking knowledge one could easily fake the death of others and send it to the BGS servers, effectively killing people at random when they log in.
Which is the same as saying that players who don't fit will quit. Fewer players, we'll be flooded with "ED is dying!" threads on the forum.
Interesting point. It might be. Instancing and handling of the ship is done on each players computer and not on the server, I think, because of the P2P design.
Basically, nope.
The technical brick wall is doing it in a way that cannot be hacked or cynically altered. No peer to peer client can be trusted to arbitrate.
Which is the same as saying that players who don't fit will quit. Fewer players, we'll be flooded with "ED is dying!" threads on the forum.
Interesting point. It might be. Instancing and handling of the ship is done on each players computer and not on the server, I think, because of the P2P design.
By "natural selection" I was referring to the baby getting stuck in the chimney
I was going to agree and suggest putting the confirmation at the start.
But since you want to get all militant about players with poor connections, FDEV sold me a game with offline mode then dropped it prior to release. There's nothing in the EULA/TOS or specs about speed or stability just broadband. They could alter it for new customers in theory but it wouldn't be retrospective.
Looks like your plan won't work.
xDBy "natural selection" I was referring to the baby getting stuck in the chimney
And won't be a contender for the next Santa Claus either.
As a now intrigued networking troubleshooter/implementation engineer, please do elaborate. I'd love to hear something genuinely interesting today.
Rats cannot vomit. Possibly as an adaptation to eating manky things.