Jump to content

Kramarz

Premium Member Tier I
  • Posts

    34
  • Joined

  • Last visited

  • Country

    Ireland

Reputation

0 Neutral

About Kramarz

Profile Information

  • Server
    EU

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Never mind for now... I have marked few tanks as reserve, ran the installation again, and all went ok this time... no idea what happened.
  2. Well, I have just updated the modpack, while making sure "Delete game cache" is NOT to be used during installation. ...All my reserve tanks are no more. Any more ideas?
  3. "Vehicle parameters on single list" mod is breaking parameters list/updates on Field Modifications section. I love this mod, but if there's no update coming... should be removed I guess...
  4. Not sure which mod prevents that. Logs attached. Aslains_WoT_Logs.zip
  5. Well, fun fact - I'm the only user/admin of my PC. But with Windows you never are REALLY an admin.
  6. Ok... got it sorted... partially... Turns out I have to run WOT as administrator now... for whatever reason... to get everything working correctly... I still don't get it though why I am able to view this file after installing mods: ‪C:\Games\World_of_Tanks_EU\res_mods\1.11.0.0\scripts\client\gui\mods\mod_autoaim_indicator.json but I can't view it after PC restart? All I get is "ERROR Can not open file...", as I'm loosing read permissions to it... like it is getting blocked by windows firewall or something after PC restart... Gotta love Windows....
  7. Confused as hell... Hours spent... Full clear reinstall of wargaming center / wot / modpack done twice... nothing helps... Guess I'm stuck with it...
  8. Here's a weird one for ya. After each PC restart my mods are getting messed up. Tried checking for any windows problems / repaired client / reinstalled fresh modpack - nothing helps. I have to run modpack installation again and again after each PC restart to get it fixed till next restart. Attached screenshots of garage before restart and after, and logs for same. Any ideas? Oh, and there's that weird script error showing after restart as well, as seen on second screenshot. logs_before_pc_restart.zip logs_after_pc_restart.zip
  9. I have this error after each modpack update, but usually 1 relog gets rid of the error. This time though, no matter how many times I try to relog - error stays. Logs attached. Aslains_WoT_Logs.zip
  10. @Aslain Logs attached. Aslains_WoT_Logs.zip
  11. Anyone knows which mod is that? Arrow points to it, inside aim circle, some freaking extra pen indicator which I have not chose to use. https://ibb.co/SBN1Np8 EDIT: Or maybe it's part of new version of Jimbo V3?
  12. Exactly the same thing here. Plus, I can't close program with icon or Alt-F4. Found a way by moving WOT to 'New Desktop' and then closing in using Task Manager.
  13. Just had same issue, can't find any solution so far... besides PC restart...
  14. Thanks Aslain. Removed Hitzones and so far all good. Shame, as I like to have hitzones ON... Maybe will try again the other ones (although those always bug different tanks camos for me...) Will report back if the issue arise again.
×
×
  • Create New...

Important Information

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