Jump to content

98whiteMC

Premium Member Tier III
  • Posts

    226
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by 98whiteMC

  1. I need a mod that will remove crew members from the barracks based on their skill level.  It is so time consuming to search and remove all of the 50% crew that the game keeps adding to my barracks.  It would be awesome to just remove them all with one-click.  Give me a drop down box with 100%, 75%, or 50% choice and let 'er rip.

  2. Had same problem with both 9.20 & 9.20b just like:

     

    1. Mescalito -  "get into battle and see the battle loading screen with the background image of the map. but i stays on that image and i don't see any tank only minimap works."
    • Pabnchew - " could see the OTM on the screen and they went into a free cam mode when I clicked the mouse"

    Xd out of game , restart in safe mode, resume game and everything is normal.

     

     

     

    Aslains_WoT_Logs.zip

    WoTerr.PNG

  3. So this problem just resurfaced.

     

    • Installed the 9.20 modpack (deselected tank highlighter).  Install was successful with no anomalies or errors
    • Game started me stuck in some weird zoom mode where the only things i could see were OTM's with map section in background.  no tanks were visible.
    • Started game in safe mode and it worked fine.
    • Tried to remove modpack and I could not remove the \res_mods\configs\xvm\Aslain folder due to patch.exe and fouled permissions again.
    • Restarted computer and was able to delete folder/file
    • Playing vanilla

    This is kinda scary when something is trashing permissions repeatedly.

     

     

  4. Did you restart your system?  If you did, and still cannot remove the files I would suggest you create a new user with full administrator privileges, restart your computer (not switch user, not log off), log in as new admin user and then try to delete the files.  Hope it helps.

  5. I had exact same problem.  Here's what I learned and how I fixed my system.

     

    - When the modpack has been successfully installed the directory \res_mods\configs\xvm\Aslain does NOT contain the file PATCH.EXE

    - When my install failed it produced the error shown below (from the installer - not from anti-virus) when it found that PATCH.EXE was already there, 

    - AND because the permissions were fouled up the installer could not move/delete/whatever it needed to do with that file.

     

    I fixed my system by the following

     

    * Restart system

    * Log in as administrator or account with administrator privileges

    * Delete the entire directory \res_mods\configs\xvm\Aslain

    * Perform another install of latest modpack being sure to select option to "Delete all previous mods from the game"

     

    Summary

     

    - At some point during a previous modpack install, something went wrong which caused the installation to either malfunction or finish prematurely.

    - The result of that occurrence was a corrupted file system in the aforementioned directory, where the permissions were broken and files remained that should not.

    - Prior to this issue I had not received any indication of any modpack install not being successful.

    - I have NO IDEA what actually caused the corruption, but my game works fine now .

     

     

     

    ModPack error.PNG

    • Upvote 3
  6. It's an error message generated by the installer.  The permissions on the Aslain directory containing the file patch.exe were broken.  I run as admin, tried explicit admin, tried everything I know about permissions to no avail. I restarted my system per Aslain and I was able to remove the directory.  I was then able to install the modpack without issues, HOWEVER, upon completion of the install there is no file called patch.exe in that folder now.  While the problem was clearly local, I think it was caused by the installer. I'm guessing that a previous install process did not terminate properly leaving some working files around on the disk.  Works now :), and thanks again to Aslain and all who help on this forum.

     

     

    ModPack error.PNG

  7. I've had this happen as well.  It always happens when the situation is very hectic and I am switching targets quickly.  However, I believe that I am really at fault here.  I think that the audio report (e.g, target acquired) is just too slow to keep pace with what is actually occurring.  So I click the button to lock, hear nothing, and assume that my reticle was not in place, so I click again and hear the unlock message......

     

    I'd like to see WG add an option to select tones to indicate the status of auto-lock instead of the lengthy messages, and the system could be more responsive.

     

     

    • Upvote 1
  8. Newbie, I also have the problem with the contact list never connecting, but the game works fine in all other aspects.  I did a little testing and here's what I found.  I have 2 systems running Tanks.

     

    System 1 has NEVER had any mods installed and has always been a vanilla client, and is my Alt account system

    System 2 has always used Aslain modpack and is my Primary account system.

    Both systems run identical OS/Anti-Virus/Malware/etc.......

     

    My Alt account contact list works FINE on both systems.

    My Primary account FAILS on both systems (contact list broken) even when NO mods are installed on either system

     

    These tests were run against both the East and West serves.

    I tried safe mode = FAIL

    I manually cleansed the mod directories = FAIL

    I tried at least ten combinations of mods = FAIL

    I did clean/delete installs each time = FAIL

     

    This has me convinced that that the modpack is not at fault, and neither is the game installation or the software config on either on my systems.  It seems to be something wrong with my account at Wargaming's end of things.  Also worth mention is that my Primary account contact list is pretty huge, and my alt account list is very small.  Maybe some new size limit is breaking it, and might explain why it happens to some and not others........

     

     

  9. I don't think that sixth sense has changed at all.

     

    *Prior to the new instant spotting mechanic introduced in 9.16, the amount of time that it took for your tank to get spotted was dependent on it's distance from the spotting tank.  So it was possible to poke out and see/shoot an enemy tank, then duck behind cover before your tank was illuminated by his.  So even though his tank did not illuminate you at that time......the system "saw your tank" and triggered the sixth sense timer.  So once you got into the hiding the 3 seconds was over and your warning went off.  This created the illusion that sixth sense was fast.

     

    Now your tank is spotted instantly, and the sixth sense timer starts immediately.  So this gives the enemy tanks the full 3 seconds to see and shoot you before the warning sounds.  This is why you are experiencing your issue.

     

    This new mechanic effectively rendered sixth sense useless IMO, and WG should either re-introduce a spotting delay, OR, shorten the delay timer on the sixth sense perk.  Doesn't seem fair to destroy the functionality of a perk for which some players spent gold to acquire it more quickly.

     

    *Based on my understanding of the game mechanics

    • Upvote 2
×
×
  • Create New...

Important Information

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