kupjones

Are you also loading the Unanonymizer mod? WOT stores quite a bit of cached data there. I've had to do the same in the past just to get back to a zero-install.

Yep, that cache and yep, doing so kills all prefs -- even WOT prefs. Interesting. After removing Unanon I am having zero (knock on wood) problems -- normal camo as well as styles -- with Aux still running and return to garage is zippy quick.

I hate to say this -- but I have had to completely dump the WOT cache + game folder and start all over. Some things I could not repair.

What version of Aslain are you installing?

PLEASE NOTE: I am *NOT* saying the Unanonymizer is the offending mod -- I truly believe it to be Auxilium and the way it is written; Auxilium appears to be consuming PC resources, more than I typically see with other mods. Its just that I could do without Unanonymizer and Auxilium camo changer is a must have. It was a simple choice.

Are you running Auxilium and the Unanonymizer? EDIT -- Yes you are: [SL_PRO] starting loading script: "mod_unanonymizer.pyc" from: "rajcel.unanonymizer.wotmod" Re-run Aslain installer and uncheck Unanonymizer. Now see if that fixes it.

You know, I have *never* had the lockup happen when I exited early -- it is always when one normally exits, either waiting around or a normal loss/win. That was what started bugging me -- it really seemed like a timeout issue.

Still having issues?

I would try removing this first InBattle WN8/EFF Calculator [ProTanki] Info: WN8 + DMG + EFF + CREDITS These were known to cause issues I also know I was having issues with this YasenKrasen session stats But only make one change at a time.

<drive>:\Games\World_of_Tanks_NA\Aslain_Modpack

post that file -- the clue might be in there

Well, crap. So, what seems to be happening is Auxilium is a very hungry mod -- it takes up quite a bit of time to do its stuff. I was looking at the docs and the Unanonymizer apparently takes quite a bit of time at the end of a battle and it occurred to me that the two just might be causing a timeout or even stepping on each other. I removed Unanonymizer and I have (so far) not had any lockups. Maybe the way to do this with your is see just exactly which mods you are loading -- _Aslains_Installer_CompList.log shows what you selected and is being loaded -- perhaps there is another mod that is interacting with Auxilium, but one that I do not run. Of course, all of this is conjecture based on my running this setup (without Unanonymizer) last night and this morning.

One question: are you running the Unanonymizer mod by chance?

So far no lockups. only change -- disabled entire Auxilium mod Next, re-enable it and see what happens

Today I removed Auxilium and played a few battles -- never a hang. I will keep it this way and see what happens, but I suspect Auxilium and there being some Aux routine that is taking too long. I do know that Auxilium takes an incredible (comparatively) amount of time switching tanks, perhaps there is some amount of inefficiency that is causing the game client to time out. Sadly, there is little help in the python log. We would need a log creating by Auxilium I would think.

I always thought this was an XVM bug .....................

Yep, you've been bit by the "WG Updated the Game in the middle of the night" malware. Aslain has the antidote coming - version 1.9.0.2

Apparently something (no idea what) was blocking any attempt at cleaning up utilities -- "sed" and "patch". I tried manually removing them and was getting blocked -- so I did a PC reboot. Whatever it was cleared up. I successfully ran the mod installer again and it was able to clean up after itself. I've only run into this a couple of times in the past -- not often enough for me to immediately go "Aha!" but enough for me to eventually remember to do a reboot. So, I release this time back to you -- and "Wash Your Hands!!" ;)

Not a bug, but a question. I found an .EXE in the res_mods dir, and that .EXE was not there in the last release (I keep histories of all updates). An artifact left behind by the mod installer?

At least you managed to get them back. I cannot explain why your depot was still empty on a completely different PC -- unless when you say "no change" you meant the items didnt return to your tanks. The way these mods work, they build a local DB of which items are installed on which tanks, pulling from you Depot inventory. What happens sometimes is a new mod pack install will wipe the DB meaning you have to start over. But at no point do these ever sell your items. Nevertheless, seeing your hard earned stuff back in the Depot is a good thing.

Yep, not just you

My understanding of how the WOT client works, nothing is maintained on you local PC other than caches -- meaning, your stuff should still be there you just cant see it. This is evidenced by virtue of logging into you account from a friends PC and your stuff shows up. Have you tried loading WOT onto a completely separate PC, logging in, and seeing if in fact your stuff shows up in your depot? Only way to empty your depot is to sell your stuff -- and I assume your bank account is not larger.

I was having the same issue -- turned out to be an old mod that I had created that included SWF's that have worked for multiple patches -- but finally got in the way. this may not apply to you -- but oddly I was seeing the same behavior. Make sure you do not have any old "favorite" mods in use.

I have to admit -- it is quite difficult to see, I have missed the "+" on several occasions. I did not look to see if the brightness or color were modifiable.

Sounds like mod troubleshooting 101 is needed.