kommador8t8

Just go to gmail.com or yahoo.com, or whatever email provider you prefer. Sign up for a new email account, then create the account on the world of tanks website using your new email address as the login. Problem solved, as you will now have two accounts available for use in any Wargaming game

Updated to the newest mod file update, 9.13.18, and the frozen loading screen stopped. I didn't even change any mod selections, must have just been an odd install or something. Thanks for the input though, much appreciated!!!

Is it possible that you could tell me exactly what mods you removed? I have the same problem every now and then after updating to the last patch (9.13.17). The game CTDs, then when I reload, I get stuck on that same loading screen with the exact same issues (which is funny because I can still rotate the screen, zoom in and out, and see the names of tanks that are spotted). I know that 9.13.18 is out, but I would not be surprised if the issue continues.

I've had it where once I came out of arty view, I could move forward and backward, and could turn my gun barrel, but could not turn the treads on my tank. Still ended up shotgunning two people haha

Hmm, didn't realize that it was such a widespread problem. Yay for WG's quality control.......

I know, I know, nobody likes it when artillery is played. However, it's sometimes fun to climb inside one and nuke some tanks in order to avenge your million deaths due to rediculous artillery shots. However, since the latest WOT patch, whenever I am in artillery mode, the gun constraints of my SPG lag. Turning left and right with the keyboard won't respond for a couple seconds, then slowly moves and goes WAY past where it is supposed to. It is making it really difficult to aim ahead of players when they are moving quickly towards one of the gun constraints. I can still move the reticle around fine, it responds normally. It's just the gun contraints (the cone/gun limits of angle) that lag behind. I have tried different reticles (i.e. Meltymath, Deegie's etc.), those aren't the issue. I am thinking that it may be the "Artillery crosshair on minimap" mod (the one that allows you to have a certain crosshair display on the minimap), but I have not had much time to try experimenting with mods to solve the problem. Is anyone else having this issue? python.log _Aslain_logs.zip

That is exactly how I edited my file to show the new render distance. The hex code at the end can be changed to any color you choose, just pull up a list online if you do not know them by heart. I used to do that to my old XVM files back in the day. To get to the minimapCircles.xc file, go to your WOT install location. Then click on: res_mods > configs > xvm > Aslain. Open the file with notepad, then find where it says "View". Under there will be a number that says "445". Just change that to 564, and you will be set. You can change any value in that line and the game will respond without any errors. Just note that you must have the client closed before attempting!

Unchecking the "Check for update in garage" at the very top of the mod selection screen will solve the crash issue at login. Props to Prometh3us for providing me with this solution!

Any ideas about this one? I get it every now and then. The game freezes on me mid-battle, so of course I open task manager and force-quit WOT (TM says WOT is not responding). When I reopen the game, it is stuck on the battle loading screen, but I can zoom in my reticle and see the outlines for it, can see enemy and friendly tank names, but no movement is allowed by my tank (can't see my tank). Look carefully at the battle loading screen, you can see the reticle through it. Because it happens VERY randomly, I'm suspecting that it might be an issue on my end (computer hardware/software), but any help from anyone would be appreciated if you've had this similar issue. I'm running 16Gb of ram, so I doubt that's the issue :P python.log _Aslain_logs.zip

Isn't that what the GTO Pen marker is supposed to do? I have always compared the sound to that of shooting someone in the COD games, the odd "fff-t, fff-t" sound that happens when your bullet connects

Mine currently works. Depending on when you last updated, there have been some new changes in the past few mod packs as far as the hit logs/damage logs/battle stats are concerned. They have all been broken down into separate trees. You now have to select each one individually, and select which side of the screen you want the wn8 estimator to appear. I hope that it's not a PC problem on your end, as I find the estimations to be quite useful. Best of luck!

Norton flags it too, and I tell it that it's a trusted file (just annoying, have to do it with each updated modpack -_- ). I know that Aslain's files aren't viruses, but man he could be the biggest internet troll and slide a little meme into it (possible April Fool's joke?) that opens with the installer. I would get a good laugh at it haha.

Solved the problem. Seems as though the Deegie’s Sights GKstd Remake cross hair mod was causing my client to crash. I have NEVER had a problem with this mod until 9.10 came out. Been using it since 8.~~ without any problems, and I really LOVE that cross hair due to the color changes (green if can hit, yellow if not). Switched to Melty Math's Mod (cross hair) and I have been playing all day (72 battles) without any problems. That's too bad, wish the Deegie’s Sights GKstd Remake cross hair mod was working for me :/

