Miac

Because of being forced to use very high resolution (1920x1080) because WoT does not have 1280x720, all of my HUD is too small to read. Forcing the resolution trough "preferences.xml" \AppData\Roaming\Wargaming.net\WorldOfTanks did not work as WoT resets the resolution even if file is set to read only. However, you can scale interface in the same file, but there occurs another problem: some mod elements remain small, or they are moved in weird position. 1. The "enemy seen" marker on the players panel is in the middle of the screen. Any way to move it back to the right side, next to the players name? 2. Crew Skill Informer remains on the same place and same size as usual, except it is covered by the upscaled tank & modules icon on the lower left side. How can I move it a bit to the right?

In my options, I have disabled "Enabled expanded minimap features and now it is working"????

When zoomed in, you can see that every alternative minimap feature is overshadowed by the vehicle name. I zoomed in at maximum in here, but when you play normal, you can barely see what's behind the vehicle name.

Sent PM

Here's the "_Aslains_Installer_CompList.txt" file. I tried also with Arab numbers version but the problem persists.

When you press Alt, the vehicle tier is not shown. Instead, only the vehicle name with shadow is displayed. Edit: It seems that You have to disable "Enabled expanded minimap features" in options....

I can confirm that it is indeed a config issue. If you want to enable Armoring Extended for all tanks, do the following: 1. Navigate to "\World_of_Tanks\res_mods\0.9.7\scripts\client\mods\" folder 2. Right click on "armoring_extended.xml" and click on "Edit" 3. Edit line 14 by changing <only_ht> true </only_ht> to <only_ht> false </only_ht> 4. Save the file

...or did I miss something in changelogs?

There is again problem with both of these crosshairs: 1. Dellux is missing the part of the crosshair you aim with (the indicator) 2. MeltyMap's Green is unreliable - corsshairs do not align many times (as if you were aiming at the sky). To correct this, you have to leave and enter the sniper mode again. I am going to go test the regular, blue MeltyMap's crosshair now EDIT: Blue MapMelty's crosshair is FINE!

Yeh, very sad... hopefuly someone will manage to continue it...

Just tested out the new version and it is still the same. Timer counts down to 1 and stays like that. It should, in fact, show "4.22" after it reaches 0.

I noticed this as well. Sometimes penetration is green, sometimes it is red. And I do remember also that hit decals have been updated in 9.7.

Well, I actually reverted to one from here The latest one from your installer just freezes the reload timer. On MeltyMap's crosshair reload time in decimals is displayed only after the numbering countdown ends.

I reverted back to old sights.pyc and it is working.

Holy moly, I just found out instructions on how to get the armor calculation data for tanks that weren't "programmed in".... and they're hefty I do not see myself actively going to look for these for every tank that is not in the "MeltyMapProtractorSetting.xml" file, but as time goes by I might try to fit in one by one. For start I will collect the list of tanks that I notice don't have armor calculation implemented.

I will try and take care of that. First I have to gather which tanks are missing the Armor Calculation(by spectating them in game, or if someone knows a better way?) and than I will fix them. It will take time but I will work on it.

That did the trick! Thanks! I didn't rename the usa_Pershing, I added a new line so it looks like this: <vehicle side="76" arc="52" front="102" name="usa_Pershing"/> <vehicle side="76" arc="52" front="102" name="usa_A35_Pershing"/> I actually did see an icon with that name, but, for whatever reason, I decided in my mind it probably wouldn't work. Sometimes you just need a push from someone else :) EDIT: I will make a list in here of all the vehicles that need to be fixed in similar fashion. Anyone can check this by using the mod in spectator mode. 1. Pershing 2. T37 3. T-54 Mod. 1 4. Firefly 5. AMX 30 6. Obj. 704 7. Pz. III 8. T-34

Thanks for all the tips. I have seen now that the pershing is entered correctly in MeltyMapsProtractorSettings.xml but it does not work.The problem lies elsewhere. I guess I can live with it.

I am not sure if this is a bug or not but, for example, my Pershing used to have armor calculation in 9.6 and KV-1 did not. It is the little blue thing here: I sold KV-1 and, after 9.7 came out, pershing does not have it. I tried applying even only MeltyMap's mod on vanilla WoT and it still didn't work. Deleted WoT cache, everything, but it does not work. Does anybody have idea how to fix this? p.s. I don't know where to ask else, so please don't mind. It IS part of Aslain's mod pack after all EDIT: I found this on the author's website: Attention. In order to display Effective armor calculation Vehicles have to be programmed in VehicleData section of MeltyMap's Protractor Mod configuration file, "name" must have same vehicle name as the tank icon name. Refer to included Vehicle_Names.txt file or comments in bellow of config file. How can I find the tank icon name? if I understand correctly, i have to edit a line in "MeltyMapProtractorSetting.xml"

