Mod Extracting Issue

[Kepos]

Hey, 

with version 2.2.0.1.02 yesterday I got issues with extracting all of Riskynet files, but I thought next version would contain a workarround. Those Riskynet mods were not installed, but the rest was correct. Tried several times including deleted cache, no changes. Unfortunately with today's 2.2.02.00 it got worse. 

The installer brought exception popups for the preview, as if it was not able to extract the pictures. Not for all mods, some showed quite weird colored previews. 
After going forward, I got a load of extraction issue warnings like the one posted. Made a couple of snapshots and included all found logs from the requested list into a ZIP file. Couldn't find xvm.log or python.log. My best guess, the installer was not able to extract the downloaded mod files, what could possibly be declared with access priviliges. However, earlier installers didn't show up with such issues before. 

System is Garuda Linux on AMD CPU and AMD GPU. Playing with LUTRIS and used the 'start exe within a Wine-Prefix' to start the installer, right as the uncounted times before. 

Thx for looking into it! 

Cheers, 

 

Kepos

2026_03_26_AslainScreenshots.zip

[Aslain]

Follow the recommendation from the warning window.

[Kepos]

Well, besides deleting the res-mods folder, I deleted your Aslain folder and all related files in the game directory I was able to find. The issue still persists when installing new with the 2.2.02.01 version. What disturbs me is, that your installer still remembered what mods I used to install before. Where the hack you stored that information, because it is truely not inside the WoT folder? 

[Kepos]

Forum shows no option to edit my former post, so I write another answer. 

Besides the above issue, the game doesn't start any longer. I do see the launcher, but when I hit start, I can only see the first window of the game forever, that's it. 

I can only start the game now, when I use secure-mode without any mods active. 

 

Is there any de-installer, because I deleted the content of the res-mod and any related file of your installer, but there seems to be something missing. Game will not start. 
I really would not like to completely re-install WoT for my lame internet. 

[Theolitius]

start WG center, press game settings, then try check and repair 
see if that fixes your game

[Kepos]

vor 2 Stunden schrieb Theolitius:

start WG center, press game settings, then try check and repair 
see if that fixes your game

Tried that yesterday with 2.2.02.00, but to be sure I've done another try. No changes. Thx anyway for the hint. 

[Aslain]

You can also manually download that file and put to World_of_Tanks_EU\Aslain_Modpack\DL_cache\ overwrite that file there then reinstall. It's not a bug in the installer, it's something on your end.

 

Modpack settings are saved in windows registry.

 

https://repo.aslain.com/WoT/contouricons_Riskynet_TIM_2.2.0.0b.7z

 

[Kepos]

Thank you @Aslain for spending time to find a solution and I agree there has to be something on my side. 

Well, the rights management could be the key to fix the issue. Besides that I should have root permissions, I did now use 'chown' to make the whole SSD my property. Then I was able to delete the registry keys, before it was impossible. So it all points toward rights management. 

Then I tried a new install of your madpack, but unfortunately there have been several warnings about access violation. But that was a bit weird, because the warning pop-up only fired for a few mods. As for the marksman crosshair...it only warned for the yellow version, while the white version didn't. So I stopped the installer, cleaned the registry again to have a virgin game, cleaned mods and res_mods, cleaned the mod folder in the user dir. Had the launcher repair the game files.

Then the game started without any issue...unfortunately without the modpack. 

 

So I'll work on it and hopefully I can locate and rework what is causing this issue. 

Thx a lot to all that have supported my struggle. 

[Kepos]

Just a heads-up. Tested a few other modpacks...all without the access violation issue. 
Tested - ProMod + WebModpack 

Then I tried Aslain again...same access violation as before. 
Just an idea, but...is your installer possibly trying to extract modpacks outside the wine/lutris prefix zone? That would point toward the 00000000 address from my view. 
Then it would be a handicap with Linux and Lutris. But then you may have changed something with the latest 2 versions as I didn't recognize the issue before. 

[Aslain]

No idea bout them, what you mentioned is custom installers. Here it's using 7zip app to extract. Inno Setup in 7.x.x will have fixed internal extraction for a very long paths, so in the 7 I will start using it, and maybe it will help you. I don't extract outside of anything, it's just regular extraction.

[Kepos]

Well, first of all, thank you for taking the time to deal with this issue. 

I'm not not really sure about and am learning about Lutris all the time. So far I know, Lutris builds a virtual box on my disk and places rudimentary Windows with it's paths, so games could install within that paths, not recognizing that there is space outside this box. Not sure how 7zip extracts, possibly it tries to create a seperate space it could delete afterwards. Just a hypothesis so far. Linux, Garuda in my case, could read and extract 7zip, preferable using tar or something similar. However I'm using the 'start EXE within wine-prefix' command, 7zip may not respect the given Lutris borders for it's extraction and trying to extract on the rest of the disk or possibly on the disk containing my OS...where Lutris doesn't have any rights. That's the closest theory I got in the moment.

What I encountered while using your installer with a fresh clean install was, that I was able to choose ...let's say 5-10 (non xvm) mods before the access violation started. So, I assume that the reserved extraction space has overflown. As the simple choice doesn't install anything, but had to extract the preview pictures, I'd place the cause of the issue in that direction. Together with the access violation also the preview pictures got corrupted in some way. What also points towards preview pictures for the assumpted overflow. Do you have any measures to tweak the size of the extraction pool? I guess not, but asking questions is never wrong. Isn't it?

What I can do, is to start a fresh install without preview next and watch the outcome. 

[Aslain]

It looks like it's not a bug in the installer itself, it’s a local issue with your Wine/Lutris setup or permissions.

Try:
- Remove contents res_mods/2.2.0.2/ mods/2.2.0.2/, Aslain_Modpack
- Clean up the Wine prefix (or create a fresh one) and make sure Wine/Lutris has full read/write access to the game directory

This kind of error is almost always related to corrupted/incomplete cache, restricted permissions, or a broken Wine prefix, not the installer. If the problem persists only on Linux, test with a clean Wine prefix outside of Lutris to narrow it down

 

Try that: https://www.mediafire.com/file/nl2gmucbgb725zo/Aslains_WoT_Modpack_Installer_v.2.2.0.2_03_x86.exe/file

[Kepos]

Thx for the testing path and the next availible version. Permission is truely the key. Will try the new Lutris prefix next and am crossing fingers not to ruin the WoT installation.