Hey all. I'm coming here for help because I know this forum is full of helpful people. Ever since WOT updated to 9.10, I have had issues with CTDs. Vanilla does not cause crashes, but a certain mod might be doing it. I had this similar issue when WOT updated to 8.7 and 8.8. All I did to solve that was do a fresh reinstall of the WOT client, reinstall the mods, and the problem was solved. However, this solution has not worked since the latest patch. I have tried removing a few of the mods that other people are saying cause crashes, but still have no luck. The client crashes randomly, but typically anywhere from every 5-10 games. If I restart my client within that window (before it crashes), it seems to "refresh" the "crash clock", and I am safe for a handful more games. CTDs occur randomly. Typically they are during battle, when loading into battle, or immediately after battles end. But never in the garage. I do not know how to read the python.log file, but I seem to be getting the same string of "error code" over and over again. In another forum, it was said that that certain code was harmless, so I am a little confused. Short of choosing one mod, then slowly adding them one-by-one, I do not currently have a solution. I have played with and without Spoter mods, and the crashes still occur. White Tank Death, with and without, and the crashes still occur. Any ideas? python.log _Aslains_Installer.log _Aslains_Installer_CompList.log _Aslains_Installer_Options.inf

I do believe this was tackled when you first introduced the "legal" version of minimap tankview extended. There was a WG employee that stated that the minimap tankview extended was legal for NA servers because it was no different than a tank being spotted by a team mate, and your team mate is typing to the team or talking and saying that said enemy is aiming, reloading etc. The problem arises when enemy tanks are actively shown on the minimap without being spotted and without being in your 500m max render range (i.e. Warpack). As long as the enemy tank is in your 500m render range, it is perfectly legal for the minimap to display enemy FOV. http://aslain.com/index.php?/topic/2951-minimap-tankview-extended/?hl=%2Bminimap+%2Btankview

Yes, some users had issues where the Autoaim indication+ and the Autoaim extended by Spoter, when used in conjunction, would cause the Autoaim indication+ to twitch the reticle and make it misbehave (made aiming a chore). The large issue was that some users could not snap the reticle to any target. You can use both of them at the same time, you just have to find Spoter's Autoaim extended mod and manually place it into your mods folder. Do so at your own risk, but that is the workaround if you so choose.

A few patches ago, yes, that was the problem, and Aslain addressed it immediately by reverting to an older and working version of the mod. I don't experience the snapshot function misbehaving this time, but it is the "repair with the T button" that is really a large problem. Like I had stated, the button does not execute the repair kit. Instead, the repair kit acts as an automatic fire extinguisher of sorts and just pops off whenever something is destroyed and has a repair timer attached to it (red modules versus orange modules that still work but at half capacity). I have tested the modpack without the autoaim indication+, and the auto-repair went away (which was nice). However, because the vanilla WOT snapshot coding is half broken and decides when/not to work, I almost have to rely on the Autoaim indication+ mod in order to snapshot something nowadays.

I believe the larger issue is that many users are experiencing an "auto repair" of sorts with the new Autoaim indication+. It is automatically using repair kits without any buttons being pressed, when most of the time the need does not exist. I find it mostly annoying partially because I like saving repair kits for my ammo rack, gun, and turret since I have fully trained repair skills on almost all of my tanks (tracks are repaired in 4-5 seconds on average).

I do believe that the automatic repair is attached to the updated autoaim mod (the one that allows you to snap your reticle to tanks without being fully on them). If you read the mod description, it says something about repair kit or tracks and a "T". I find it extremely annoying, especially when I don't need/want to use my repair kit at that given moment.

Hey guys, sometimes when there is an update to the game and you try and install mods, you may have to uninstall the game entirely and reinstall from scratch. THEN, reinstall the mods after the fresh install has finished. I have had this problem in the past, but luckily not this time around.

Hopefully this comes back up soon, as I do enjoy using the OTM reload!

Now, before I go into detail, I have not tried using the Jahral's panel from the 4.4.13 patch. However, in the 4.4.1x-12 updates, the Jahral's panel would act odd at some points in time. Healthy icons for the crew/modules are grey, injured/damaged are orange. Sometimes the icons for the crew or modules would not turn from grey to orange when they are injured/damaged. I don't know if anyone else has had this issue, but a couple of my clan mates were reporting the same problem after I had them try out the damage panel. It was getting rather annoying when I realized my tank was moving slower than normal, or my aim circle was slow, but the Jahral's panel was not displaying the damaged crew/modules correctly. I switched over the the Shtys (or however you spell it) damage panel, and that one works just fine. Although.....I do like the little stacks of coins/gold in the Jahral's panel that tell me if I'm being hit by standard/prem ammunition versus the colored text that Shtys uses

I have had this issue twice using prior modpacks, including Aslain's. Sometimes your computer just does a funky install, and does some stuff it shouldn't. The easiest remedy for this, albeit time-consuming, is to clean out your Res_Mods folder completely and then uninstall the entire WOT client. Then, do a fresh reinstall of the WOT client, let it do it's mega updates, and then reinstall your favorite mods. It's horrible, and lengthy, I know....but it works.

I am experiencing the same issue. It makes it a rather large problem when there are many tanks around a corner, and you cannot unstick the auto aim. Other times, it will unstick itself and reattach to one of the other tanks near it. I've found that in order to deactivate autoaim, I have to hold down the RMB for a second or so, but that really only works 50% of the time. I too reverted back to version 10 and the problem was fixed