kupjones

<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.

I'll be standing by

I have to be honest here -- losing control *usually* means packet loss even though the game client is still running. Download PingPlotter and point it to, say, Google and see if it reports any loss in the path. If it does then you can use the trace to "backwalk" toward you until you identify the source of the loss. In the past the loss was right at the WOT NA game servers and I spent months sending then traces and telling them exactly which piece of hardware was showing the loss. WG ended up moving to Central US off the East coast and things have been better sicen. Good Luck Try installing a virgin copy of WOT via the Game Center, then try that copy. I wish Game Center would allow us to rename the game instance but it doesnt (at least I havent found a way) so you have to remember which instance it is as they are assigned a number.

LOL -- I guess I missed that part in your original post, sorry. And for Aslain to look at it you have to upload the python.log file. I've never seen the archiver *not* do its thing, so no idea why that wouldnt do it. Follow this link

I assume this behavior does not happen in vanilla (safe) mode?

Post back if you need any additional help. I've set this topic to notify me when there are updates.

If there is no obvious error in the log file then I start by renaming "mod" first to see if a packaged mod is the culprit. If a crash continues I revert back and rename "resmods" and repeat. That at least helps home in on the class of mod first (packaged or not). Then start disabling mods one at a time. BTW, I have found that sound mods typically are the most bugged mods -- although I did discover recently that an external python script for XVM was causing a problem in that it was outdated. I forgot my first rule of python -- everything is evaluated, regardless of whether or not the code is actually used. I caught the error in the python.log file.

Doesnt that always seem to be the case with event hangers????? Sigh.

.... Ok, I added Custom Manager back in after the 1.6.0.1 patch --- and it seems to be operating now as expected, but I'll keep working with it to see. One thing I noticed that is different -- when switching to "Exterior" mode there is a pause, the tank disappears from the "garage" (now the festival), one only sees the festival and a shadow where the tank was, then we switch into the Exterior modification mode. Before all I saw was an immediate switch into that tunnel area. I'm thinking WG did something odd and then "fixed" it in the recent patch.

Yes, very strange. Is there a way to add some additional debugging that can be enabled/disabled through a JSON config file? This only occurs in the hanger ....