When it comes to mods outside of the Aslain's pack, I do not know what is worse: WG's policy on mods or the fact that even if you use the worst kind of mods (destructed objects marker, tracers, etc.) you risk only getting a temporary ban, a week or so for a first time offender. Since the detection and policy on mods is so blurry, most people get away with it never getting caught. If we are talking about Aslain's modpack here, there are no mods which would be considered downright cheating but I will give my opinion on what I think are mods that give way too much advantage: 1. Zoom In and Zoom out mods - Zooming in makes it easy to hit weakspots; Zooming out indefinitely makes it so you can see the spotted enemy's precise position over tall obstacles like buildings which usually would mean you'd have to move closer - both are unfair IMO 2. Direction indicator extended 1.07 by spoter - this mod TELLS YOU when you have a clear shot on an enemy which you would normally have to look for on minimap and check if you have a visual on it manually. The fact that it marks multiple enemies at the same time is even more unfair. 3. ALL damage panels except Recieved damage announcer 2.5 (NA legal) - all of these mods will tell you name of the tank who shot you even if they weren't spotted. I did a research on the NA forums and devs said that these mods mine data that is normally not available to the client. 4. Minimap tank view extended - basically tells you where the spotted enemy is looking at where you'd normally have to check for yourself by looking at it instead of the minimap 5. Any mods that mine exact reload time or other enemy player information (OTM reload??) Again, it is very difficult to claim which are unfair and which are not especially when you have to rule by your own ethic instead of having a clear policy from WG EU.

Answer=Backspace :D

The stuttering problem (crosshair flicker in sniper mode) is fixed when I extract the files from this version - this eliminates the hardware/driver problem. However, this is the complete version of MeltyMap's Math Mod and it overwrites a lot of Aslain mod pack settings, including the Zoom-out camera settings and more. If I knew which files were only for crosshair part of the mod, I could pinpoint the problematic file.

I have not used any updates BEFORE the installation of Aslain. I always uninstall old Aslain's modpack version and empty out "res_mods" folder before I apply the new installer. In this case I have installed Aslain's modpack first and overwritten files from MeltyMapsMathMod09701.zip. I overwrote all files from the MeltyMapsMathMod09701.zip archive and problem was fixed but sniper zoom mode configuration was overwritten as well. In the end I excluded to overwrite any files with "Zoom" in it's name from the archive. Problem was fixed as well which means the "Zoom" files are not the culprit.

@Aslain, there is a problem with MeltyMap's crosshair mod - the crosshair stutters and micro-moves to every side in sniper mode. I managed to fix the problem by overwriting files from installer with files from latest version of the mod but then also the configuration of the crosshair (zoom settings) are overwritten.

Hello there, by a coincidence I was forced to switch to another crosshair today which happened to be MeltyMap's Mathmod Crosshair. Here's my explanation, please correct me if I am wrong. The slope angle marker takes into account enemy's armor thickness and your penetration power. Possible angle of penetration is measured on the crosshair from the upper part of the crosshair to the right part, making a total of 45 degrees angle: |_ The thicker the enemy's armor the more narrow will be the angle you can penetrate it from. Here's two pictures to demonstrate. In the first picture you can see that our gun can penetrate 22mm of armor and the enemy armor on the spot we are aiming at is only 15mm. The angle marker becomes green and it indicates that we can penetrate this armor from a wide angle. NOTE: The green angle marker has a notch in the middle - to the left and right of the notch is how this crosshair takes into account WoT's mechanic of 25% of more or less chance of penetration. This is to say that the notch is theoretically anywhere on the green marker. Now, when we move the crosshair to a more thicker part of the armor which is 20mm, you can see that the the angle of penetration is more narrow which means you should probably fire only when the target is not much sloped. The lower your penetration is, smaller is the arc of the angle you can penetrate from. The crosshair DOES NOT take into account the actual angle at which you are aiming at the enemy. You can see this here. I am aiming at the t29 turret cheeck from an extreme angle and the crosshair is telling me I still have the chance to penetrate.