Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won

  • Country

    United States

HockeyPhool last won the day on September 14 2015

HockeyPhool had the most liked content!

Community Reputation

8 Neutral

About HockeyPhool

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Server
  • Location
    Colorado, USA
  • Interests
    ice hockey, cycling
  1. I recall seeing this issue a couple of weeks ago. I did not investigate it further, but I suspect it *may* be related to Nomogram's dynamic crosshairs. I quit using that crosshair because it was causing terrible graphics performance (especially in scenarios), and since I quit using it I haven't seen this issue either. The "keep_calm" dynamic crosshair is a good alternative. Maybe give that a try and see if this issue disappears as well.
  2. Well, shucks: I have *never* noticed the big gray "Select Crosshairs" button in the game settings! Sure enough, that's what's necessary to enable the crosshair I installed. FWIW: you have to select the "Type 1" static crosshair to see the Krab V3 crosshair. Thanks for pointing me in the right direction, Iceman! HockeyPhool
  3. Thanks for the reply, Iceman. I re-ran the installer with the preview window enabled, and I do not see any instructions like what you mentioned. However, I'll go take a look at in-game settings to see if there are any that make a difference. FWIW: The crosshair that I *do* get is not the WoWS default, nor is it like any of the ones depicted in the modpack installer. :-( HockeyPhool
  4. I have installed the WoWS modpack v7.12.0_05. I selected the Krab v3 crosshair when I installed the modpack, but the crosshair that's actually displayed is something else entirely as shown in the attached screenshot. Is there another mod I chose that's overriding my crosshair choice? I confess that I don't know the WoWS mods nearly as well as I do the WoT mods. I did completely uninstall the modpack and play a game without mods (and saw the default crosshair). I then reinstalled the modpack, played a game, and took the attached screenshot. Thanks! HockeyPhool Aslains_WoWs_Logs.zip
  5. I like to change the activation key from MOUSE2 to KEY_B, for one thing. There are several other options (such as always following the projectile, the key to activate projectile following), but I haven't found good documentation for all that they do.
  6. Good call, @Quaksen! I just start WoT, quit, and now the config file is present.
  7. Thanks, bubs. I'll give that a try this evening. However, I don't agree that it's "easy", because it means I have to remember to edit the configuration in-game every time I update my modpack. With a configuration file on-disk I can have a template with my desired configuration and then use WinMerge to apply my changes to the mod config. I'm already doing that as part of installing the modpack.
  8. For some reason, the installation of the "Battle Assistant" mod does not always leave a configuration file. At one point in the past two days I found the configuration file here: c:\Games\World_of_Tanks\mods\configs\battle_assistant\mod_battle_assistant.txt However, I just installed 1.0.0_06 and there is no configuration file for this mod. I went back and reinstalled 1.0.0_03 and 1.0.0_05 to see if either of those versions left behind the config file, but neither of them did. I can't explain why there *was* a file the other day, and I don't understand the new mod packaging enough to investigate further. I can see in the installer log that the mod *was* installed, and I confirmed that the mod works with the default activation button (MOUSE2). I realize this may not be an issue with Aslain's installer but with the original mod. I cannot find any way to contact the mod authors on the Armor Inspector website or I would raise the issue with them as well. Aslains_WoT_Logs.zip
  9. Thanks for reminding me that I have Malwarebytes running. I just added 'res_mods/configs' as an exclusion and will see if that resolves the issue over the next few modpack installs.
  10. I cannot install WoT modpack v9.19.1_09. After selecting options and beginning the installation, the installer attempts to extract the binaries 'sed.exe' and 'patch.exe' in the Aslain's XVM configuration folder. It keeps throwing the errors found in the attached screenshots. It's complaining that it cannot rename a file in the destination directory and that the file already exists. I have tried the following without success: Clicking "Ignore". The installation finishes, but not all of the modpack is correctly installed (no carousel configs, tank icons are reversed for enemy team, no hitlog or damagelog, etc). Deleting the existing file, then clicking "Retry". The installer extracts the file but immediately re-throws the same error. Clicking "Abort". The installer rolls back its changes and exits. I'm attaching logs, and am going to install the previous version of the modpack to see if it will still work. I had to attach logs manually because the Archiver app failed because it couldn't reinstall 7za.exe UPDATE: I restarted my computer and was able to install v9.19.1_09 successfully. That's not a pleasant workaround, though> HockeyPhool _Aslains_Installer.log _Aslains_Installer_CompList.log _Aslains_Installer_Extractor.log python.log
  11. Hey there Capt Black! I'd love to have your steam code for The Witness! HockeyPhool
  12. The one time it happened it started at battle loading - no pre-battle summary although I could hear the countdown timer.
  • Create New...

Important Information

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