for some reason when i started hosting a mission 2 days ago, i clicked the fire button multiple times but for some reason my spacecraft was shooting in the opposite direction… (I’m not joking)
(The first wave forced my spacecraft to rotate 180°, i think it was “Zig Zag”, this problem fixed itself when i flew this mission again, and sorry i couldn’t record this and i don’t remember the mission name…)
Did this happen due to a problem with my device’s performance or was it a bug?
Although this could be a legitimate bug, your device has a history of weird behaviour that makes it possible that it’s a problem with the device itself and not the game. I don’t know what it could be, though… bad memory? Some sort of malware?
If anyone else notices this bug on “ZigZag” (or any other game), please report it immediately.
He forgot to post the error message itself for some reason.
I assume that the upgrade from 10 to 11 broke some DirectX components. I’ve seen this happening before already, and other people say that 11 might also behave like that on a fresh system sometimes.
I’ve gone through the code and I can’t see where these surrenders came from. It’s possible that during the very early games of multiplayer (v.91-v.94), there were bugs or at least a different way to handle results (for example, from the changelog I see that “PARTIAL” results were added later) and some of your early missions were counted under those rules.
Did you notice when those surrenders first appeared in your stats?
Definitely let me know if you notice it increasing again.
At the time of the update, all Galactic Cup knockout matches of that day will be reset. If you have already flown your knockout match, you will need to fly it again.