Jump to content

kupjones

Premium Member Tier II
  • Posts

    108
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by kupjones

  1. Are you also loading the Unanonymizer mod?

    17 hours ago, Hav0c said:

    I deleted the whole wot folder in %appdata% then reinstalled aslains. So far the mod is working and not hanging on a certain tank.

    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.

  2. 13 minutes ago, pabnchew said:

     

    You mean the folder roaming>wargaming>WOT folder via %appdata%  ???

     

     

    If it's the folder I just asked about I don't think it'll help.  I dumped it since Aux... got his mod fixed cause I was still having issues thinking it would fix it.  It didn't.   It also has all the history for some of your mods like the camo and gear stuff, so if you don't back it up then you start from zero.  Normally I back it, up but I used to use the other camo demount so Auxiillium was new to me and most my tanks weren't set up so no big deal.

     

    I uninstalled unanonymizer and the others mentioned and all the other garage mods I was running and still hanging up and pretty much every battle now unless I exit out early.  Hate to not run it, but the camo may have to go till it's sorted.   I honestly think that's it.    I even dumped stuff I didn't think would matter like friends notifier, Aslain's gold prems, the selected tank highligher, garage clock, etc...

     

    I play on NA but I went to EU and there's not  a peep in Auxillium's thread.  I'm gonna go through and delete some more mods and go from there.  If that doesn't work then I may try just the camo mod to see what happens.

    Yep, that cache and yep, doing so kills all prefs -- even WOT prefs.  

     

     

    12 minutes ago, ViperTC75 said:

    What seems to be clear to me is that the hang NEVER occurs when my tanks got preset styles on (2d/3d).

     

    Aux Auto Camo seems only to bug, if u put individual camo on.

     

    And I didn't have a hang for hundreds of battles now ... ranked is quite intensive.

     

    So I guess, preset styles are a workaround, too.

     

    And yes, I use Unanonymizer anyway - its no prob with preset styles.

     

     

    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.

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

    • Upvote 1
  4. 11 minutes ago, Pak63 said:

    The same thing happens to me, it hangs when I leave the battle when I wait until the end. If I go out before I finish without problem.
     

    python.log 292.12 kB · 0 downloads

    Aslains_WoT_Logs.zip 237.38 kB · 0 downloads

    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.

  5. 2 hours ago, pabnchew said:

    kupjones could very well be correct.   I've noticed Auxilliums really drags to load up even if I'm just going between tanks in the garage.   And I also do run the unanonymizer mod. 

     

    Some thoughts.   Has anyone had this issue if they exited from battle before it ended?  I've only had it if I hang around or am living at the end.  BUT I normally do that anyways, so I don't have any results where I exited battle early.   And even then the way it's so sporadic I don't know if that would help pin it down.  

     

    Just thinking if you exit early then all the after battle data isn't being compiled at the same time as you're exiting back into it and possibly also back into  a different camo scheme that was on the tank when you clicked battle.   That extra time swapping into a new camo into the garage could be putting the time over enough extra to trigger it or trigger it more often.  

     

    If I exit the game and go back in immediately it'll still be updating sometimes.  If I wait it out that doesn't happen.  That leans toward kupjones being correct.

     

    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. 

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

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

  8. 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!!"  ;)

     

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

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

    • Upvote 1
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.