has anyone seen a bug like lets shut the game window but keep the game running
this happens quickly and often this has been happening since the last windows ten upgrade
ps still playing in win 7 if you are asking
has anyone seen a bug like lets shut the game window but keep the game running
this happens quickly and often this has been happening since the last windows ten upgrade
ps still playing in win 7 if you are asking
paca_madaidhean, on 27 January 2020 - 09:50 PM, said:
has anyone seen a bug like lets shut the game window but keep the game running
this happens quickly and often this has been happening since the last windows ten upgrade
ps still playing in win 7 if you are asking
Had the same, game wasn´t even visible in the task manager just an "wargaming error" task.
Restarting Gamecenter didnt solve the issue, restarting system did.
I don´t know for sure if it is to do with a new form of bug or not. I´ve been seeing server-disconnects in any team at any battle.This is happening constantly at every battle every day. Now It was my turn yesterday midnight when I just came back to hangar with victory, then, to my astonishment,another battle result had popped up in front of my eyes, where my team had lost and I made 1,000 PP only. The same plane.
The thing is I´ve never flown the latter battle at all. Neither can I recongize names of players of the both teams. Because I was not in there myself at my own will.( I keep a captured hangar screen of it) My server was working properly and at online.
There are several seconds´ time differecne betweeen these two battles. It is totally utterly impossible that I have flown 2 battles exactly at the same time. Typical numbers in those disconnects are , 0K & 1k PP 0 kill ,3 got killed. 0-critical hits, 0-gts
I duly suspect this might be the effect of a bug or, the WG might be doing this incessantly in order to mobilize and ulitize ghost persons.Or for lack of human players.
This is the main reason why I believe other players must be experiencing this nightmarish oddity.
regards,
Edited by Ykazumi, 06 February 2020 - 01:20 PM.
Looks like just a variation on a number of bugs that launches your plane in battle without you.
I have even left the queue and started another battle, only to get a result afterwards for the first battle I never was in ... even with the same plane.
Same for disconnected from server, client crash, endless-queue-of-death ...
You sure ?
Because I have left the queue and selected a plane (same or other) and entered another battle and only got 1 result afterwards ... only in rare cases do I get 2 results ; 1 for a battle I was not in, but my plane was and 1 for the battle I played ...
Ykazumi, on 06 February 2020 - 04:07 PM, said:
I don´t know for sure if it is to do with a new form of bug or not. I´ve been seeing server-disconnects in any team at any battle.This is happening constantly at every battle every day. Now It was my turn yesterday midnight when I just came back to hangar with victory, then, to my astonishment,another battle result had popped up in front of my eyes, where my team had lost and I made 1,000 PP only. The same plane.
The thing is I´ve never flown the latter battle at all. Neither can I recongize names of players of the both teams. Because I was not in there myself at my own will.( I keep a captured hangar screen of it) My server was working properly and at online.
There are several seconds´ time differecne betweeen these two battles. It is totally utterly impossible that I have flown 2 battles exactly at the same time. Typical numbers in those disconnects are , 0K & 1k PP 0 kill ,3 got killed. 0-critical hits, 0-gts
I duly suspect this might be the effect of a bug or, the WG might be doing this incessantly in order to mobilize and ulitize ghost persons.Or for lack of human players.
This is the main reason why I believe other players must be experiencing this nightmarish oddity.
regards,
Is it possible that you've left the queue for some reason and re-enter it afterward? It seems to me that you might've left the queue when your match had already been found and then joined another queue, and that caused a "ghost" battle.
0 members, 0 guests, 0 anonymous users