Jump to content

Ress

Modder
  • Posts

    273
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by Ress

  1. python.log is empty and xvm.log is off (XVM Revision:9191 on Version:1.5.1.1.08 modpack, should be 9192). Play 1 game before generating/posting logs, they are useless if you post them after fresh/clean modpack install.
  2. First crashing and now BSOD (DPC_WATCHDOG_VIOLATION)? well damn...check/scan all your drives, check you SATA/IDE interface/drivers, try updating/reinstalling chipset/ssd drivers. What Is DPC Watchdog Violation Error? DPC Watchdog Violation (error code: DPC_Watchdog_Violation) is a common issue in the Windows operating system. It’s occurred due to some specific reasons, like unsupported SSD firmware, old SSD driver version, hardware incompatibility issues, or system files are corrupted. This is not modpack issue...you have issue with your OS/Hardware.
  3. Build date: 15-06-2019 Mod-Pack Installer by Aslain Version: 1.5.1.1.01 Installed on: EU Client #01? use latest modpack when reporting issues. Update your stuff, play 1 game, do some screenshots, post new logs if crashes.
  4. update for 2nd 1.5.1.1 micropatch also .csv bump for [#1341] added Bretagne Panther (france-F113_Bretagne_Panther) Drum0
  5. This is all part of battle observer (as you can see if you follow sub-section dots).
  6. Next time post logs when reporting issues. Your answer: v1.5.1.1 #03 (17-06-2019): - Battle Observer still not compatible with XVM v1.5.1.1 #02 (16-06-2019): - same known issues as before v1.5.1.1 #01 (15-06-2019): - same known issues: team counter/score gets bugged when Battle Observer is installed with XVM [currently this mod isn't compatible with XVM, choose which is more important for you] v1.5.1.0 #04 (13-06-2019): - known issues: team counter/score gets bugged when Battle Observer is installed with XVM [currently this mod isn't compatible with XVM, choose which is more important for you]
  7. Even if updated mods are not what you are using, it's still mandatory to use latest modpack when reporting issues. Aslain said if few times, aslo stated on how to report bugs > make sure you have latest modpack version installed, don't post bugs from old versions! Your first problem, you are using XVM and Battle Observer.Try without Battle Observer. v1.5.1.1 #03 Changelog:"Battle Observer still not compatible with XVM"
  8. I see you are using third party overlay/injection programs (overwolf) and fps counter top left? Did you try without it? As for logs nothing interesting except some errors on each startup. 2019-06-18 21:13:31.347: ERROR: [EXCEPTION] (scripts/client/game.py, 197): Traceback (most recent call last): File "scripts/client/game.py", line 160, in init File "scripts/client/gui/shared/personality.py", line 379, in init File "<string>", line 543, in init File "scripts/client_common/shared_utils/__init__.py", line 47, in forEach File "<string>", line 543, in <lambda> File "<string>", line 562, in _callModMethod File "python\gui\pmod\__init__.py", line 23, in init File "_legacy", line 1, in <pjorion_protected> File "_legacy", line 1, in <pjorion_protected> File "_legacy", line 1, in File "_legacy", line 1, in <pjorion_obfuscated> File "_legacy", line 1, in __init__ File "_legacy", line 1, in _loadCache File "scripts/common/Lib/logging/__init__.py", line 1186, in error File "<string>", line 365, in new__log File "<string>", line 354, in FilterMessageGUI TypeError: not all arguments converted during string formatting Dunno if this is normal, not using pmod so can't tell if this is related to it or not.
  9. You still have that token error inside xvm.log, is your xvm active ingame? 2019-06-18 18:07:11: [ERROR] No valid token for XVM network services (key=ASIA/Pius_PP_X) Did you try without xvm or reseting token? You still have that mod_spg_hitlog/artyhitlog error inside python.log 2019-06-18 18:11:13.583: INFO: [gui.app_loader.loader] Space is changed: LobbySpace() -> WaitingSpace() ... 2019-06-18 18:11:14.356: INFO: [gui.app_loader.loader] Space is changed: WaitingSpace() -> BattleLoadingSpace() ... 2019-06-18 18:11:14.581: ERROR: Traceback (most recent call last): 2019-06-18 18:11:14.581: ERROR: File "mods/xfw/python/xfw/events.py", line 71, in <lambda> 2019-06-18 18:11:14.581: ERROR: File "./swf.py", line 132, in _AppEntry_onAsInitializationCompleted 2019-06-18 18:11:14.581: ERROR: File "scripts/client/gui/Scaleform/framework/application.py", line 479, in onAsInitializationCompleted 2019-06-18 18:11:14.582: ERROR: File "scripts/client/gui/Scaleform/framework/entities/EventSystemEntity.py", line 8, in fireEvent 2019-06-18 18:11:14.582: ERROR: File "scripts/client/gui/shared/event_bus.py", line 45, in handleEvent 2019-06-18 18:11:14.582: ERROR: File "mod_spg_hitlog", line 1, in onAppInitialized 2019-06-18 18:11:14.582: ERROR: File "mod_spg_hitlog", line 1, in updateLayout 2019-06-18 18:11:14.582: ERROR: File "mod_spg_hitlog", line 1, in generateLayout 2019-06-18 18:11:14.583: ERROR: AttributeError: ArtyHitLog instance has no attribute 'result' ... 2019-06-18 18:11:15.294: INFO: [gui.app_loader.loader] Space is updated: BattleLoadingSpace() ... 2019-06-18 18:11:20.340: INFO: [gui.app_loader.loader] Space is changed: BattleLoadingSpace() -> BattleSpace() Did you try without artylog?
  10. ....there is always extreme way of testing xvm and force disabling it without need of messing with your xvm presets or installations. (not recommended) 1. go inside wot/mods/1.5.1.1 and move com.modxvm.xfw folder outside (this will disable xvm for you) 2. put com.modxvm.xfw folder back inside 1.5.1.1 (to re-enable it) ...less trouble Did you try without sound mod or artyhitlog and infopanel?
  11. Your xvm doesn't appear to be active, but you are probably aware of that one. The usual recommendation after new patch, try without: xvm, sound mods, tank skins, hitzones mod, battle observer... Might be unrelated to your issue but those are some of errors between battle loading>battle>game close. BATTLE LOADING... 2019-06-16 00:59:24.346: INFO: [gui.app_loader.loader] Space is changed: WaitingSpace() -> BattleLoadingSpace() 2019-06-16 00:59:24.574: ERROR: Traceback (most recent call last): 2019-06-16 00:59:24.574: ERROR: File "mods/xfw/python/xfw/events.py", line 71, in <lambda> 2019-06-16 00:59:24.574: ERROR: File "./swf.py", line 132, in _AppEntry_onAsInitializationCompleted 2019-06-16 00:59:24.574: ERROR: File "scripts/client/gui/Scaleform/framework/application.py", line 479, in onAsInitializationCompleted 2019-06-16 00:59:24.574: ERROR: File "scripts/client/gui/Scaleform/framework/entities/EventSystemEntity.py", line 8, in fireEvent 2019-06-16 00:59:24.576: ERROR: File "scripts/client/gui/shared/event_bus.py", line 45, in handleEvent 2019-06-16 00:59:24.576: ERROR: File "mod_spg_hitlog", line 1, in onAppInitialized 2019-06-16 00:59:24.576: ERROR: File "mod_spg_hitlog", line 1, in updateLayout 2019-06-16 00:59:24.576: ERROR: File "mod_spg_hitlog", line 1, in generateLayout 2019-06-16 00:59:24.576: ERROR: AttributeError: ArtyHitLog instance has no attribute 'result' 2019-06-16 00:59:31.084: INFO: GUIFlash: [ERROR] Component 'ShellTravelTime' not found! 2019-06-16 00:59:31.120: INFO: [gui.app_loader.loader] Space is changed: BattleLoadingSpace() -> BattleSpace() ...IN BATTLE... 2019-06-16 01:00:20.217: INFO: GUIFlash: [ERROR] Component 'InfoPanel.Content' not found! 2019-06-16 01:00:20.217: INFO: GUIFlash: [ERROR] Component 'InfoPanel' not found! 2019-06-16 01:00:49.973: INFO: GUIFlash: [ERROR] Component 'ShellTravelTime' not found! ...END/GAME CLOSE
  12. Not related, you should already have current 1.5.1.0 folders (mods/1.5.1.0 and res_mods/1.5.1.0) and after micropatch you will have new 1.5.1.1 folders. I don't know what to suggest you, moving game to other partition or drive (ssd/hdd) should't be any issue at all. In truth game doesn't really depend on registry stuff that much it's basically portable. Game should auto detect most of stuff, not even integrity check should be required. You can try posting new logs (now that you are on 1.5.1.0 and new modpack) but if it's instant crash your logs will be empty again...so yeah Maybe reinstall is your last resort? EDIT: Since safemode works, maybe you have issue with xvm? (try xvm only or without xvm) Did you update any drivers before you moved game to new location? (check your drivers)
  13. @tezra Most of AV can be temporarily turned off, if not then at least adding game to exclusion list is an option or checking blocked files. At this point doubt you have issues with game or mods, check your security stuff (antivirus, firewall).
  14. v1 doesn't have specific positioning (didn't see need of adding it) based on camera mode (arcade/sniper/strategy) only general xy. Inside battleLabelsInfoPanel.xc "x": 0, "y": 225, (x: left/right y: up/down), since it's "screenHAlign": "center", "screenVAlign": "center" go negative up and positive down. EDIT: Inside @xvm.xc if you add "infoPanel": ${"infoPanel.xc":"infoPanel"} at the bottom previous def need to have comma. Or if you add it in middle/above last one add comma behind it. example: "xmqp": ${"xmqp.xc":"xmqp"}, "tweaks": ${"tweaks.xc":"tweaks"}, "assistLog": ${"assistLog.xc":"assistLog"}, "infoPanel": ${"infoPanel.xc":"infoPanel"}, <--- not final edit/def "safeShot": ${"safeShot.xc":"safeShot"}, "sight": ${"sight.xc":"sight"} <--- last one (no comma) only 1 allowed without comma (last one) or config breaks Every edit inside @xvm.xc from top ("configVersion": "6.1.0",) to bottom have comma after (except last one).
  15. @John11 Same on this site, you can't download attachments if you are not registered member, nothing unusual. I prefer to link original instead of including other peoples work inside my archive.
  16. It's little hard to spot, but it's packet inside infoPanel.zip
  17. Lol, what makes you think its not inside modpack? Anyway... [Garage mods] > personal reserve & hangar headers > yellow (that's what you had installed)
  18. At first i tought it's xvm counter, but just realised it's vanilla one. It's hawg's Personal Reserve & Hangar Headers
  19. They are configs for infopanel.py (addon for xvm) for xvm only, while those inside modpack are standalone mods (xvm unrelated). As for difference well i tried to port originals to xvm as best as i could (not 100% identical, but close enough). Now the real question is: What's the point of having all those extra mods when you can recreate most of them with xvm? +less troubleshooting (example Battle Observer)
  20. @tezra In my opinion best way to delete all cache and stuff is Winkey+R > %appdata% or goto C:\Users\<user>\AppData\Roaming\Wargaming.net\WorldOfTanks and delete everything inside WorldOfTanks folder except preferences.xml file (you can delete it, but it will reset all your settings ingame). After that goto xvm site/settings and reset all activations/tokens and then start wot and try activating xvm again. That's all there is about cache/token, but if you have issues with your pc or something else this might not help you at all. Still worth a shot.
  21. 13.06.2019 added v8 (similar minimalistic design as v7 but using infopanel.py data) renamed all definitions Info > info (infoPanel, infoPanelbg, infoPanelAlt) updated infoPanel.py macros (v1, v2, v3, v4, v5, v6) "enemiesOnly" > "showFor" {{py: compareColor}} > {{py: infoPanel.compareColor}} {{py: infoPanelFormat}} > {{py:infoPanel.format}} updated optional aimingSystem.py macros (v2, v3, v4, v5, v6) PY(ON_CAMERA_MODE) > PY(ON_AIM_MODE) {{py:sight.cameraMode=arc?|{{py:sight.cameraMode=sn?|{{py:sight.cameraMode=str?|}}}}}} > {{py:aim.mode(v1, v2, v3)}} sidenote: should work without issues, didn't have time to test all 16 configs
  22. I was about to say you are missing xvm.log, but for some reason not all of you xvm/xfw stuff is loading on startup inside python.log, guess that explains missing xvm.log? ... 2019-06-12 14:53:28.517: INFO: [XFW] Loading mod: 'com.modxvm.xvm' FAILED: No module named xvm_main.python 2019-06-12 14:53:28.517: ERROR: Traceback (most recent call last): 2019-06-12 14:53:28.517: ERROR: File "mods/xfw/python/xfw_loader.py", line 287, in xfw_mods_load 2019-06-12 14:53:28.517: ERROR: ImportError: No module named xvm_main.python 2019-06-12 14:53:28.518: INFO: [XFW] Error with mod: 'com.modxvm.xvm.tankcarousel'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.518: INFO: [XFW] Error with mod: 'com.modxvm.xvm.squad'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.518: INFO: [XFW] Error with mod: 'com.modxvm.xvm.contacts'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.518: INFO: [XFW] Error with mod: 'com.modxvm.xvm.crew'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.518: INFO: [XFW] Error with mod: 'com.modxvm.xvm.integrity'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.518: INFO: [XFW] Error with mod: 'com.modxvm.xvm.autologin'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.518: INFO: [XFW] Error with mod: 'com.modxvm.xvm.profiler'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.518: INFO: [XFW] Error with mod: 'com.modxvm.xvm.profile'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.518: INFO: [XFW] Error with mod: 'com.modxvm.xvm.battle'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.518: INFO: [XFW] Error with mod: 'com.modxvm.xvm.limits'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.518: INFO: [XFW] Error with mod: 'com.modxvm.xvm.techtree'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.518: INFO: [XFW] Error with mod: 'com.modxvm.xvm.hotfix'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.519: INFO: [XFW] Error with mod: 'com.modxvm.xvm.hangar'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.519: INFO: [XFW] Error with mod: 'com.modxvm.xvm.sounds'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.519: INFO: [XFW] Error with mod: 'com.modxvm.xvm.export'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.519: INFO: [XFW] Error with mod: 'com.modxvm.xvm.battleresults'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.519: INFO: [XFW] Error with mod: 'com.modxvm.xvm.online'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.519: INFO: [XFW] Error with mod: 'com.modxvm.xvm.ping'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.519: INFO: [XFW] Error with mod: 'com.modxvm.xvm.equip'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.519: INFO: [XFW] Error with mod: 'com.modxvm.xvm.tooltips'. Dependency failed: 'com.modxvm.xvm' 2019-06-12 14:53:28.519: INFO: [XFW] Error with mod: 'com.modxvm.xvm.tooltips'. Dependency failed: 'com.modxvm.xvm.limits' ... So safemode work... well you can try without xvm, just to see if its xvm related? To me feels like somethings corrupted or blocked, xvmtoken or AV? All i can suggest you is "clean slate" modpack reinstall (clear cache, all xvm cache, reset your tokens, install as admin, make sure your AV is not blocking stuff). Until Aslain can look into it.
  23. We can't help you with only screenshot and no logs. We don't know what mods you are using and what possible issues you may have based only on screenshot. Therefor generate and post logs.
  24. You are better of trying to figure out why you have issues with latest xvm builds then trying to use old 1.5.0.4 stuff. That "fix" was temporary fix - use of part from previous xvm 7.9.3 version inside 7.9.4 and we are now on xvm 7.9.5 + new wot patch. You can't use older parts from previous xvm builds forever and hope to just work without issues with future game patches. Aslain warn you about this and here we are 1.5.1.0 and you can't use old "fix" anymore. EDIT: Of course you can but should you use it is the question...
×
×
  • Create New...

Important Information

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