Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/11/14 in all areas

  1. v3.8.10 (11-08-2014): - changed expD config so it won't spam to chat - fixed update checker built-in the installer - updated the update checker - updated expD v.2.2 - Hitlog & InBattle WN8 Calculator - added Marked undestructible structures (DLC) - re-added KT's engine sounds and gun sounds (DLC)
    2 points
  2. Hello everyone! I've noticed a few things that many people often miss about Aslain's Mod Pack. In this Thread, I will discuss them in detail. I hope this is of some use! The topics that I will cover are: Basic Installation PSA Mixing Aslain's Mod Pack with other mod packs Files that Aslain's Mod Pack leaves behind in your Game Client. Partial Un-installation In-game Crashes and Freezes Other Information [basic Installation PSA] Whilst downloading Aslain's Mod Pack, there will not be a shortcut on the Desktop. If you are planning on using the same version of the installer in the future, go to your Downloads folder, and Create a Shortcut on your Desktop. This is also where you can access all versions of Aslain's Mod Pack that you have downloaded in the past. You may select the installer's language upon start-up. You may not change the language once you have gone past the Language pop-up. If you have selected the wrong language, turn off the installer, and turn it back on again. You will then be able to select the correct language. If Google Chrome says that Aslain's Mod Pack contains a virus, don't believe it! Google Chrome often sends off false alarms. Aslain's mod-pack is absolutely safe to use. If you cancel the installation of selected mods in the middle of the process, some traces of the modifications may remain. In order to remove these, simply go to your res_mods folder and delete them, or run a clean installation next time you download mods. [Mixing Aslain's Mod Pack with other mod packs] You can use multiple mod packs with your game client. In order to avoid conflicts, make sure that you're not installing the same mod twice, or installing an out-dated mod with a different mod pack. As long as you're installing different mods, and up-to-date mods, there should be no conflicts. You may notice that some other mod packs have similar lay-outs to Aslain's installer. Make sure that you read the buttons carefully. Some other mod pack authors use similar appearances, but may place certain buttons in different locations. Double check what you are pressing! This applies to Aslain's Mod Pack too! Other mod packs may or may not over-write mods that Aslain's Mod Pack has installed. Chances are, they will over-write and update your current mods. If this does not happen, un-install Aslain's Mod Pack, and remove any traces of it. [Files that Aslain's Mod Pack leaves behind in your Client] There are several different files that Aslain's Mod Pack will leave behind in your Client. The file names are: Aslains_Downloaded_FilesThis is where all of the archived Downloadable Content (DLC) files end up after you finish installing Aslain's Mod Pack. If you wish to remove Aslain's Mod Pack in the future, but keep one of these mods, simply drag the appropriate RAR file to your Desktop. _Aslains_InstallerThis is the text file that the Installer creates and leaves behind whilst installing your mods. This is essentially an event log of everything that the installer has done. _Aslains_Installer_CompListThis is a ReadMe file of all of the most recently installed mods and selected options. If for whatever reason Aslain's Mod Pack does not detect your most previously saved settings (usually due to a cache clearing), then this ReadMe file is where you can find exactly which mods and options you had selected. _Aslains_Installer_Options (Setup Information)This file also states which mods you had most recently installed. However, this is a file that Aslain's Mod Pack may read and use to pre-set these settings the next time you run a Custom Installation (if I am correct) _Aslains_Installer_Options (Text file)This is a Text File for Aslain's Installer. This file is not directly used by Aslain's Mod Pack, rather it's a remainder after an installation has been run. It's essentially a text file of the Setup information. unins001This is the un-installation wizard for Aslain's Mod Pack. Double click on it and follow the steps to remove Aslain's Mod Pack from your computer. You might also see a file called: IMPORTANT REGARDING THIS VERSIONThis file is left behind by GnomeFather's Historical Realism Gun Sounds Mod. Since GnomeFather's Mod is part of DLC, Aslain's Installer uses all of the files that GnomeFarther left behind in his mod, including the Read Me file. Deleting it will have absolutely no effect on your computer. [Partial Un-installation] If you want to un-install only some of the mods within Aslain's Mod Pack, you have two options. Manually look through your res_mods folder and remove the un-wanted modifications Run Aslain's Mod Pack again, except de-selcect all of the mods that you do not want. Make sure that your desired mods are still selected, and then run a Clean Installation. This will remove the un-wanted mods, and will re-install the mods that you want to keep. [in-Game Crashes and Freezes] If you are experience crashes and/or freezes in-game, there is most likely a conflict with some of the mods that you have installed. For example, if you install several different sound mods of the same type, an internal conflict error may occur and cause your game to crash. The sound mods are most likely responsible for any freezing that you will experience; especially GnomeFather's Sound Mod. Whilst known as a great mod, it is notorious for causing a screen-freeze for a few seconds whenever multiple tanks are spotted in the beginning of the battle. If your game begins crashing, this is either caused by a mod conflict (perhaps a sound mod conflict, or a conflict with other mods you had previously installed, or your computer may have ran out of memory. If you heavily mod your Game Client, and put a lot of stress on your processor, your game (whilst uncommon) may crash. Sound mods and lighting mods usually are the causes of these kinds of crashes. [Other Information] If you are experiencing a problem with Aslain's Mod Pack, you should first try a Clean installation, as well as clear your World of Tanks and Installer Cache files. If this does not work, upload your CompList and Installer Text File, and someone may be able to help resolve your issue. If you have pinned Aslain's European Forum Thread for download convenience, you should consider pinning Aslain.com instead, since Aslain has moved his download link here. If I made any errors or missed something, please let me know; and I will fix it immediately!
    1 point
  3. For the second installment of my "No Duh" PSA series, I will be covering Team Killing, how to avoid it, and what to do if someone is trying to team kill you. How to avoid accidental Team Kills: First thing's first. Sometimes, you accidentally team kill an ally. However, it is avoidable. The easiest way to avoid Team Killing is to pay attention to your surroundings. Occasionally look around your tank, check the mini-map, etc. Not only will that make sure that you're not flanked by enemies, but it will also help you see any allies that may be trying to drive past your gun. Also, don't drive in Sniper Mode. That is a literal example of tunnel vision, which will make it extremely difficult to notice your own scouts and mediums driving by. In addition, if someone is face-hugging a tank, don't shoot unless you have a clear shot at the enemy, and don't risk hitting the ally. Remember - if even a small part of your aiming circle is displayed over an ally, then there is a chance that you might hit him/her. How to avoid being Team Killed: Pay attention to where you allies are pointing their guns. If the gun appears to be locked on target, don't drive past it unless the ally just fired a shot (and has a somewhat long reload). Otherwise, simply drive around the ally. In addition, avoid face-hugging enemies that are being shot at from all directions. This will only put you directly into your ally's line of fire, and there is a significant chance that your snipers or artillery may end up hitting you. If someone tries to Team Kill you: DON'T SHOOT BACK! After the ally shoots you 3 times, he will turn blue and receive a ban. If someone begins shooting you, don't shoot back. Let them earn a ban. Also, add the player to your Ignore List (Ctrl + Right click on a player's name, then press Ignore), save the replay (Enable Battle Recording in Settings), and send it in to Customer Support (https://na.wargaming.net/support/Tickets/Submit). Saved replays are found within the following directory: C:/Games/World of Tanks/replays If someone is blocking your way: Add the player to your Ignore List, and send in a ticket to Customer Support. If the ally is preventing you from getting anywhere, you have five options: Load an HE shell, and shoot the ally once in his tracks. This will immobilize him and allow you to move on. Ask an ally to load an HE shell and shoot his tracks. Wiggle around the ally; figure out a way to get around him. Lead the ally that is blocking your way to enemy fire. It sounds mean, but if he's doing his all to stop your team from winning, it would be best if he got destroyed. Lead him to the enemies, and let them take care of him for you. Pretend to go AFK. Trolls try to annoy other players. If you pretend to go AFK, then the troll will not receive the kind of response that he wants; thus he will most likely leave. Regardless, DON'T try to team kill the ally, don't cuss in chat, and don't shoot his tracks more than once. Also, remember: If you shoot at an ally, you risk a ban. Shooting an ally once is usually forgiven by the server; sometimes it doesn't even yield a fine. This is why I say load an HE shell and shoot the tracks of the ally who is blocking your way. You won't risk a ban, and it will immobilize the ally; thus allowing you to escape... as long as you did it once, and once only. If an ally is being circled by an enemy: Remember the ranges that you're shooting at, and the type of ammunition you're shooting with. If you're in an artillery, don't shoot at any enemy nearby an ally unless it is the ally's last hope of survival. Also, if you're shooting high caliber HE shells, such as when in the KV-2, make sure that you will hit the enemy; otherwise you greatly risk destroying the ally, or at least dealing splash damage to him. In addition, remember that your shell takes time to reach the enemy if you are sniping at range. Take this into consideration when aiming your shot. Try to ensure that you aim slightly ahead of the enemy so he will drive into the shot. However, if aiming ahead of the enemy would require pointing your gun directly at the ally, don't do it! If an ally is circling an enemy: Here are a few images that demonstrate where you are safe to shoot, where you should be cautious whilst firing, and where you should avoid shooting in certain scenarios: (Green is safe to shoot, yellow is be cautious [especially if the ally is moving], red is a "don't shoot zone". The green star is an ally, red star is an enemy, and the blue triangle is you.) Additional Information: There is a known glitch where your bullets may exit your gun barrel at a 45 degree angle if you just finished rotating your turret whilst driving your tank at a high speed. There are two ways to avoid shooting shots at strange angles due to this glitch: Enable Server Reticle in your Game Client's Settings Don't shoot immediately after rotating your turret at a high speed. Give the gun an additional half a second, up to 1 second, and you will most likely eliminate the possibility of a strange shot.
    1 point
  4. LOADINF for Aslain's Installer v2.7.1 ( GUI ) DOWNLOAD (GitHub - source code) [VirusTotal] On each installation, the installer saves user selections to a file located in the following example location: c:\Games\World_of_Tanks_EU\Aslain_Modpack_Aslains_Installer_Options.inf You can use this LoadInf application to load those selections again into the modpack. For instance, if you want to back up your settings in case you are reinstalling Windows or transferring Aslain's stuff to another computer. If, for some reason, the LoadInf isn't sufficient for your needs, there is an alternative method for transferring settings from one PC to another. This method is more suitable for advanced users. The process involves exporting and then importing this Windows Registry key for: WoT: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Aslains_WoT_Modpack_Installer_is1 WoWs: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Aslains_WoWs_Modpack_Installer_is1 The modpack installer is now automatically creating a Windows registry file. You can find it in the Aslain_Modpack folder as _Aslains_WoT_Modpack_Exported_Settings.reg or _Aslains_WoWs_Modpack_Exported_Settings.reg. Copy it to a new PC and execute it (might require admin rights). Then launch the installer, select the proper path, and install. README: Changelog: v2.7.1 - Changed some messages, for better understanding - Changed the pictures to some lighter ones
    1 point
  5. ok, got it... between the 2 of you I now understand to just keep doing it the way I have... Thank you both very much. You both reconfirm why this mod pack is the ONLY thing I will donate real money for, to have the kind of support that you provide. Again, thank you for your support.
    1 point
  6. Hello , For starters: Normal Installation - This is NOT recommended - -it copies the new content ( mods , xvm ) over the old res_mods ( Like a copy - paste- replace ) Clean Install -FULL - This is highly recommended - -it removes everything from the res_mods folder , that it copies the new content into that fresh res_mods :D Clean install - PARTIAL - This is moderate recommended - -this options removes everything from the 0.9.x folder , inside the res_mods , but it leaves the xvm folder... so it will overwrite the xvm files on update... So in the end ... i must say that the best option is to use the Clean Install - FULL - ( it's usually fail-proof )
    1 point
  7. OMG this was so obvious.... You know why it disconnects you guys? Because WoT replays must be played in offline mode :) In the garage when logged in, all you can is to review list of replays with some details, but you cannot play, when you try to play it, it will disconnect you, to help it :) Once disconnected click on replay manager icon again (on the login page) and then you can play a replay.
    1 point
  8. thk so much.. is everything on the same line, but i found where to put false instead true.. thk dude :) ;)
    1 point
×
×
  • Create New...

Important Information

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