Darth_Clicker

see post below

I have no problem at all with the size of the installer.  But, I can understand if a person has to use the smoke signal modem on the Indian reservation for downloading that a 100+ mb file could take a long time.

The NSA in America knows each and every mod that you are using.... :lol:

I am using the larger one and it seems to work fine, but only after 1 battle.   The smaller one is the current one in the mod pack and it is what was causing my problem.  The mouse 4 option still does not work for me but that does not matter at all.  I am happy using the F key.  May be a problem with my mouse software etc...not sure.  Another life mystery....lol.

I solved my problem. The __init__.pyc file in the current version in the modpack is different from the older version. It is 9kb smaller, but I have no idea what is different because I do not understand python files. But, I installed the __init__.pyc from the version 9.10 Battle Assistant and now I can reassign the activation key from G to F. I will see how this works over the long run. But, for now it works perfectly.

Is it possible to change the G key to activate to F like I did before?  Since I am arty only, moving my finger one key over to the G key is simply too much work and far too complicated for my simple little clicker brain....lol.

Thanks for your time Aslain.

If the mouse 4 option is working for you, then there is a problem with my system.  The installer is installing Key_G and Mouse_4 options as directed, because you can see the command lines in the file I pasted above, but the mouse 4 does not activate Battle Assistant for me.  The G key does work, so nothing wrong there at all.

Do you know how to change the G key to activate to another key?  Changing the Key_G to Key_F does not make any difference.  G is still required to activate.

Thanks for your time Aslain.  I know that none of this is actually your problem, I would just like to solve it and I appreciate your and Grandorf's help.

I looked at logs, and there is only G key option selected by you. It was logged that way.

I guess the log is wrong.  Because in the installer, I have G and mouse 4 option selected and that is what the installer installs into the directory, the file I posted above that shows   keys: "[Keys.KEY_MOUSE4, Keys.KEY_G]" # список клавиш, кавычки не убирать!    I copied this file after running the installer and before uploading my log files.

Hi

 

Do you have anything in Aslains_Custom_mods folder?

 

Also check you are changing right xml: 

 

C:\Games\World_of_Tanks\res_mods\0.9.12\scripts\client\gui\mods

I am changing the correct file, and I do not have a file in the res_mods>0.9.12>scripts>client>gui>mods folder in my zip file in the custom mods folder.  I used to have a file there to change from Key_G to Key_F but I removed it yesterday.  I have other things in the zip file, but nothing pertaining to Battle Assistant, only mini map xvm changes, hit log location changes etc

By the way.

 

Doesnt this indicate a problem? 

 

список клавиш, кавычки не убирать!

 

Its in the xml.

I saw that, but what does "list of key quotes not clean!" mean?  At least that is what Google Translate returns.

In the logs I see you have selected to activate it with G key only.

I have selected "triggered by both "G" and "Mouse4" button.

My mod_battle_assistant.txt file reads:

spg:

  enabled: true                         # false - полностью отключить мод

  keys: "[Keys.KEY_MOUSE4, Keys.KEY_G]" # список клавиш, кавычки не убирать!

  zoomSpeed: 3.0                        # скорость зума

  ignoreObstacles: false                # игнорировать препятствия (true - камера не будет перескакивать на препятствия на пути снаряда)

expert:

  enabled: true

gunner:

  enabled: true

But the mouse4 button will not activate Battle Assistant.  And, if I change the Key_G to Key_F, I still have to press G to activate.  It ignores the Key_F command

Battle Assistant will not activate using the mouse4 button as selected in the modpack installer.  It will only work with the G key.  Also, before, I could change the key to activate in the  mod_battle_assistant.txt file from G to F with no problem.  But now, if I change the Key_G to Key_F, I still have to press G to activate Battle Assistant.  So, I think there is something else in the mod that dictates which key has to be pressed.  I have no knowledge of Python Files or how to open a pyc file in order to investigate myself.  I also can not find a way to contact the author except by leaving a message on http://worldof-tanks.com/battle-assistant-best-modification/#comment-385023blog comment section.  If I get any information I will let everyone know.  I am sure there is a common problem/new change that is causing the inability to make custom changes to the activation method.

