Jump to content

kupjones

Premium Member Tier II
  • Posts

    124
  • Joined

  • Last visited

  • Days Won

    4

Everything 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 when I reload #6, I get an executable from 2020 BUT -- that version actually loads and works python.log
  2. thats what I was thinking -- but, he hasnt responded so .......
  3. And what is telling you this?
  4. all fixed. Thanks!
  5. yes, I saw that. I wasnt aware that I was loading little helper until I went in to compare versions of PMOD -- which is why I went to reload everything!
  6. doing it right now .... I downloaded PMOD first from WG just to check versions -- was at the same one. Reloading the entire stack now.
  7. Used PMOD for ages -- zoomout now appears to be stuck at 100m.
  8. Oldskool needs to get up early and do some updating!! <grin>
  9. Confirmed -- it is MOE Extended. Turn off the TechTree support and you get the plain TechTree
  10. Soo, basically there is nothing to actual configure -- I'm not missing anything. If thats the case -- consider it ignored ;)
  11. @Aslain, I want to test removing all of my selected mods and just install OldSkool -- but I would rather not have to go back in and reselect things when I am done. Is there a way to save my current mod selection list and restore it after I am done?
  12. So ... Im not quite clear as to qhat the fix was. I will say - I do not use Spotted Messenger, but it sounds like there is a collision between the mod config pages.
  13. Ok, ran #4 -- still get the same. Im wondering if there is some data that is cached somewhere? and runnig the log archive tool still produces the error above but now the archive subdir is empty.
  14. Sounds good. thanks
  15. I actually tried that -- it errors out. I get no more info than that. What I got is atteched Aslains_WoT_Logs.zip
  16. Should there be any item to configure for OldSkool? All I get is a blank panel. Python log attached (XVM log empty) python.log xvm.log
  17. 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.
  18. 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.
  19. 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.
  20. What version of Aslain are you installing?
  21. 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.
  22. 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.
  23. 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.
  24. 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.
×
×
  • Create New...

Important Information

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