HockeyPhool

Seeing the same issue with v12.4.0_01. I suspect Banner Switcher mod, but haven't been able to disable it yet to prove it.

Thanks, @Quaksen. I had looked for an option several times without success. This time I switched "Alternative Interface" from "Off" to "Adaptive" and now I have a range finder.

Sure would be nice to know what the options actually do!

In the past few mod packs I have lost the range finder in the HUD. I checked both dynamic and static crosshairs and the range finder is missing in both cases (see attached screenshots). I did select the "More Visible Range Finder" option on installation. This has worked fine in the past.

Attaching logs.

Aslains_WoWs_Logs.zip

I recall seeing this issue a couple of weeks ago. I did not investigate it further, but I suspect it *may* be related to Nomogram's dynamic crosshairs. I quit using that crosshair because it was causing terrible graphics performance (especially in scenarios), and since I quit using it I haven't seen this issue either.

The "keep_calm" dynamic crosshair is a good alternative. Maybe give that a try and see if this issue disappears as well.

8 hours ago, Iceman said:

I just checked that one, there isn't any instructions like the others.  Perhaps Aslain or MajorRenegade can answer your question.

 

Usually you see something like this in the mod installer:

 

Well, shucks: I have *never* noticed the big gray "Select Crosshairs" button in the game settings! Sure enough, that's what's necessary to enable the crosshair I installed. 

FWIW: you have to select the "Type 1" static crosshair to see the Krab V3 crosshair.

Thanks for pointing me in the right direction, Iceman!

HockeyPhool

21 hours ago, Iceman said:

On the mod you selected, there should be some notes (at the bottom I think?) that tells you what in game crosshair you have to select to get the modded crosshair to show.

Thanks for the reply, Iceman. I re-ran the installer with the preview window enabled, and I do not see any instructions like what you mentioned. However, I'll go take a look at in-game settings to see if there are any that make a difference.

