Almace

If you haven't done it already, you can edit the paths.xml in the main WoT folder (preferably, you make a backup of it first) and delete line #54 <Path>./res/packages/hangar_premium_WG_Bday.pkg</Path> Then some other garage mods will work. However, some older ones might not work, as they are missing files that I don't know how to create (since I'm not a programmer).

I don't think that I've ever seen something like that. Only numbers that are usually displayed, are the distance to your enemy (at which your crosshair is pointing) and maybe pen / armor values. - At least in the location you described, between crosshair and equipement - Since you normally have the viewrange circles on your minimap already. Not much of a point to have the actual values displayed seperately, outside of the hangar. Like your penetration: 150 vs enemy armor: 210 would be displayed like: 150 / 210 The mod you speak of might exist, I just haven't seen it yet.

Ok, so if you want to use one of the colors that already exist in the colors.xc file and have it yellow/orange, you can take the same color as for platoon-member damage. For that, you just copy the color code from "squadman_enemy_hit" (which would be 0xB85C00) and paste it to all the lines that start with "player_..." (unless you want to keep the purple damage [the default color in colors.xc for your own dmg] for anything, like kills or team-damage done by you or something) "damage": { "ally_ally_blowup": "0x0099CC", "ally_ally_hit": "0x0099CC", "ally_ally_kill": "0x0099CC", "ally_allytk_blowup": "0x0099CC", "ally_allytk_hit": "0x0099CC", "ally_allytk_kill": "0x0099CC", "ally_enemy_blowup": "0x990000", "ally_enemy_hit": "0x990000", "ally_enemy_kill": "0x990000", "ally_enemytk_blowup": "0x990000", "ally_enemytk_hit": "0x990000", "ally_enemytk_kill": "0x990000", "ally_squadman_blowup": "0x0099CC", "ally_squadman_hit": "0x0099CC", "ally_squadman_kill": "0x0099CC", "enemy_ally_blowup": "0x005500", "enemy_ally_hit": "0x005500", "enemy_ally_kill": "0x005500", "enemy_allytk_blowup": "0x005500", "enemy_allytk_hit": "0x005500", "enemy_allytk_kill": "0x005500", "enemy_enemy_blowup": "0x990000", "enemy_enemy_hit": "0x990000", "enemy_enemy_kill": "0x990000", "enemy_enemytk_blowup": "0x990000", "enemy_enemytk_hit": "0x990000", "enemy_enemytk_kill": "0x990000", "enemy_squadman_blowup": "0x009900", "enemy_squadman_hit": "0x009900", "enemy_squadman_kill": "0x009900", "player_ally_blowup": "0xB85C00", "player_ally_hit": "0xB85C00", "player_ally_kill": "0xB85C00", "player_allytk_blowup": "0xB85C00", "player_allytk_hit": "0xB85C00", "player_allytk_kill": "0xB85C00", "player_enemy_blowup": "0xB85C00", "player_enemy_hit": "0xB85C00", "player_enemy_kill": "0xB85C00", "player_enemytk_blowup": "0xB85C00", "player_enemytk_hit": "0xB85C00", "player_enemytk_kill": "0xB85C00", "player_squadman_blowup": "0xB85C00", "player_squadman_hit": "0xB85C00", "player_squadman_kill": "0xB85C00", "squadman_ally_blowup": "0x0099CC", "squadman_ally_hit": "0x0099CC", "squadman_ally_kill": "0x0099CC", "squadman_allytk_blowup": "0x0099CC", "squadman_allytk_hit": "0x0099CC", "squadman_allytk_kill": "0x0099CC", "squadman_enemy_blowup": "0xB85C00", "squadman_enemy_hit": "0xB85C00", "squadman_enemy_kill": "0xB85C00", "squadman_enemytk_blowup": "0xB85C00", "squadman_enemytk_hit": "0xB85C00", "squadman_enemytk_kill": "0xB85C00", "squadman_squadman_blowup": "0x0099CC", "squadman_squadman_hit": "0x0099CC", "squadman_squadman_kill": "0x0099CC", "unknown_ally_blowup": "0x005500", "unknown_ally_hit": "0x005500", "unknown_ally_kill": "0x005500", "unknown_allytk_blowup": "0x005500", "unknown_allytk_hit": "0x005500", "unknown_allytk_kill": "0x005500", "unknown_enemy_blowup": "0x990000", "unknown_enemy_hit": "0x990000", "unknown_enemy_kill": "0x990000", "unknown_enemytk_blowup": "0x990000", "unknown_enemytk_hit": "0x990000", "unknown_enemytk_kill": "0x990000", "unknown_squadman_blowup": "0x005500", "unknown_squadman_hit": "0x005500", "unknown_squadman_kill": "0x005500" },

I just prepared a custom mod file for it too, just earlier. But then I saw you added it with newest version, you sly fox! :P

Looks like they found a fix for it and Aslain implemented it in the latest version. Give it a shot.

+1 for accuracy. ;)

Well, according to http://aslain.com/index.php?/topic/58-client-hangs-up-on-loading-screen/page-2 the issue could be resolved for that guy, running as Admin. As for antivirus, some of the software is known to be overprotective and prevents certain files from being executed (usually the big stuff, which you pay lots of money for). I would have to dig through the old forum, since I think there was a case like that once but I don't really feel like it. It's easy enough to do and the last thing on your list anyway, if you're desperate. So I still stand to those 2 options and it's worth trying as much as you can, before having to file a report and maybe wait for days to get it fixed, when you could have fixed it within minutes by yourself. E: Fixed it, Grinch!

