Wolvenworks

everything is up to date so far. and there are no issues. the only thing that's triggering issues right now is when i run WoT with mods. Win10 is up to date. all drivers are up to date. the only major change this year is my laptop's keyboard getting repaired, so the SSD and harddisk was briefly unplugged for a month while it was in the shop. if the issues stem from there then i would be getting BSOD outside WoT...except for the sole reason that it really only happens when i run WoT with mods now. the WoT files were moved from an internal HDD to an external HDD.

so to re-summarize:

-i moved WoT files to another HDD (should have no issues)

-drivers and Win10 are up to date

-modpacks installed are as up to date as possible

-game is up to date

-game refuses to run with mods and freezes/crashes on loading screen, occasionally blue-screening after that.

-game still refuses to run mods after a complete reinstall of game client and modpack

-game runs perfectly normal on safe mode/vanilla (complete uninstall of modpack). noticeable lack of BSOD.

-therefore the game client has nothing wrong with it

-if hardware/drivers are the cause to the BSOD, i should be getting BSOD even when not playing WoT. but it did not BSOD, even under noticeably heavier usage (eg: running BFV, opening 20 tabs on chrome while running WoT vanilla, whatever). therefore it is not a driver/hardware issue.

-therefore the source of why the mod is not working remains unknown

-Ress notices some "weird code" on my older logs. perhaps that's related to the issue?

did i get everything @Aslain @Ress ? ps: will be travelling to UK for a week so might not check the forums as often.

20 hours ago, Aslain said:

Mods cannot cause BSOD that I know for sure. Maybe your PC is not capable to run those you selected, and your hardware is failing (overheating, driver issues etc.).

 

I don't know if devs checking this forums.

shouldn't be the case since it can run exactly the same mods before. hell, i'm actually running LESS mods now. so for some reason what was able to run before 1.5 (the last time i played before recently) somehow ceased to run now. 

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?

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

@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.

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?

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?

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

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

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

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 

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?

-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:

O_O

well shiiiit. what now?

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.

Found a bug with the "gold ammo visibility mod" : it didn't work as intended (in this case, no blue effects), and it disabled zooming for me (shift button was working as intended when typing). already ran the game with that particular mod off and everything is back to normal, so can say that mod is the cause of the issue.

found this weird bug where the screen freezes like this post-match (in this case, after i played Grille) wondering if mods are the cause, this time.

still think that WG needs to help out with a method for modding sounds without affecting actual sound files, since sometimes the sounds can "disappear" if you run it it safe mode

anyway did my logs reveal any other problems other than the Zorgane issue? looks like WG support gave up on helping me

weird. i'm on win10. i don't even use edge. did notice that my frames seem to improve somewhat when i switch to the WW2 sound mod, but i don't like it overriding my choice for the 6th sense sound mod to a default one

could this be related? i got this back when i was using Zorgane's, and now when i switched to the World war sounds.

so? found the issue?

this one, right?

Aslains_WoT_Logs.zip

this time noticed that my British Valentine's 75mm gun has no gun sound at all. might wanna get Zorgane to fix this fast: i'm currently on a bug hunt to find out why i'm having very severe performance and screen tearing issues on a brand new gaming laptop

uh not that. i just want an update from the notice Aslain put up earlier on the changelog regarding the mods not working properly in ASIA servers due to our side of the 9.20.1 update. want to know if that's fixed with 9.20.1.2 being here already. not that it matters for now since i'm still waiting for the zorgane audiopack to be updated. you feel this post needs to be moved, go ahead. i think it's an issue, therefore i post it here. was i wrong?

would like to ask, is the issue with mods still there for the asian server? awaiting the day where i can hear sounds again