Honest question for SDS
-
I'm going to get a tiny bit technical and I apologize in advance.
Freeze offs will never go away as MLB plays P2P for head to head play. One side is locking up on the other, and until one side terminates connection with the other, and one side is able to send an outcome to SDS without the other side sending conflicting data, the game will never end.
It's possible for one side to lock up the game, move on to another, and leave you in a state where you are forced to quit or terminate connection. Not a fault of SDS directly. It's more of a guilty party thing. No code is 100% able to not be exploited.
A majority of freeze offs are done so due to excessive network traffic during an abnormal event that needs to get reconciled by both consoles.
People that leave a machine on for hours during a freeze off, are abusing their systems. To each their own.
If I was losing, I'd quit. If I was winning, I'd give it 5 minutes and then quit. That's me though.
-
P2P is peer to peer. SDS servers store data, update data as you navigate menu to menu, send data to your console for moments, and match make you with opponents when you play RS, BR, events etc.
They don't have dedicated game play servers like people sometimes think they do. Everything is data transmission/storage, match making oh.. and data transmission/storage.
-
Yes, I did sit there just as long. But I was winning and was up to bat with no outs. Pretty sure if the game continued I would've won anyway.
Also, when the first thing your opponent does during his initial AB is hold R2 for the ENTIRE inning, plus do it again for the ENTIRE second inning, then msg you after the freeze-off started saying; "Good luck getting this win.#; I was pretty much in it for the long haul.
The point of the post is that there has to be some way of working around having to sit there for minutes, hours, or even days, just so someone can get a win in a game that they are clearly going to lose.
-
@dj-sparky-2k22_psn said in Honest question for SDS:
Yes, I did sit there just as long. But I was winning and was up to bat with no outs. Pretty sure if the game continued I would've won anyway.
Also, when the first thing your opponent does during his initial AB is hold R2 for the ENTIRE inning, plus do it again for the ENTIRE second inning, then msg you after the freeze-off started saying; "Good luck getting this win.#; I was pretty much in it for the long haul.
The point of the post is that there has to be some way of working around having to sit there for minutes, hours, or even days, just so someone can get a win in a game that they are clearly going to lose.
I've proposed that the disconnect trophy be broken down to differentiate between a menu quit and console quit. Give out a different one for each type.
Console quits are dashboards or internet "time outs". SDS could parse that easily, and punish repeating users.
If people knew that their console quits were racking up for a time out, they'd stop.
The dashboarding goobers are just trying to get on to the next game while being toxic.
-
I don’t see the point of waiting 18 hours there is no way it could’ve been worth it. It doesn’t matter how the other guy is playing. The fact that you are waiting 18 hours proves the point why freeze offs are a problem.
The longest I have ever waited on a freeze off was 45 mins to an hour. That’s only because I had to [censored] and had to shower. Otherwise I would’ve quit after 10 mins max.
Waiting 18 hours is pointless only to get a win. Out of the scenarios you could’ve been playing there is no way that it was worth it.
If you were playing ranked seasons and quit, you maybe lose like a max of 20 points. The ranked season program path is based on innings this year not wins so it’s not like winning would’ve been anything special.
If you were playing the event, you wasted 18 hours of possible wins you could’ve gotten. The event is free and you can enter as many times as possible.
The only way I see it being anything close to worth it is if you were 11-0 in BR. Even then the flawless rewards are like max 50k.
Just quit the game and take your L
-
So last year there were periods where people could make the game freeze on purpose, so if that becomes an issue again and gets widespread, having a system that guarantees a win means those people will freeze games as soon as they take the lead, guaranteeing themselves a win.
Winning 3-2 in the 9th, but your opponent has bases loaded with no outs? Don't worry, just freeze him and you get the win!
-
@hoboadam_psn said in Honest question for SDS:
I'm going to get a tiny bit technical and I apologize in advance.
Freeze offs will never go away as MLB plays P2P for head to head play. One side is locking up on the other, and until one side terminates connection with the other, and one side is able to send an outcome to SDS without the other side sending conflicting data, the game will never end.
It's possible for one side to lock up the game, move on to another, and leave you in a state where you are forced to quit or terminate connection. Not a fault of SDS directly. It's more of a guilty party thing. No code is 100% able to not be exploited.
A majority of freeze offs are done so due to excessive network traffic during an abnormal event that needs to get reconciled by both consoles.
People that leave a machine on for hours during a freeze off, are abusing their systems. To each their own.
If I was losing, I'd quit. If I was winning, I'd give it 5 minutes and then quit. That's me though.
Ok. I'll admit that I know nothing about coding. But if SDS can code it that a pitcher, in an H2H game, MUST throw a pitch within a certain timeframe or it will throw one for you; why can't they do the same for a freeze off?
Now, from what I gathered from your post, a freeze off is initiated when one of the players 'loses connection'. If that happens they why can't it be set up where, after a certain amount of time passes, and there is not a baseball move; the game just ends and gives the person the loss?
Now some may say that if it's not a solid loss of connection; there is no way for the programming to kick in to end the game. But if that's the case; then the programming does know something is up and it should show on the back end.
-
@deetch_30_psn said in Honest question for SDS:
I don’t see the point of waiting 18 hours there is no way it could’ve been worth it. It doesn’t matter how the other guy is playing. The fact that you are waiting 18 hours proves the point why freeze offs are a problem.
The longest I have ever waited on a freeze off was 45 mins to an hour. That’s only because I had to [censored] and had to shower. Otherwise I would’ve quit after 10 mins max.
Waiting 18 hours is pointless only to get a win. Out of the scenarios you could’ve been playing there is no way that it was worth it.
If you were playing ranked seasons and quit, you maybe lose like a max of 20 points. The ranked season program path is based on innings this year not wins so it’s not like winning would’ve been anything special.
If you were playing the event, you wasted 18 hours of possible wins you could’ve gotten. The event is free and you can enter as many times as possible.
The only way I see it being anything close to worth it is if you were 11-0 in BR. Even then the flawless rewards are like max 50k.
Just quit the game and take your L
I forgot to add to my original reply if why I waited is that the freeze off happened at 2:30am eastern time. I was heading to be after that game anyway so I figured I would let it sit in hopes that he would quit and give me my much deserved win (since I'm trying to complete the BR Program before tomorrow and am only at 70pts).
When I got up this morning; it was still froze and since I had appoints all day and wasn't able to play until later this evening I figured that I'm in it this far and I may as well ride it out.
I had all intentions of whiting when I got in later in the evening; but when I checked when I got home, he had already left.
Was it his fault for sitting there? Maybe.
Was it my fault for sitting there? Maybe.
But who's fault was it that we had to experience that freeze-off? SDS's, most likely. And I say that because I'd there are unknown factors, or at least that we think/they say, causing one of your MAIN game modes to mess up, especially one with rewards tied to it, then either find a fix or don't have that mode.
-
@dj-sparky-2k22_psn said in Honest question for SDS:
@hoboadam_psn said in Honest question for SDS:
I'm going to get a tiny bit technical and I apologize in advance.
Freeze offs will never go away as MLB plays P2P for head to head play. One side is locking up on the other, and until one side terminates connection with the other, and one side is able to send an outcome to SDS without the other side sending conflicting data, the game will never end.
It's possible for one side to lock up the game, move on to another, and leave you in a state where you are forced to quit or terminate connection. Not a fault of SDS directly. It's more of a guilty party thing. No code is 100% able to not be exploited.
A majority of freeze offs are done so due to excessive network traffic during an abnormal event that needs to get reconciled by both consoles.
People that leave a machine on for hours during a freeze off, are abusing their systems. To each their own.
If I was losing, I'd quit. If I was winning, I'd give it 5 minutes and then quit. That's me though.
Ok. I'll admit that I know nothing about coding. But if SDS can code it that a pitcher, in an H2H game, MUST throw a pitch within a certain timeframe or it will throw one for you; why can't they do the same for a freeze off?
Now, from what I gathered from your post, a freeze off is initiated when one of the players 'loses connection'. If that happens they why can't it be set up where, after a certain amount of time passes, and there is not a baseball move; the game just ends and gives the person the loss?
Now some may say that if it's not a solid loss of connection; there is no way for the programming to kick in to end the game. But if that's the case; then the programming does know something is up and it should show on the back end.
The forced pitch is in the game mechanics and has nothing to do with connection between players.
The funny thing about connection logic, is that it doesn't care who's winning and who's losing. In it's basic form, the logic works like this:
Home team sends result A, away team sends result A. Next event triggers.
During a freeze, home team sends A, SDS is waiting for away team's send. One side eventually stops communication during a reconciliation attempt by the SDS server. Could they try to code something where THEY (SDS) force a disconnect due to no data being sent? Yes but it would create more issues than solve.
Play a friendly game with somebody you know. Have both sides record or stream the game. You will see subtle differences in animations and PCI feedback, but results will be the same. There are bugs with hits vs errors at times, and that's on SDS to fix.
-
@hoboadam_psn said in Honest question for SDS:
@dj-sparky-2k22_psn said in Honest question for SDS:
@hoboadam_psn said in Honest question for SDS:
I'm going to get a tiny bit technical and I apologize in advance.
Freeze offs will never go away as MLB plays P2P for head to head play. One side is locking up on the other, and until one side terminates connection with the other, and one side is able to send an outcome to SDS without the other side sending conflicting data, the game will never end.
It's possible for one side to lock up the game, move on to another, and leave you in a state where you are forced to quit or terminate connection. Not a fault of SDS directly. It's more of a guilty party thing. No code is 100% able to not be exploited.
A majority of freeze offs are done so due to excessive network traffic during an abnormal event that needs to get reconciled by both consoles.
People that leave a machine on for hours during a freeze off, are abusing their systems. To each their own.
If I was losing, I'd quit. If I was winning, I'd give it 5 minutes and then quit. That's me though.
Ok. I'll admit that I know nothing about coding. But if SDS can code it that a pitcher, in an H2H game, MUST throw a pitch within a certain timeframe or it will throw one for you; why can't they do the same for a freeze off?
Now, from what I gathered from your post, a freeze off is initiated when one of the players 'loses connection'. If that happens they why can't it be set up where, after a certain amount of time passes, and there is not a baseball move; the game just ends and gives the person the loss?
Now some may say that if it's not a solid loss of connection; there is no way for the programming to kick in to end the game. But if that's the case; then the programming does know something is up and it should show on the back end.
The forced pitch is in the game mechanics and has nothing to do with connection between players.
The funny thing about connection logic, is that it doesn't care who's winning and who's losing. In it's basic form, the logic works like this:
Home team sends result A, away team sends result A. Next event triggers.
During a freeze, home team sends A, SDS is waiting for away team's send. One side eventually stops communication during a reconciliation attempt by the SDS server. Could they try to code something where THEY (SDS) force a disconnect due to no data being sent? Yes but it would create more issues than solve.
Play a friendly game with somebody you know. Have both sides record or stream the game. You will see subtle differences in animations and PCI feedback, but results will be the same. There are bugs with hits vs errors at times, and that's on SDS to fix.
I can understand that.
-
A admin locked this topic on
