Off PCI homers and Comment Regarding the Display Feedback Code versus the Actual Hitting Code
-
Can SDS Engineering comment on the off-PCI homers? Personally, I think the issue is not really an issue, yet rather an offset/timing bug between the hitting engine code and the display code. I think sometimes that code that displays the hitting location displays slightly incorrectly in relation to the actual hitting engine code. The display code of the hitting feedback would be single-threaded code, dependent on the actual hitting engine code.
People often state that "this was an off-PCI home run", when in reality it probably was not, yet rather just that their is a bug in the hitting feedback display code that makes it look worse than it is. Some comment from SDS engineering regarding if there is a disconnect between the actual hitting engine code and the feedback display code would be great.
Maybe something that says "....The hitting display feedback is not always 100% correct, and sometimes displays off-PCI home runs, that are in-fact, actual home runs, yet just don't always display correctly. We are aware of the issue and it is a bug, yet rest assured, off-PCI home runs are actual home-runs and it is just a bug in our hitting feedback code." Some statement like this would be much appreciated.
-
Not going to happen
-
@tvsectog_xbl said in Off PCI homers and Comment Regarding the Display Feedback Code versus the Actual Hitting Code:
Can SDS Engineering comment on the off-PCI homers? Personally, I think the issue is not really an issue, yet rather an offset/timing bug between the hitting engine code and the display code. I think sometimes that code that displays the hitting location displays slightly incorrectly in relation to the actual hitting engine code. The display code of the hitting feedback would be single-threaded code, dependent on the actual hitting engine code.
People often state that "this was an off-PCI home run", when in reality it probably was not, yet rather just that their is a bug in the hitting feedback display code that makes it look worse than it is. Some comment from SDS engineering regarding if there is a disconnect between the actual hitting engine code and the feedback display code would be great.
Maybe something that says "....The hitting display feedback is not always 100% correct, and sometimes displays off-PCI home runs, that are in-fact, actual home runs, yet just don't always display correctly. We are aware of the issue and it is a bug, yet rest assured, off-PCI home runs are actual home-runs and it is just a bug in our hitting feedback code." Some statement like this would be much appreciated.
Well it's hard to tell now that the opponent's PCI is not displayed on the feedback. I can say I have hit a few homeruns with feedback that showed my PCI didn't touch the ball and it sure felt like I missed it as well.
-
@chuck_dizzle29 said in Off PCI homers and Comment Regarding the Display Feedback Code versus the Actual Hitting Code:
@tvsectog_xbl said in Off PCI homers and Comment Regarding the Display Feedback Code versus the Actual Hitting Code:
Can SDS Engineering comment on the off-PCI homers? Personally, I think the issue is not really an issue, yet rather an offset/timing bug between the hitting engine code and the display code. I think sometimes that code that displays the hitting location displays slightly incorrectly in relation to the actual hitting engine code. The display code of the hitting feedback would be single-threaded code, dependent on the actual hitting engine code.
People often state that "this was an off-PCI home run", when in reality it probably was not, yet rather just that their is a bug in the hitting feedback display code that makes it look worse than it is. Some comment from SDS engineering regarding if there is a disconnect between the actual hitting engine code and the feedback display code would be great.
Maybe something that says "....The hitting display feedback is not always 100% correct, and sometimes displays off-PCI home runs, that are in-fact, actual home runs, yet just don't always display correctly. We are aware of the issue and it is a bug, yet rest assured, off-PCI home runs are actual home-runs and it is just a bug in our hitting feedback code." Some statement like this would be much appreciated.
Well it's hard to tell now that the opponent's PCI is not displayed on the feedback. I can say I have hit a few homeruns with feedback that showed my PCI didn't touch the ball and it sure felt like I missed it as well.
Fair point, as display code can be hard to predict. However, that is why SDS should just come out with a statement from engineering saying that "The feedback display code is approximate, and not always 100% correct, and that the hitting code is correct. Rest assured, that a hit is a hit, even if it looks incorrect in the Feedback Display Code." ....... and problem solved. That is all (or something similar) that SDS has to say, to put the issue to bed permantely. Just call a spade a spade and be done with it/never have to say another word about it. I would have to think that would make life easier on SDS.
-
I have always said its a problem with the feedback, but theres not way to tell for sure. You definitely won't get a comment from SDS though
-
@tvsectog_xbl said in Off PCI homers and Comment Regarding the Display Feedback Code versus the Actual Hitting Code:
@chuck_dizzle29 said in Off PCI homers and Comment Regarding the Display Feedback Code versus the Actual Hitting Code:
@tvsectog_xbl said in Off PCI homers and Comment Regarding the Display Feedback Code versus the Actual Hitting Code:
Can SDS Engineering comment on the off-PCI homers? Personally, I think the issue is not really an issue, yet rather an offset/timing bug between the hitting engine code and the display code. I think sometimes that code that displays the hitting location displays slightly incorrectly in relation to the actual hitting engine code. The display code of the hitting feedback would be single-threaded code, dependent on the actual hitting engine code.
People often state that "this was an off-PCI home run", when in reality it probably was not, yet rather just that their is a bug in the hitting feedback display code that makes it look worse than it is. Some comment from SDS engineering regarding if there is a disconnect between the actual hitting engine code and the feedback display code would be great.
Maybe something that says "....The hitting display feedback is not always 100% correct, and sometimes displays off-PCI home runs, that are in-fact, actual home runs, yet just don't always display correctly. We are aware of the issue and it is a bug, yet rest assured, off-PCI home runs are actual home-runs and it is just a bug in our hitting feedback code." Some statement like this would be much appreciated.
Well it's hard to tell now that the opponent's PCI is not displayed on the feedback. I can say I have hit a few homeruns with feedback that showed my PCI didn't touch the ball and it sure felt like I missed it as well.
Fair point, as display code can be hard to predict. However, that is why SDS should just come out with a statement from engineering saying that "The feedback display code is approximate, and not always 100% correct, and that the hitting code is correct. Rest assured, that a hit is a hit, even if it looks incorrect in the Feedback Display Code." ....... and problem solved. That is all (or something similar) that SDS has to say, to put the issue to bed permantely. Just call a spade a spade and be done with it/never have to say another word about it. I would have to think that would make life easier on SDS.
SDS has gone back and forth on this. For a long time you couldn't see the other player's PCI on feedback. They then added it and it's been around and a source of contention for a few years. It's now gone again.
I think that's SDS's subtle way of saying let's just forget about it
-
There's an upcoming gameplay feature reveal where they can probably talk about this directly at some point
-
A admin locked this topic on
