Darth_Clicker

When you say you unzipped the mod, what mod are you talking about? I always use the modpack installer to install my choices of mods etc.

I always use the Aslain's Custom folder to install my own personal xvm files configured the way I like them. xvm version 19 had changes to it that made the same files that were ok in version 18 no longer useable. I simply had to update my files in the Custom folder to version 19 files.

Probably any well known 3rd party free antivirus software is less trouble/better than Windows Defender.

the folder should be named 0.9.15.1.1 Try renaming it.

Avira AntiVirus Pro does not detect any bad things in the modpack....same as always. SED.exe files are know to be mistakenly viewed as malicious software/malware by programs. Panda probably is not up to date on their definitions concerning SED.

Thanks for the information. Your reason is good enough for me. I will try to remember to check out files for configs in the future....

Now I have to listen to the great KC and the Sunshine Band song "That's the way I like it"......

Glad you got yours sorted out too.

Did your xvm version change between v18 and v19?

Problem solved. I had xvm config changes in my Aslain's Custom folder that were causing these problems. Something apparently changed in XVM from v18 to v19 which resulted in my custom configs to mess everything up. My custom file was the same one I used in v18 with no problems. v19 installer works fine as long as I use the xvm files from v19 in my Aslains custom folder zip file and not from v18 oh.....I tried the first v20 and it worked fine with the correct xvm files in my custom zip file. Do you want me to try v2 as well?

I just played a battle and got an error message. xvm.log

I do not get an xvm error.

I tried installing with my anti virus turned off and that did not change anything.

I have not played a battle with the latest modpack version so I do not know about which mods work or not, but Auto Login, 2 row carousel etc does not work. I get the notification in the game that xvm is working, but something is definitely wrong with the latest version. v18 works perfectly for me too....with the exact same config. python.log _Aslain_logs.zip

If you are using a custom gun sight then that may be causing your problem. Mods that use a mod_sight.pyc file are buggy at the moment. Use a sight that does not use it and see if your problem is solved. Currently these crosshairs are using mod_sight.pyc: - standard and more... - taipan 2 - overcross - minimalistic sights shtys - sword of damocles

The Free Replay Camera by Hunter1938 http://forum.worldoftanks.eu/index.php?/topic/576377-free-camera-9151-tutorial/ works much better in my opinion than the one currently in the mod pack. Current modpack advantage: only one keystroke is needed to activate: F3 disadvantage: the camera movement control only has one speed....fast. This makes it difficult to control. Hunter1938 version advantages: It offers two speeds for camera movement control. The normal speed is the same as the current modpack version. By pressing the P key, the movement becomes smoother, and it seems a bit slower which makes it easier to control. It also allows the user to press the x key which keeps the camera on the same level where it does not move up or down in elevation. This also makes it easier to control. Disadvantage: Activation is a bit more complicated: you must hold caps lock and press F3 together. This means that you have to remember to turn off caps lock or YOU WILL BE YELLING AT PEOPLE THE NEXT TIME YOU TYPE SOMETHING IN CHAT ETC:

The problem also exists when using OTM by OM. Not just with Aslain's config

I used the same setup of OTM by Aslain as I have had in previous versions but in the battle the only thing I see over the tanks is the tank class icon. There are also no damage amount numbers floating above the tank after you score a hit and also no angel wings/nuke with a kill. python.log _Aslain_logs.zip

very funny...I played 20 battles so far today after starting this thread and did not have any problems. I was in a battle just now and saw the notification that bubs had posted his response above....I thought...hmmm I have not had any problems and then boooooom.....the problem happened again...haha. bubs79 you jinxed me....haha. Here are my logs in case there is new relevant info in them. The problem happened in the last battle. python.log _Aslain_logs.zip

This problem does not happen all of the time and I have not figured out a pattern yet. But sometimes the center of the mini map artillery sight will freeze on the map. The artillery sight itself will still move, but not the center that was added from the modpack. In the next battle, the center is missing completely. A restart of the client will solve the problem and then everything will work perfectly. So...once again....we have an intermittent problem....lol. Another gremlin!! If I learn more information, I will inform you here in this thread. Here is the screenshot where you can see the in-game arty sight on the mini map in a different position as the center image from the modpack. _Aslain_logs.zip python.log

I should add that I have just downloaded the latest mod pack version which includes a different Gambiters script. I am now installing it and will report my experience after a battle or two. Update: I think the Gambiters problem has been solved. So far no problems with chat.

The issue that you describe with the chat log is probably caused by Gambiter's hit log. The esc/ctrl issue is caused by sight mods that contain a mod_sights.pyc file. Currently these crosshairs are using mod_sight.pyc: - standard and more... - taipan 2 - overcross - minimalistic sights shtys - sword of damocles This explains why you are not having the esc/ctrl issue (you are using the vanilla sight)but are having the chat issue. Another work-around is to hit F1 twice at the beginning of the battle. This worked for me. But, I have stopped using Gambiters hit log for now and that has been the best solution for me.

Have you asked Lil'Abner for assistance? I hear he is good with computers.

The only alternative I know of is one of the damage announcers maybe. I am not sure if they cause chat problems or not. They are free to triy...

I use J1mbos without Gambiters and have no problems. With Gambiters I had the problem with chat. Remove Gambiters and your problem should go away.