Hi, doesn't look like there is a general consensus about it. For some ppl it's fixed somehow (for unknown reasons), another person fixed hang-ups doing right-click > run as Admin on the game client and others don't report back for days. So, I can't see consistency in there. Since I can't confirm a lot of issues, I can also just say the same things if some unknown crash/hang-up/problem happen: - try to use latest version of the installer - always use clean-install at least (with the option in the installer) - clean out DLC content and re-download it - clear game cache (with the option in the installer) - avoid using additional mods or at least use this installer here first > check if everything works > add another mod > check if it works still > and so on - try using right-click > run as Admin on the installer and/or the game client - try disabling your antivirus for the installation The last 2 can be security risks for your system but since Aslain is an IT guy, it's fairly safe to assume that he doesn't spread infected files. I still recommend that you don't do like online-banking and stuff, while antivirus is down and while playing WoT. :rolleyes: So if everything of the above fails, there's not much left but to report issues with the help of detailed information and the log files and wait and see, if they can be replicated and fixed.

Yea, if you're in no rush, just wait it out. Just figured I'd mention it, so ppl can still get what they want; can also keep this in mind for future events that alter your hangar.

You can actually edit the paths.xml in the main WoT folder and delete line #54 with <Path>./res/packages/hangar_premium_WG_Bday.pkg</Path> in order to make other hangars work. E: I always recommend making a backup of game files anyway, before you edit them.

I had this too, when using an early version of your pack and later adding multiline carousel manually. Can recreate/fix the issue installing/uninstalling that mod as well. So, that should be the source of the problem.

Some corsshair mods only use the first 3 options of the ingame settings. So if you pick like option number 5-7 for the middle part of the crosshair or so, it won't be displayed properly. Try out using mostly the first 3 ingame crosshair modifications and see if that helps any.

No, it's cool, I always thought that the mod replaced the game version of it or something, being more accurate or so. =3 I'm trying it out and it's not too bad. Last night I had a little bit more lag and it was pretty bad; also being new to me and all. Seems to be good now though, hardly notice it once I got used to it.

Did you try to run the installer itself as admin? Because that's what I was referring to, in case something on your system prevents mods from being installed. So does just running WoT as admin now work without hang-ups?

Idk, just looking at the shapes of the 2 individual crosshairs, I would say that I had both but locked in the same place; if that makes sense. Like, the server cross kinda looked like both the mod and the server cross put together but I definitely never had it that there were actually 2 crosshairs delayed like that when turning tracks and/or turret. However, hard to try to figure it out now, since I don't have any footage to analyze and never paid that much attention to the specifics of the crosshair. I only noticed it last night, that I suddenly got 3 corsshairs in total, while not touching the ingame setting for server cross in months and always installing fancy blue cross mod. So I didn't ever change anything and now had those 2 crosshairs.

I see, thx for clearing that up for me then. xD Still wondering though why it never was like this before, even though I never changed anything (always had it activated ingame and used the mod).

And that's normal? Like I said, I've never had it like this before. Starting to doubt myself now but I think I would remember 2 crosshairs floating around, having 3 crosshairs in total. I guess maybe one of the crosshairs never worked for me then, up until now. <.<

Yes. I've never had 2, with the ingame one enabled and the mod installed. Has always been the one you point with and then 1 server cross for me.

I also might have to add, that this didn't show up in replays. After changing to Meltymap's, I ran a replay to check out if it changed and there was only 1 server cross. Ingame, however, there were 2 again.

Nothing outside the installer. I've tested Dikey93's and Meltymap's and had it with both. Didn't test others, since I figured that the server cross mod is seperatly anyway.

Not really much of an issue but I experienced that you get 2 server crosshairs now, if you activate it ingame and choose to have it in the installer as well. They both move slightly delayed too, so, not sure which of them is more accurate. Obvious fix is to disable one of them and I chose to just disable it ingame and the modded one still works too. I guess my question is, did the modded server cross overwrite/disable the ingame one in past versions and is just not doing this anymore? Or is something wrong with the mod itself, since you are supposed to have the ingame cross enabled, in order to use the modded one (at least you used to)?

I had a weird thing last night, where the zoom seemed to be a 1-step zoom, where it went from 0 to 30x and zoomed from 30x out more than "0", both in one scroll. - I use 30x (6 steps, 2-30) - This only happened on the very first battle after installing the mod and went away a while still in the same battle. While the battle was going, I went to check if the zoomX file had only one or two steps in it, for some reason, but it didn't. So I returned to the game again and it suddenly was working as intended. Is it possible that the script was just loading slowly or something? Didn't really want to create a new topic for that, since it went away quickly and only happened once. So, sorry for hijacking this thread. :ph34r:

Might also add the obvious SafeShot mod, since it's in Aslain's pack and greatly helps to avoid a lot of accidental team damage. Personally, I don't have a use for it very often but it does happen to trigger every now and then. What's more, it actually prevents you from rage-shooting others as well and displays a message in chat, that let's your allies know when they might be in the way of your shot.

Well, stats are stats. They can give you a guideline of how well you do and if you suck, then that's just how it is. You can certainly improve with help here and there but you probably don't have much of a talent. Which is ok too, since not everyone can be perfect in everything. The only thing that matters is having fun, imo. If you suck and still can have fun, go for it. If you don't have fun, then try to improve and maybe have a little bit more fun while learning or when getting better. Maybe you will never have fun, but that would be the point in stopping to do what you're doing, I guess. Life's too short for trying too hard for things that are just not meant to be. But that are only my 2 cents. Maybe it already helps not caring too much about how other ppl see you but more about how much fun you can have doing something (whether you're good or bad at it).

Still good that you brought it up, never know if ppl are aware of it already or not. 30x isn't too bad either, I personally don't like how close everything beyond 30x is but that comes down to taste, I suppose.