Jump to content

kupjones

Premium Member Tier II
  • Posts

    124
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by kupjones

  1. Python file uploaded -- but the exact error line is below.  

     

     

    2021-03-09 23:03:53.187: INFO: [SL_PRO] starting loading script: "mod_stat.pyc" from res_mods folder
    2021-03-09 23:03:53.190: ERROR: [EXCEPTION] (<string>, 627):
    Traceback (most recent call last):
      File "<string>", line 614, in _findValidMODs
      File "scripts/common/Lib/importlib/__init__.py", line 37, in import_module
      File "D:\Mods\World_of_Tanks\SessionStatistics\mod_stat.py", line 1164, in <module>
      File "D:\Mods\World_of_Tanks\SessionStatistics\mod_stat.py", line 98, in __init__
      File "D:\Mods\World_of_Tanks\SessionStatistics\mod_stat.py", line 188, in readConfig
      File "scripts/common/Lib/codecs.py", line 878, in open
    IOError: [Errno 2] No such file or directory: '../res_mods/configs/wotstat/config.json'

    2021-03-09 23:03:53.190: INFO: [SL_PRO] skipped script in res_mods folder: mod_stat.pyc

     

     

    When I look at the version for wot_stat.pyc loaded under #8 I find an executable from 2019

    image.png.6a703f569f9dce08ad86528c5d53a276.png

     

    when I reload #6, I get an executable from 2020

    image.png.ae6dc26e4c992e06b030f44ff61ceb0c.png

    BUT -- that version actually loads and works

    image.png.78ebb73a46b32f65b10b27e6f1472c71.png

    python.log

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

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

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

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

×
×
  • Create New...

Important Information

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