Wolvenworks Posted June 8, 2019 Posted June 8, 2019 game instantly crashes on loading screen. sometimes it doesn't and gets stuck on the loading screen until i force-close it or restart the computer. a pop-up box says that it's something to do with XVM not working. modpack is latest version. i'm on the asian server. the only major change i did is moving the game files to another HDD to free up some space on the old one. i updated the modpack after the moving. Aslains_WoT_Logs.zip the game runs ok in safe mode. Quote
Administrator Aslain Posted June 8, 2019 Administrator Posted June 8, 2019 No idea, there is nothing in your logs, xvm log is empty, python log is incomplete. Looks like a local problem. Quote
Ress Posted June 9, 2019 Posted June 9, 2019 Moved game to new hdd... hmm simple move should work without any issue i did it few times (cut-paste). make sure you don't have dupes copies of client (old leftovers) try runing game in safe mode (does vanilla client work?) try deleting entire game cache (inside %appdata%) try running check integrity on you client try re-adding game to firewall exception try running game as admin if located on system drive try reinstalling modpack as admin (does modpack auto-detect new game path)(clear cache, logs..all recommended stuff) if using, check/disable antivirus try getting ccleaner and clear your registry (leftovers from install) ..idk some of ideas Quote
Wolvenworks Posted June 14, 2019 Author Posted June 14, 2019 -no dupes on client -file integrity checked -can run on safe mode -already re-added to firefall exception -not a system drive. -antivirus is defender, so that should be a non-issue -ccleaner is useless. -deleting the cache at %appdata% didn't help also already updated the game and the modpack due to 1.5.1 being out but still crashing. this pops up as with before: Quote
Wolvenworks Posted June 14, 2019 Author Posted June 14, 2019 i just noticed that there should be a micropatch tomorrow that "adds a folder for mods". i wonder if that's related to this issue? Quote
Ress Posted June 14, 2019 Posted June 14, 2019 1 hour ago, Wolvenworks said: i just noticed that there should be a micropatch tomorrow that "adds a folder for mods". i wonder if that's related to this issue? 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) Quote
Wolvenworks Posted June 15, 2019 Author Posted June 15, 2019 (edited) just now updated my graphic driver and modpack. game CTD'd on loading screen without the error report msgbox this time. i'm fully aware that moving the files between HDDs shouldn't cause this issue, so the issue should be within the game or modpack itself...i have removed all mods that have any "XVM" written on it (repair timer, map mod, reload sound mod) and it crashed with the messagebox appearing this time. in the opinion that something might be wrong with the mod itself since game can still run in safe mode Edited June 15, 2019 by Wolvenworks Quote
Wolvenworks Posted June 15, 2019 Author Posted June 15, 2019 correction: yea might be something wrong with my WoT. i just got hard crashed into a blue screen from loading a match. that aint natural Quote
Wolvenworks Posted June 16, 2019 Author Posted June 16, 2019 already did a reinstall or game client and new modpack. game was okay (i can see the garage load up) until the prompt where i have to restart the game due to installing audio mods. after that the game crashed as usual. had to do a soft-restart because the comp was stuck on the loading screen to the point i can't use task manager to force shut down WoT Quote
Administrator Aslain Posted June 16, 2019 Administrator Posted June 16, 2019 Try latest modpack, and generate new logs with that after the problem occurs. Quote
Wolvenworks Posted June 16, 2019 Author Posted June 16, 2019 4 hours ago, Aslain said: Try latest modpack, and generate new logs with that after the problem occurs. ver 1.5.1.1 #01 right? already did that earlier on my prev comment. attached are the logs. Aslains_WoT_Logs.zip Quote
Administrator Aslain Posted June 16, 2019 Administrator Posted June 16, 2019 No, it's not the latest one. Quote
Wolvenworks Posted June 17, 2019 Author Posted June 17, 2019 20 hours ago, Aslain said: No, it's not the latest one. it was when i posted that. anyway #2 looks like it only has updates to parts of the mod i never used, so would updating the modpack really affect my situation? Quote
BokiDeNiro Posted June 19, 2019 Posted June 19, 2019 (edited) i have that crashes 6 months with Asslain modpack, any modes i have are in conflickt... i have many of tham :) The crash i have comes around all 10 battles... I was reinstall Windows, and i try some day without mods... works without problems... and if i install i got the crashes again... i have that crashes 6 months with Asslain modpack, any modes i have are in conflickt... i have many of tham :) The crash i have comes around all 10 battles... I was reinstall Windows, and i try some day without mods... works without problems... and if i install i got the crashes again... Aslains_WoT_Logs.zip Edited June 19, 2019 by BokiDeNiro Quote
Ress Posted June 19, 2019 Posted June 19, 2019 On 6/17/2019 at 3:49 PM, Wolvenworks said: it was when i posted that. anyway #2 looks like it only has updates to parts of the mod i never used, so would updating the modpack really affect my situation? 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! 1 hour ago, BokiDeNiro said: i have that crashes 6 months with Asslain modpack, any modes i have are in conflickt... i have many of tham :) The crash i have comes around all 10 battles... I was reinstall Windows, and i try some day without mods... works without problems... and if i install i got the crashes again... 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" Spoiler ...and second there is some strage stuff inside logs, but don't know what is related to. 2019-06-19 11:38:51.902: ERROR: KeyError: 2 2019-06-19 11:38:51.902: INFO: ============================= 2019-06-19 11:38:52.288: INFO: owh:399 2019-06-19 11:38:54.690: INFO: owh:601 2019-06-19 11:38:55.692: INFO: owh:930 2019-06-19 11:39:15.702: INFO: owa:0 2019-06-19 11:39:19.094: INFO: owdmg:0:805 2019-06-19 11:39:19.094: INFO: owk:0 2019-06-19 11:39:52.792: INFO: owdmg:0:357 2019-06-19 11:39:57.091: INFO: owa:0 ... 2019-06-19 11:40:03.090: INFO: owh:974 2019-06-19 11:40:03.190: INFO: owh:975 2019-06-19 11:40:20.292: INFO: owh:1348 2019-06-19 11:40:28.098: INFO: owd 2019-06-19 11:40:28.101: INFO: owdmg:0:310 ... 2019-06-19 11:41:09.685: INFO: owa:0 Quote
Wolvenworks Posted June 19, 2019 Author Posted June 19, 2019 (edited) 58 minutes ago, Ress said: 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" Reveal hidden contents ...and second there is some strage stuff inside logs, but don't know what is related to. 2019-06-19 11:38:51.902: ERROR: KeyError: 2 2019-06-19 11:38:51.902: INFO: ============================= 2019-06-19 11:38:52.288: INFO: owh:399 2019-06-19 11:38:54.690: INFO: owh:601 2019-06-19 11:38:55.692: INFO: owh:930 2019-06-19 11:39:15.702: INFO: owa:0 2019-06-19 11:39:19.094: INFO: owdmg:0:805 2019-06-19 11:39:19.094: INFO: owk:0 2019-06-19 11:39:52.792: INFO: owdmg:0:357 2019-06-19 11:39:57.091: INFO: owa:0 ... 2019-06-19 11:40:03.090: INFO: owh:974 2019-06-19 11:40:03.190: INFO: owh:975 2019-06-19 11:40:20.292: INFO: owh:1348 2019-06-19 11:40:28.098: INFO: owd 2019-06-19 11:40:28.101: INFO: owdmg:0:310 ... 2019-06-19 11:41:09.685: INFO: owa:0 noted. am downloading #03 now. will get back within...2-3 hours, judging by how throttled the downloads usually feel (if not actually are). completely missed that PSA about Battle Observer, my bad. will try installing the modpack without it this time....whenever the modpack finishes downloading PS:i have no idea what's that code saying. did we accidentally stumble on SerB's virtual rasp? Edited June 19, 2019 by Wolvenworks Quote
Wolvenworks Posted June 19, 2019 Author Posted June 19, 2019 (edited) @Ressturned off Battle Observer. game still crashed with mods. i am now officially confounded tried running the game vanilla (uninstalled modpack) and it runs just fine, so the issue is positively in the modpack. Edited June 19, 2019 by Wolvenworks Quote
Nick911 Posted June 19, 2019 Posted June 19, 2019 I have same problem but i found that it can work only without mods in section PMOD. I try to turn off and turn on all mods that I using and only one mod that crashes game is DEFAULT ZOOM SETTINGS (or all of mods in PMOD, but I using only that one in that section) Quote
Nick911 Posted June 19, 2019 Posted June 19, 2019 @Aslain Try update PMOD, I think its new version, you have in Modpack 1.41.2 and new is 1.41.3 Quote
Administrator Aslain Posted June 19, 2019 Administrator Posted June 19, 2019 New version introduces a new feature for hangar only , it's not a fix or anything like that. Quote
BokiDeNiro Posted June 19, 2019 Posted June 19, 2019 vor 8 Stunden schrieb Ress: 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" Unsichtbaren Inhalt anzeigen ...and second there is some strage stuff inside logs, but don't know what is related to. 2019-06-19 11:38:51.902: ERROR: KeyError: 2 2019-06-19 11:38:51.902: INFO: ============================= 2019-06-19 11:38:52.288: INFO: owh:399 2019-06-19 11:38:54.690: INFO: owh:601 2019-06-19 11:38:55.692: INFO: owh:930 2019-06-19 11:39:15.702: INFO: owa:0 2019-06-19 11:39:19.094: INFO: owdmg:0:805 2019-06-19 11:39:19.094: INFO: owk:0 2019-06-19 11:39:52.792: INFO: owdmg:0:357 2019-06-19 11:39:57.091: INFO: owa:0 ... 2019-06-19 11:40:03.090: INFO: owh:974 2019-06-19 11:40:03.190: INFO: owh:975 2019-06-19 11:40:20.292: INFO: owh:1348 2019-06-19 11:40:28.098: INFO: owd 2019-06-19 11:40:28.101: INFO: owdmg:0:310 ... 2019-06-19 11:41:09.685: INFO: owa:0 Is the Battle Observer only that HP Information in the middle or the Tank Icons HP Pool Bar to? Should i delate all both or only that Mode in middle? (Sorry for my bad english) Quote
Ress Posted June 19, 2019 Posted June 19, 2019 19 minutes ago, BokiDeNiro said: Is the Battle Observer only that HP Information in the middle or the Tank Icons HP Pool Bar to? Should i delate all both or only that Mode in middle? This is all part of battle observer (as you can see if you follow sub-section dots). 1 Quote
Administrator Aslain Posted June 19, 2019 Administrator Posted June 19, 2019 1 hour ago, Nick911 said: Its now working for me well, so.... :) Well, I'm glad ... :) Quote
BokiDeNiro Posted June 19, 2019 Posted June 19, 2019 Thx i found it and i will reinstall Modpack without Battle Observer! I tell you if i have crashes or some issues... THX anyway Quote
tankattack Posted June 21, 2019 Posted June 21, 2019 (edited) On 6/16/2019 at 3:06 PM, Aslain said: Try latest modpack, and generate new logs with that after the problem occurs. To update members about the situation, it is exactly what I did this morning when #6 was available: With update #3, cannot start to play a game: crash With update #6, it is working! Edited June 21, 2019 by tankattack mistyping: ws instead of was Quote
Wolvenworks Posted June 22, 2019 Author Posted June 22, 2019 (edited) installed #7, and did not install Battle observer nor PMOD stuff. game blue-screened the comp under 5 mins in the loading screen. DPC_WATCHDOG_VIOLATION Edited June 22, 2019 by Wolvenworks Quote
Administrator Aslain Posted June 22, 2019 Administrator Posted June 22, 2019 BSOD? It's not mod related. It's your pc failure. Quote
Wolvenworks Posted June 22, 2019 Author Posted June 22, 2019 6 hours ago, Aslain said: BSOD? It's not mod related. It's your pc failure. yeah but it only happens when i run WoT with mods. i do everything else and no BSOD so far. i wonder if WG devs ever come to check this forum? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.