Mana Games

[Azoak]

Hello Manu,

a player reacted to a ball that was clearly off the line and hit it back.
It happened multiple times in one match. It may be related to build 111 or recent changes.
(Sorry the GIF is small due to the file size limitation)

Hit_It_Back.gif (348.49 KiB) Viewed 6816 times

[Azoak]

Oh, sorry, this was the topic for Mahmut's problem, not a place for general bug reports. I would appreciate it if you could move my post to somewhere more appropriate...

[manutoo]

Hello,

could you send me a Bug Report the next time it happens ? (HowTo => topic5-31732.php )

[Burned]

I would add that the speed of the ball is exactly the same as the previous ball's speed.
A player hit a 65mph forehand that is out. The opponent may throw the ball back in play (while the line judge called the ball out and the score is going to be announced) at the same speed of 65 mph, exactly the same speed as the previous ball every time it happens. That can happen very often after a dropshot winner.
You can see that sometimes in real life too, so I thought this happened because Manutoo made it so.
I don't know if I'm talking about the same thing though, as I spotted that a long time ago.

Sorry for the disturbance, in case I'm talking about something different.

[Azoak]

Hello,
Thanks for moving my post!

could you send me a Bug Report the next time it happens ?

Sure! And since the log of this match was kept, I am sending the ZIP file. (Bottom of this post)
Here are the seven rallies you will see.

Game #3 (0-2)

0-0

0-30

Game #4 (0-3)

15-0

Game #5 (0-4)

0-0 (swing and miss of a smash)

40-30 (swing and miss of a volley)

Game #7 (1-5)

15-30 (the GIF)

30-30

I probably would not have pressed either strike button for a ball going off the line. So I assume these are Safe Strike. In two of Game #5, the ball did not hit the racket, but I don't think players have tried to swing in these situations before. (Except for the Warm-Up)
I didn't spend much time playing TE4 in March/April, so maybe the latest build isn't the cause. But for sure, in February I did not experience this.

- - - - - - - - - -

BugReport_Azoak.zip

(51.92 KiB) Downloaded 10 times

[manutoo]

Azoak,
indeed it was just from the last update, because of a change in the CPU handling when the ball is going out that unfortunately also affected the human behavior.
It'll be fixed in the next update, thanks to your report !

Burned,
I think you're talking about something completely different...