FWIW: The crosshair that I *do* get is not the WoWS default, nor is it like any of the ones depicted in the modpack installer. :-(

HockeyPhool

I have installed the WoWS modpack v7.12.0_05. I selected the Krab v3 crosshair when I installed the modpack, but the crosshair that's actually displayed is something else entirely as shown in the attached screenshot. Is there another mod I chose that's overriding my crosshair choice? I confess that I don't know the WoWS mods nearly as well as I do the WoT mods.

I did completely uninstall the modpack and play a game without mods (and saw the default crosshair). I then reinstalled the modpack, played a game, and took the attached screenshot.

Thanks!

HockeyPhool

Aslains_WoWs_Logs.zip

16 hours ago, bubs79 said:

strange that as my activation is mouse wheel click by default , but think the mod uses wat u choose ingamesettings

I change it *FROM* middle mouse *TO* 'B" :-)

13 hours ago, bubs79 said:

doh lol    

 

@thebluescreenofdeath yeh I do that for my other mods   ,  

 

wat can u config for battle assistant ?  what changes can u make ?

I like to change the activation key from MOUSE2 to KEY_B, for one thing. There are several other options (such as always following the projectile, the key to activate projectile following), but I haven't found good documentation for all that they do.

1 hour ago, Quaksen said:

@bubs79 you're mistaking Battle Observer and Battle Assistant - two vastly different mods.

 

The #06 modpack, installed the config file just fine for me. (Maybe you need to run the game, for the config file to be created? Not sure on that part, actually.. I did run game before checking..)

Good call, @Quaksen! I just start WoT, quit, and now the config file is present. 

Just now, bubs79 said:

the config file is actually ingame now,     click the small box  on bottom right corner  in garage and select battle observer  and the lconfig file appears and u can edit whatever u want , 

wish all mods were like this as its so easy to do 

Thanks, bubs. I'll give that a try this evening.

However, I don't agree that it's "easy", because it means I have to remember to edit the configuration in-game every time I update my modpack. With a configuration file on-disk I can have a template with  my desired configuration and then use WinMerge to apply my changes to the mod config. I'm already doing that as part of installing the modpack.

For some reason, the installation of the "Battle Assistant" mod does not always leave a configuration file. At one point in the past two days I found the configuration file here:

c:\Games\World_of_Tanks\mods\configs\battle_assistant\mod_battle_assistant.txt

However, I just installed 1.0.0_06 and there is no configuration file for this mod. I went back and reinstalled 1.0.0_03 and 1.0.0_05 to see if either of those versions left behind the config file, but neither of them did. I can't explain why there *was* a file the other day, and I don't understand the new mod packaging enough to investigate further. I can see in the installer log that the mod *was* installed, and I confirmed that the mod works with the default activation button (MOUSE2). 

I realize this may not be an issue with Aslain's installer but with the original mod. I cannot find any way to contact the mod authors on the Armor Inspector website or I would raise the issue with them as well.

Aslains_WoT_Logs.zip

15 minutes ago, guido22 said:

Turn off Malwarebytes to delete the files

Thanks for reminding me that I have Malwarebytes running. I just added 'res_mods/configs' as an exclusion and will see if that resolves the issue over the next few modpack installs.

I cannot install WoT modpack v9.19.1_09. After selecting options and beginning the installation, the installer attempts to extract the binaries 'sed.exe' and 'patch.exe' in the Aslain's XVM configuration folder. It keeps throwing the errors found in the attached screenshots. It's complaining that it cannot rename a file in the destination directory and that the file already exists.

I have tried the following without success:

1. Clicking "Ignore". The installation finishes, but not all of the modpack is correctly installed (no carousel configs, tank icons are reversed for enemy team, no hitlog or damagelog, etc).
2. Deleting the existing file, then clicking "Retry". The installer extracts the file but immediately re-throws the same error.
3. Clicking "Abort". The installer rolls back its changes and exits.

I'm attaching logs, and am going to install the previous version of the modpack to see if it will still work. I had to attach logs manually because the Archiver app failed because it couldn't reinstall 7za.exe

UPDATE: I restarted my computer and was able to install v9.19.1_09 successfully. That's not a pleasant workaround, though>

HockeyPhool

_Aslains_Installer.log

_Aslains_Installer_CompList.log

_Aslains_Installer_Extractor.log

python.log

Thank you very much!

Hey there Capt Black! I'd love to have your steam code for The Witness!

HockeyPhool

54 minutes ago, Quaksen said:

Maybe it only happens on initial client loading? That it sometimes goes wrong... or did you experience it mid-battles previously?

The one time it happened it started at battle loading - no pre-battle summary although I could hear the countdown timer. 

22 minutes ago, HockeyPhool said:

 

I'll do that if it happens again. I have been using that crosshair since 9.17.00 (since J1Mb0's isn't updated).

 

I also reinstalled without "Spotted Vehicle Direction on Aim Circle" and played one match. That match was fine, FWIW

Several battles in, no problems.

3 minutes ago, Quaksen said:

HockeyPhool, try without;

            Crosshairs
               Standard crosshair, with better timer and more
Because crosshairs script has been messing things up - but not every time you play.. it's hit and miss, it seems.

I'll do that if it happens again. I have been using that crosshair since 9.17.00 (since J1Mb0's isn't updated).

I also reinstalled without "Spotted Vehicle Direction on Aim Circle" and played one match. That match was fine, FWIW

I am also having this problem. I am attaching logs from installing 9.17.0.1 #03. As far as I can recall, the only difference between my previous install and this one is that I selected "Spotted Vehicle Direction on Aim Circle" mod. During my match, that mod was functioning. I am going to try reinstalling without that mod to see if the game works correctly.

_Aslain_logs.zip

python.log

I've also noticed that it takes a very long time to launch the installer. I just disabled Defender before installing the latest modpack, and the installer launched right away and zipped through its screens very quickly. Thanks!

I just encountered the same issue. I checked the 'C:\Games\World_of_Tanks\res_mods\0.9.15.1.1\scripts\client\mods' directory before dismissing the error popup, and there was no 'stat' subdirectory.

Attaching logs.

_Aslain_logs.zip

I rarely click "Show Descriptions" unless I want to see the image previews. (It's in the PMOD Battle Results Informer description, BTW)

I'll try to remember to view the descriptions more often. It would be nice to have text in the configuration dialog that warns of incompatibilities like this, but it's not much on an inconvenience.

Thanks!

I've noticed this problem in the last few modpack releases (all 9.15.1.1.xx?). When I run the installer, my previous chat mod selection (battle results reporting) is never checked.

It's very minor but I figured it's worth reporting.

_Aslain_logs.zip

python.log

3 minutes ago, Quaksen said:

NoScroll isn't part of PMOD anymore. It's been added to World of Tanks itself.

Find it in the WoT Settings.

Thanks, Quaksen. I checked the options log and saw the setting listed so I assumed it was still in the mod pack.