Jump to content

Darth_Clicker

Premium Member Tier II
  • Posts

    725
  • Joined

  • Last visited

  • Days Won

    16

Everything posted by Darth_Clicker

  1. Sounds like maybe you have installed the show gun direction mod previously. The first thing to try is to make sure that you always have "clean install" selected in the modpack installer. This is either the last step or one of the last steps in installing the mod pack. Also make sure that you do not have anything being installed from your Aslains_Custom_mods folder located in your C:Games:World_of_Tanks folder. I manually updated my sight mod (Damokles) to the latest version for 9.15.1 and have not had anymore problems in the last 28 battles.
  2. I agree. I think the problem is widespread through various mods and is intermittent which makes it mostly impossible to diagnose. I suspect that some mods that work in 9.15.1 are in fact not optimized for 9.15.1. I have downloaded the latest Sword of Damokles, which is a more recent version than in the modpack at the moment I believe. Since updating this, I have not had any more problems. Before, about 25% of the time the mod would not work and esc strg (ctrl) etc keys would also not work. But now....so far so good. I think a lot of mod devs simply tried their mod in 9.15.1 and it worked one time so they declared it worked perfectly....but it doesn't all of the time.
  3. I had these same problems very frequently until I reinstalled the modpack without ATAC selected. There are still occasionally some small problems, but very rarely. If you have ATAC selected in the modpack, try reinstalling the modpack without ATAC. I suspect that with the UI language change that WG made in the game with the latest version, that some mods are not always functioning perfectly as expected. WG threw the modding world a big juicy curve-ball and everyone is still adjusting. I think we just have to be patient and wish for the best. Maybe Trump can fix this too since he has said that he is the only one that can fix all problems....lol.
  4. small update: I have uninstalled ATAC and have not had any issues for the last 30+ battles.....it could be the problem. No guarantees though...
  5. XVM has changed in the basic way it works....some different necessary files etc. I am not exactly sure of what all has changed, but for instance the way you change the position of the xvm hit log for example has been moved to a separate file from all previous versions. So, I suspect that there are a lot of other changes that are causing you problems. XVM has had to be rewritten due to the changes made by WG in 9.15.1. This is a very big learning experience for everyone.
  6. Thanks for the info, but pressing F1 over and over does not always solve the problem for me. Sometimes, the only way to solve it is to restart the client.
  7. I was sure that it was the non XVM hit log causing this. But it just now I was in a battle where I could not chat, I could not use the esc key...and Damocles crosshair was not working at all...I only had the vanilla crosshair in both standard and strategic (arty) view. I closed the client mid battle and restarted it and when I got back into the battle, everything worked perfectly. I did not have non xvm hit log installed. Could this be a global problem with the new UI langauge/mod incompatibility problem? Here are my current logs for that battle: _Aslain_logs.zip python.log
  8. The Aslain's player panel (I have selected the large in game) has the wn8 values partially covered. Also, using the set up in the logs below, the escape button on the keyboard does not function. I switched my OTM from Aslain's back to XVM and the problem was fixed. One more thing: Chance to win in game does not have a percentage shown. The panel when I press the tab key has the chance percentages. I have everything selected on the xvm website. These are all small things and are simply FYI. They are by no means game breakers for me and can wait until after vacation. Thanks python.log _Aslain_logs.zip
  9. it is not only the contour that is wrong, the wrong vehicle is also listed wrong. To be clear, it is not a problem with the contours.
  10. This may be a problem with XVM, I will make a report there if needed. Since I am using Aslain's version of XVM I thought I would post this here first. I understand that XVM is not stable, but thought I would mention the problem here. If I report it on the XVM forum, I have to provide the XVMlog and I am not sure if it shows I am using Aslain's xvm. Not a big deal and definitely does not need to be addressed during vacation time. More of an FYI. The problem: The battle loading panel shows the current team vehicles correctly except for my vehicle. The vehicle from the last battle is shown in the roster instead of the current vehicle. The Contour Icon is correct, it is only the vehicle name that is incorrect. Edit---more info---This only happens when the vehicle survived the previous battle. When I exit the battle after being destroyed, the correct tank is displayed in the next battle. Edit 2: It does not always happen...... _Aslain_logs.zip python.log
  11. In addition to Non-XVM hit log, Gambiter's Damage Log (#1) is causing either chat not to function properly but also the escape key and ctrl keys not to work in battle.
  12. Which mod are you talking about? Or, are you talking about the modpack which is not a mod but a collection of mods? The modpack is not complete because 1. XVM is not completely updated and stable with 9.15.1. The XVM developers are working on it. Aslain is not in control of this. 2. The mods selections that are greyed out in the modpack are not updated to be compatible with 9.15.1. WG made huge changes to the inner workings of WoT (changed the UI Codebase) which made a lot of mods incompatible. If you use mods that have not been proven to work with 9.15.1 you run a risk of crashes and other problems. Be patient and trust Aslain. He is the best and most reliable in the game.
  13. I am not sure about this being great news or not...it could be that it only gives the geniuses at WG more time to change things in bigger and "better" ways. We will probably get a big surprise when it is released.
  14. yes, you have to drive an enemy tank into a fire. Driving your own tank into a fire will not suffice. You have to hack someones computer, play the game on their account etc to complete the challenge.
  15. make sure you include the required log files when making a report such as this. It will help Aslain help you.
  16. edit: did not correctly understand the problem the first time I read it. My original reply is irrelevant...so I deleted it.
  17. provide a screenshot of your problem. Provide the required logs.
  18. Same here for me too. EU1 35k and EU2 24k even though the actual player count as reported by WG when I switch servers is different.
  19. Look in Aslains signature on his reply to you above. There is a little link How to report a bug or issue It is also the first thread in the Issues and Bug reporting section of the forum. There is a wealth of information here if we only take the time to look for it. Once you understand how everything here works, you will get help. But, you have to give the proper information to enable the helpers.
  20. I play arty only and do not own any new tanks or tanks that would need an expected damage recalculation. Your idea is logical, but not in my case.
  21. I think that the in game wn8 rating is correct and the wn8 reported by vBaddict and other sites is the one that is incorrect. I know that my in game wn8 is 1330 and that is correct. vBaddict and other sites have me at over 1400 wn8.
  22. Was it Quaksen's yelling nicely that did the trick?
×
×
  • Create New...

Important Information

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