Forum Discussion
Both on WiFi or cellular data have this problem. And all maps will have this problem. And this only happen when I operate, so it's hard to record and provide a video.
I asked my friend, they have this situation when the net connection is not good. So I changed time to play game when the net connection is good. The game work fine and have no such situation. But for our players from China, we have an unstable net connection. Lag happens at any time. Maybe this is the problem.
Thanks for your help. Hope you can help to improve our unstable connetcion but we know it's really hard.
Hey @yehoshualee thanks for getting back to me. It does sound like it is related to your connection. ☹️ Have you and your friend tried restarting your WiFi router regularly? That could help performance for you? Let me know if that helps.
- 7 years ago
Finally I get a video of this bug. This is record game from Windows on Bluestacks. At 2 second, mouse clicked common aircraft at the bottom of map but failed. The common aircraft at the top moves down.
You can get it here:
https://drive.google.com/open?id=1687mzZpxmKyseDkR1mZG9BS7LQZHK62R
- EA_HighCommand7 years ago
EA QV Team
Hi @yehoshualee and thank you for the update.
Upon checking your video you had indeed selected the southern Banshee and ordered it to move but then you've built another Banshee which is then auto-selected by the game since it was the latest unit built. After you ordered the northern Banshee to move south you attempted to click the southern Banshee again but the northern Banshee was still selected, making it move.
The second mouse pointer is a bit confusing at this part tho. Did you click the southern Banshee just once or multiple times?
Is this also still happening on 1.4.1?
- 7 years ago
I think I recorded it on 1.4.1, but maybe on 1.4.0. I forget when I update to 1.4.1. And only click the southern Banshee once.
I find that it only happens when southern Banshee is moving, maybe at the time it move at the edge of two blocks.
On 1.3.2 it happens many times. I will test more on 1.4.1 to see if it still happens.