Almace

That's due to the fact that the installer still installs mods into the directory 0.9.14 but WG patched to 0.9.14.1 (patch hit EU today only). You can try to rename the folder inside of res_mods and see if you can get into garage. Most mods seem to work in replays but for me it's stuck on updating vehicles. Aslain needs to see if it can be fixed easily, when he gets online (in about 1-2 hours).

Well, drops in framerate are certainly normal and relatively irrelevant (30s to ~100 can and will happen). What matters is, that you get playable fps on average. It's not normal though, is that the fps are suddenly stuck at 20 and below, if you're supposedly usually getting 120. In any case, as said already, simply running the game vanilla should give a good indication whether it's related to a mod (or mods) or if some other software/drivers or hardware are at fault. Remote diagnosis is a guessing game anyway, due to the lack of information about the system.

That's probably where Aslain forgot to update the download link then. I'm glad you found the culprit yourself and can finish the installation now. I've had a few of those since 2014 but it really isn't much of an issue. Simply means that you just can't use this particular mod right now, until the download link is fixed. Thanks for investigating the issue anyway. I'm sure that it helps out Aslain a lot.

Normally, when Aslain refers to "the logs", he just wants the _Aslain_logs.zip and python.log, located in the main WoT folder. More info on that and general bug reports can be found here: http://aslain.com/index.php?/topic/9-how-to-report-a-bug-or-issue/ (a link to that is also in Aslain's signature) As for the problem itself, it's probably just an issue with Aslain not updating the correct download link. So the installer tries to get files from a location where the files aren't actually at. Not a big issue and easily fixed, if Aslain knows which link needs the correction.

It's not that easy to tell where the problem is but I would guess that it's not coming from WoT. One way to find out, if it might be related to mods, is to play the game vanilla for a bit (if you're scared to under-perform, play low tiers). If the issue were constant, I would make a shot in the dark and say that your RAM may be faulty (can try to only use individual sticks and on different RAM banks, for testing). But it could be a number of things, really. Maybe your HDD/SSD is faulty/has bad sectors. Could try moving the game to a different partition/drive (no need to uninstall, just move the WoT folder). You could try to monitor your CPU/GPU/RAM usage and see if either of those get maxed out while playing. Another thing could be the PSU, not being able to keep up with what your system needs (aka. too small or faulty). If you can exchange RAM, GPU or PSU for testings, that would be helpful in determining whether or not those components are faulty. Other than that, could also just be some random-ass software running in the background and eating up all of your resources (RAM/CPU heavy) or some driver conflict.

Great to hear. =)

From a quick look, it seems like you want to do the following: Open Config_file_chooser.xml (WoT > res_mods > 0.9.14 > scripts > client > gui > mods > MHL) and check what config file it uses. Next you can then open and edit the .json mentioned in the above file (in the same folder as the previous), via notepadd++, and edit the "WindowKeyList" parameters for x and y respectively. Only tried it out quickly and it worked for me.

That's fine then, I guess. Probably has been dealt with after .05 and your issue might have been something Aslain patched up recently then. Even if the problem is resolved, I find the thread useful nonetheless. Thx for putting in the effort of trying out the newest version and checking on that file.

Hence my conclusion that you only checked different versions. But yea, a misunderstanding and to be fair, you always have to assume the most simple/stupid mistakes first. Not every user is completely capable and/or tells you the whole truth. I'm glad that your issue is fixed regardless. You could check if there is a sixthsense.bnk file in your res > audioww folder as well. I think that it got created on the first iterations of the installer and is probably useless (and might have caused the issue). But before deleting it, maybe Aslain could comment on that.

My apologies that I didn't get the gist of your text correctly. To me it read like "I've checked and re-checked different versions of the installer", instead of "I've checked and un-checked the mod in the installer". Although, you might say that it's worded poorly. In any case, if you could test it again with the latest installer and make sure that no sound mods are selected, that would be very helpful indeed.

Mods sometimes get checked/un-checked without you doing anything. Just hitting "next" in the installer doesn't mean that only the mods, which you previously had selected, get installed that way. Please take a minute of your time, run the latest installer and actually go down the list of mods. Make sure that things you want are selected and things you don't want aren't. If you don't want to go through all the trouble, simply check if only the sound mods are selected (without you doing anything) and share your findings.

If you're really not using any other 3rd party mods, could you try out if you also get crashes without any mods? Perhaps there's something else causing the crashes, like hardware or drivers. I'm not ruling out mods entirely, as I've also had 1 single crash in like 100 games. Not sure what iteration of the modpack it was though.

I'm not sure if you're trolling me right now or not.. >_> If you're genuinely seeing an issue, you could take a screenshot without any mods and one with the mods, from the same camera position. Because I really don't see a problem with trees having different sizes at all (it's realistic), let alone being caused by mods.

Could you elaborate some more? Maybe it's just me but I don't understand what problem you have. I see trees in the picture but don't know what they have to do with tanks. Also, I think you have "Show vehicle tier" enabled in the in-game settings (general tab > right side > top), which looks to be shining through the contour icons in the playerpanels.

You could check if the same is happening without any mods. If the issue isn't with mods, you should get the crashes within a small sample size as well (like 10 battles or so). Trying out a different game, that is similarly demanding, would also help excluding any hardware/driver issues. If it's mods though, need to wait for Aslain indeed.

Well, at least it's fixed now. =)

Well, I can't read logs for shit, so.. Did you change anything around WoT or your system security between last modpack uses? Did you use any other 3rd party mods/modpacks and may have any remnants of that still in there somewhere? Could check if moving the game to c: (not uninstalling, just cut and paste), running installer as Admin and/or disabling any super-tight security software during installation does anything. Just some things to try out/think about, while you wait doing nothing or play vanilla. =3

Same here, last one shows no issues for me either, even when I added all mods that were causing problems. texts.xc also has the right permissions now.

Same result for this too. So, this file has different permission levels than most of the other random files I've checked. Can't move it or attach it here even. It's read, write and read/run only. Has a user called "NULL SID" on it's list too, if that tells you anything.

RIP me then, I guess. >_>

1st installer: _Aslain_logs - fail.zip _Aslain_logs - working.zip 2nd installer: _Aslain_logs - fail_2.zip _Aslain_logs - working_2.zip Both give the same result. E: Did 1st - working with wrong installer lol. Will add the correct logs. E2: Logs replaced. Still worked.

First installer didn't change anything for me. Mods run with current config but fail if I only add one other mod out of the 3 I found.

Smartscreen is a one-time thing. You allow it once for new software and everytime you run it afterwards it's permitted automatically. Same goes for the installer, have to allow new versions once and then they don't need to be permitted anymore. I ran the installer like 30 times last night, with all kinds of configs and all mods either worked or not, depending on the mods selected. Regardless of smartscreen (I guess).

Test 3 required manual input. required permission via smartscreen playersPanel.xc

Since I too had issues with .07 (just with certain mod-selection), I'll post mine too. Test 1 playersPanel.xc Test 2 playersPanel.xc Had to allow running test2.bat in a smartscreen pop-up both times (Win 10).