Thanks in advance for any help provided.

_Aslain_logs.zippython.log

In the past, I have always opened the mod_battle_assistant.txt file in Notepad++ and changed the Key_G to Key_F because I wish to activate Battle Assistant with the F key instead of the G key.  With the latest version that is in v9.12.11 this does not work.  Even after changing the Key_G to Key_F as before, I still have to activate using the G key.  I have made sure that the file is being saved after changing, but Battle Assistant is not seeing the change.  It still requires G even though the txt file shows F.  Is there a new location/file that I also have to change?  Or does anyone have another idea of what the problem may be?

Thanks in advance for your help.

no its not windows

Just curious, how do you know that it is not windows.  I have the same problem maybe once every 75-100 battles or so...not very often.  I have been thinking that it is related to the arty rotation lag bug.

I think a lot of people watch QuickyBaby and see that his replays have wn8 in the battle results.  That is a feature of QuickyBaby replays site, not the game client itself.  I generally have vBaddicts ADU running on my second monitor and it updates automatically and I can see both the wn8 for each battle as well as my average.  But, as Grandorf said you can use YasenKrasen to show it...but I have to click to see it and since I am an Arty player only, I am exhausted from a hard battle of clicking..... :P

yep, I just figured out that it was the ATS and BRR files causing it....but I found it out by trial and error/removing mods one by one....should have waited and read it here first....oh well.

I have even had two battles were my arty would not move at all using the keyboard keys.  It would not move forward or backwards either.  It would rotate by aiming with the mouse but only in strategic view.  Talk about being a sitting duck....lol.

Even though last sighted enemy markers is not an option in the xvm mini map section in the modpack set-up panel, I can see the markers on my mini map.  I guess that Aslains xvm setup has this selected as the default.  If you are not using Aslain's xvm mini map, you can always enable these markers by enabling the expanded mini map features under the General tab in the game settings.  If you use the in game mini map features with the xvm mini map you will have double markers, so it is an either or situation.

Thanks for sharing the info.  I had not noticed that 6th sense was not staying lit 9 seconds.

The auto aim in the mod pack works perfectly for me.  The files are in fact the same...just as Aslain said. So, OP, I do not know how to help you.  It works fine for me.

It's the same in modpack and on that linked thread, the only difference is removed stupid auto-repair from the config.

Yeah, I saw that and did not think it would make a difference.  That is why I said that I was not sure if I actually had a problem before or if it was because using auto aim is too difficult for pro clickers like me.... :P  I am now reinstalling it from the modpack and will terrorize someone with my Bert.....

I think I had the same problem, but I do not use auto aim very often since I mainly play arty.  But, I downloaded the latest files from the author in the WoT forums http://forum.worldoftanks.eu/index.php?/topic/441413-0912-autoaim-indicationsnapping/ and replaced the files from the mod pack and it is now working perfectly.  But, I am not 100% sure it was not working before...I think I only tried to use it once.

 

 

Maybe Google Crome sucks. Maybe it saw something.

When I go to an art museum, I see something but I usually do not have any idea what I am looking at.  :P

I had the same issue.  The game never started after I clicked "Play".  I think that one problem is Skins of destroyed vehicles-white.  I installed the modpack without this and the game did not crash.

Hi,

Until some time ago when right clicking on a player's name in the battle results window one of the options was to report the player.

 

I don't have the option anymore.

 

Was it removed by WG or I have a problem and I'll come back with the log?

 

Thx.

I just played a vanilla game with no xvm or mods and you are able to report from the battle results window.  So, it was not removed by WG and is caused by a mod etc.   But, who knows, the new version that is released tomorrow may work fine with all mods....or not work at all with any mods.  I will wait until everything settles down with v9.12 before posting logs.