Jump to content
Korean Random

kupjones

User
  • Content Count

    117
  • Joined

  • Last visited

Everything posted by kupjones

  1. Normally I would agree, however, the previous TIM .exe versions did not cause the virus engine to kick out and quarantine. So, something in the build is including something new that some think shouldnt be there
  2. Ah -- makes sense. See? I knew there was a reason that I was not grokking! Thanks!
  3. Got it -- at least now I understand why the disparity. Perhaps a change to t-winrate to take the value of v.winrate over the server? I find v.winrate to be entirely more accurate. OR, I am not seeing the reason for the two being different. Thanks!
  4. Other than one being available in the hanger and the other available in the battle interface, it looks like both should return the same value -- but they do not. So does anyone know if, in fact, these are measuring two different things? {{t-winrate}} │ X │ X │ X │ X │ X │ X │ vehicle win ratio {{v.winrate}} │ X │ . │ vehicle win rate (percent of wins on this vehicle) After all, a percentage IS a ratio!
  5. Avast shows this as infected as well. The last person to compile this needs to check their system, as prior trains were not infected. V128 is infected.
  6. Unfortunately, that latest version is infected with the Win32:Evo-gen virus
  7. Yeah, I made my own too -- it just doesnt show up and that is the only one. bizzarre. thanks anyway
  8. Yes, which is why this is so perplexing and leads me to think the name is coming in as something else.
  9. Anyone seen this? I've checked vehicles.xc against WOT's tank package -- tank names are the same. I have an icon with the same name, yet the PlayerPanel shows a generic tank contour. My guess is WOT is using a different name for the Pudel? Anyone else see this?
  10. XVM.log shows this error -- and I noticed that the directives in captureBar.xc do not appear to be processed -- either correctly or not at all. Total Error is below and occurs multiple times in the XVM.log file 2017-08-27 13:56:15: [b:004] ReferenceError: Error #1074: Illegal write to read-only property CAPTURE_BAR_LINKAGE on Linkages. at com.xvm.battle.teamBasesPanel::UI_teamBasesPanel/setup()[/var/lib/jenkins/jobs/XVM/branches/9-19-1.up2i50/workspace@script/src/xvm/xvm_battle;com/xvm/battle/teamBasesPanel;UI_teamBasesPanel.as:58] at net.wg.gui.battle.components::BattleUIComponent/configUI()[/var/lib/jenkins/jobs/XVM/branches/9-19-1.up2i50/workspace@script/src/xvm/xvm_battle;com/xvm/battle/teamBasesPanel;UI_teamBasesPanel.as:33] at net.wg.gui.battle.components::BattleUIComponent/validateNow() at net.wg.gui.battle.components::BattleUIComponent/onRenderHandler() Complete log file attached. xvm.log
  11. I would never have guessed that would have been Total Efficiency. Thanks! or TANKS!!
  12. Perhaps I am not just seeing it -- the previous XVM version I was able to disable XVM support for teh hitlog/damagelog, but in 6.8.0 when I disable these and make sure we are not turning off native WOT hit/damage support that I am still seeing XVM "stepping on" the native logs. It makes it doubly difficult to troubleshoot as everything is in separate files, but as I said -- I had managed to disable XVM support in the last version. This seems to be not working in 6.8.0 as it did before. Or --- I have completely missed something added. for example, this (screen snip) appears on loading XVM defaults -- and I can find nothing (yet) that removes this header other than removing XVM. Thanks!
  13. Others have done XV-independent clocks by changing BattleAnimationTimer.swf. I've attached mine - you have to get rid of the .txt extension. Place it in the gui/flash folder battleAnimationTimer.swf.txt
  14. Had the same problem -- latest 6.4.4 is supposed to have fixed a "mouse capture" problem that I havent tried yet. Have you upgrade to 6.4.4 yet?
  15. I image some enterprising person will write an external py routine that can be called using the macro-like support. Hmmmmm.........
  16. Ahh, I understand. But note: An injector IS a Trojan, just under my control. a matter of semantics, the end result is the same. Thanks!
  17. Yeah, dont use 3rd party tools to update XVM -- there's no need. Just grab the installer that they provide. However, I would recommend never updating your primary game folder, but instead creating a copy of WOT where you can test updates before promoting them. Just good, safe game modding. For future cleaning http://www.mediafire.com/download/w0e79traad94xdh/CacheCleaner_WoT.7z
  18. Yeah, I have no idea what "XVM Update" -- unless you are referring to the installer?. BTW Пользователь, what does "WFT" stand for? Thats a new one on me Just pull the prod version from the XVM main download page - either the zip archive if you like doing it manually or grab the installer. So, curious, what did you use to delete the cache?
  19. No, but a question -- you say that you have done clean installs. Did you by chance completely clean out the WOT cache directories prior to the re-install? Re-installs of WOT will not clean up the cache, and many crashes can be directly traced to corrupt cache files.
  20. Read the Changelog -- XVM minimap is nop -- about 1/2 month out now? Maybe.
×
×
  • Create New...