rustyJunk

I am happy to report that the next patch fixed at least *my* problem.

EDITED - correction: I thought I had his same problem but I don't. Instead I see the following, which is almost the opposite. Weird. - I see tank and player names fine on minimap. I also see all the information correctly on the HUD. - I DO NOT see tank names or icons on the panels in v1.10.1.4 #01. I tried a restart just in case, it did start with the modpack being up to date. The problem persists. I will just use safe mode until the next update and make a new thread with logs and screenshot if it remains. EDIT 2: - Cap circles also not displaying in this update when Aslains is active.

I ended up having to uninstall everything, delete the folders, then reinstall everything from the Gaming Center down... and all appears to be fine now. Fingers crossed.

After today's WoT patch I am able to start in Safe Mode but not with the modpack, even after installing (v1.10.0.4 #08). Suggestions?

Cool beans. Bye bye icons :)

Is it possible to get just the clan name instead of the icons perhaps? Worst case I'll just disable the clan icons, as I don't really rely much on them.

Images: https://imgur.com/gVh0VbT https://imgur.com/KN8XCbS The very long portions are "extracting" and "finalizing" (note, looks like I messed up one of the screenshots)

will do, and will time it to get precise measurements. Probably tonight when I have some free time.

Mainly it is the installation step, after having selected all the options.

I've been using Aslains for a month or two and noticed that the process of installing the package took longer with each patch, to the point of taking what feels like 10x as long as the initial install. (not that nothing else on the computer feels slower, only the Aslains install process) Is this normal? Is there a way to return it to its initial speed?

Thank you, worked perfectly.

I really like the feature that shows the player's name (and color) on the minimap. But the truncation of the name drives me nuts and I have not been able to find a configuration setting to display the full name. Any hints?

Thank you very much. It was not Bitdefender, turned out that a reboot was what that was needed. Weird. I was not too worried about the mod being safe, just the false detects were a little annoying. The reinstall issues were more worrying though.

Thanks. I ended up deleting the whole Aslains folder. I figured that would be enough since bitdefender would not let me run the uninstaller and I was going to reinstall anyway. Sadly now the installer fails because it wants to move Uninst000.exe to the newly recreated folder and for some reason it get Access Denied (even with Bitdefender completely turned off). When I skip it... it then fails trying to write to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\Aslains_WoT_Modpack_Installer_is1. RegSetValueEx failed; code 5 Access is denied. I checked in regedit... and there is no Aslains_WoT_modpack_installer_is1 key there either. No idea why it is failing with access denied. I contacted bitdefender and there are no quarantined files. They say it has to be something being set by the installer as read-only that did not get unset when I deleted the folder instead of using the uninstaller? So... I can't reinstall Alsains. Any suggestions to how to fix this? Or have I lost all ability to use the Aslains modpack? I hope there is a fix. Where does the installer put the files temporarily before moving them to the destination Aslain_Modpack folder?

Just letting you know of the following issues: - Windows alerts that the Aslains installer is unsigned and thus potentially malicious. - Bitdefender detects an exploit in unins000.exe. If these are innocuous... I suggest fixing them so that they don't trigger these kinds of alerts.