Update 9.16: Bugs & Issues
Дата: 09.10.2016 22:10:48
Doh2x, on Oct 09 2016 - 14:41, said: 1) You may not like this answer, but your usual suspects
are your mods. You updated the client, but not your mods. It
usually takes some time for the mod developer to update and have it
be compatible with the latest version. Even if they update, mod
packs are a collection of mods. Not all of them will be
updated and will still cause issues with the game client.Now that
you have updated to the latest version of Aslains you are now
crashing less that's because it's a more stable version than its
predecessor. Mods don't help your system run World of Tanks, they
add more processes to an already process heavy game. It makes it
difficult for us to investigate the actual causes of unwanted
client behavior when mods are present. ***As I stated,
WITHOUT mods, CTD was occurring every 3-5 matches (to me, that's
unplayable)...WITH mod, CTD occurs much less frequently.
Trust me, I am very familiar w/how long it takes some modders
to update their product and I patiently wait, dealing w/the vanilla
client until such time that I can update the modpack. Aslain
has in the past been very quick to ID, then disable broken aspects
of his pack (one of the main reasons I utilize his collection
versus some others). 2) I know of an intermittent issue of
the client reopening after closing out of the game, but it is
usually stopped when you end the game's process through Task
Manager. Do you keep your crash logs or Windows event logs?
*** It's not intermittent if after every crash, the game
relaunches. Also, I shouldn't have to have TM up and running
to terminate processes that fail to terminate themselves 3)
WargamingGameUpdater.exe is not World of Tanks. It's an updater
file that keeps World of Tanks up to date. ***
You are correct WGU.exe is not WoT but why is it running
outside of WoT? Prior to 9.16, this line item was never seen
in my TM. And again, why is it running when WoT isnt?
And why will it not stay off?? I see no need for it to
be running 24/7, with or without WoT active. 4) This sounds
like a combination of latency + XVM. Do you have a replay where I
can review what you're seeing? *** I don't keep
replays, so not able to share my experience with you. I keep
XVM updated regularly, which fixed the "mini-map" issue,
thankfully, because that was really annoying.Saffr0n: Please confirm that you cleaned out the World of Tanks
directory of all mods before you updated to 9.16. Deleting the
outdated mod isn't the same thing. You have to uninstall it from
the directory. If you can't confirm this then you still had
outdated mod files in the World of Tanks directory, which still has
an effect on the client and will cause crashing. You stated that
you keep XVM updated regularly, which fixed the "mini-map" issue.
The minimap bug (the one that reverts minimap size for every
battle) is caused by an outdated version of XVM, which has
been confirmed by us and many in the mod community. If you were
experiencing this issue then you were running outdated mods on the
World of Tanks client. I wasn't inviting a debate, I really
want to take a look at your crash logs and event logs. Like I said,
I am aware of a particular issue, you're describing something
different so I need to have a look at those logs. We
introduced an option to keep the client updated. If you don't want
this option opt out in the launcher. This would be the least of
your worries since the updater isn't process heavy at all. Turn on
replays for 1 battle, I just need one to review.
Update 9.16: Bugs & Issues














