nixxxie

PS: seems that it IS indeed working outside render distance, i finally met some enemies "in black", loading slower than i...

Then i missed the adjusting part. I will check this, too. BTW: why there are no number values upon 1st spotting, but bars are drawn with correct lengths (taking lengths from the same macro)?

I'm not a coder enough to talk about it and i only found very old source (8.9), but shouldn't you look at this function? def onHealthChanged(self, newHealth, attackerID, attackReasonID): 294 if newHealth > 0 and self.health <= 0: 295 return 296 elif not self.isStarted: 297 return 298 else: 299 # Update Tank Health 300 damage = self.__tankHealth[self.__battleID] - newHealth 301 self.__tankHealth[self.__battleID] = newHealth 302 303 if attackReasonID == 0: 304 self.damage_announce(attackerID, damage) 305 306 if not self.isPlayer: 307 marker = getattr(self, 'marker', None) 308 if marker is not None: 309 g_windowsManager.battleWindow.vMarkersManager.onVehicleHealthChanged(marker, newHealth, attackerID, attackReasonID) 310 self.appearance.onVehicleHealthChanged() 311 if self.health <= 0 and self.isCrewActive: 312 self.__onVehicleDeath() https://github.com/partap/WOTDamageAnnouncer/blob/master/src/vehicle.py#L323 Anyway, i will check this with some friends in training room and report. You surprised me. PS: you definitely know maxHealth of neverspotted tanks, xvm reports this - idk how, because it returns no value, but still draws correct length bar and doesn't adjust it upon first spotting (as far as i noticed). PS2: you were right, sirmax, i feel cheated , It always reports full health for unspotted tanks - worst case scenario, it seems. And i never noticed for a year...

I had to dig deep in my screenshots folder... I've been using this mod from the very beginning (like a year?) and you still don't believe me :P ... This is even better as it is after death, hit reported on spectator, by FV304 arty with HE, clearly never spotted (white square). Still, better download the mod yourself, you can sneakpeak into the code then ;) . http://i.imgur.com/xsloFPx.jpg

I told you that on numerous occasions... Just install the mod yourself (EU version), edit config to display HP (i don't remember what is in default) and enjoy chat spam :) . http://forum.worldoftanks.eu/index.php?/topic/299941- Game server reports lots of weird stuff, which you'd think it shouldn't... IIRC it also reports equipment used by dealer, so you can take rammer into account in reload estimation (no crew perks/base skill, though...). PS: based of this we can extrapolate if it doesn't report dealer's HP on misses into ground too, if they are within render distance...? Or at least on hits on other tanks withing render distance - both allies or enemies. Interesting thing to check.

Yes, out of render range, because validity of HP data is directly related to that - so there is a way to indicate that.

Omegaice again ;) . You can get even HP of unspotted enemy outside of render box, if he hits you. Allowed both on EU and RU, banned on NA. IDK if it is possible for both hitter and receiver being outside of render box - i suspect not, there is no reason for server to send such info.

Great :) . Another round, from today: 1. Due to HP reporting mechanics, it would be useful to have {{rendered}} macro to have instant notice if value/bar is obsolete or accurate. Or, maybe i can talk you into reporting more HP values obtained in other ways :P ... 2. This is connected. In 5.3.4 this: { "x": "320", "y": 3, "format": "<font size='12' color='{{ready?#CCCCCC|#000000}}'>{{hp%4.4d|____}}</font>", "alpha": "{{alive?100|0}}" }, upon battle startup reports all enemy tanks in white "____", always (while some of allies are reported black, only with number; so i know it works) - obviously they are outside render distance. Seems that {{ready}} macro works only in render distance too which limits its usefulness. Or is it because you are updating ears only for rendered players and macro by itself works ok somewhere else? 3. I just checked macros.txt and it says that {{gun-marks}} works for spotted vehicles only, too. Why? It's not different from any other statistic macro.

I am currently tinkering with new release config and of course i felt a sudden urge to share my valuable ideas... So tiny this time, that not worth separate threads. 1. Could you copypaste code for "none" section of playersPanel and create "none2" for alternate mode? Other sections are heritage of vanilla game and it seems reasonable to allow two fully customizable versions. 2. I haven't checked yet (still reluctant, although getting closer and closer), but i am hearing that "none" doesn't allow interaction with players lists (reporting, adding to friends etc)? Could it be possible to create invisible field with defined size that would act as such? Sth. like "width" in other modes? Or some macro for extraFields?

Yea, only my xvm.log behaved strange and it took me a while to find out that the whole dump was after closing the game... PS: i just noticed that it doesn't update on enemy tanks upon battle startup - all are white while some of my teammates aren't. Does it work only on rendered tanks, too?

Seems to me that this way of using macros is... sub-optimal. XVM either auto-detects language on startup or has it forced in config. So, logical step is that all macros should already be taken from respective language file instead of forcing it by {{l10n:macro}} command and plain {{macro}} should be enough. Quite the opposite, if we want to force some specific message to be fixed in one language (although it bothers me why, but let's assume that in consistence with current functionality) it should be {{macro:LANGUAGE}} eg. {{ready:EN}}.

Thanks, seems to work now. BTW, it took me two days to find this bug, xvm totally refused to load the whole config on the very beginning - login screen. Seems, that now xvm loads whole config at once - it would be a good idea to display errors on login screen, or at least in notification center.

New xvm doesn't like this color definition: { "x": 320, "y": 3, "format": "<font size='12' color="{{ready?'#CCCCCC'|'#000000'}}">{{hp%4.4d|____}}</font>", "alpha": "{{alive?100|0}}" }, How to do it right? You surely know what i want to achieve, unlike my computer ;) .

I thought you wanted colors changed back, too? Outer glow is "shadow" copy whole block from one config to another, idk anymore which one is which :P ...

Use minimapLabels.xc and colors.xc from Jimbo's. If colors won't change, add {{c:system}} macro to the former instead of color definitions. It should work, i don't have time for tinkering and checking myself.

I think that for what you want, you have to rewrite your panels to "none". Maybe you could move clanicons by disabling them and adding manually in extraFields in your current panel, but that's all. Oh, and in "none" you lose spotting markers, for now.

Use {{c:system}} macro, works great for what you want (i use it too).

Yep, get yourself a transparent config to start with (like mine :P ) and one you learn what is where and for what, it will become very easy.

You lack a font for makers, gooroo. Just check which is used and install it.

I'd like to have similar functionality too. Best would be to stack icons one on another with an offset, in case of multiple (like clan/friend/bot/etc).

I already proposed sth. similar earlier, i.e. {{c:spotted}} and {{a:spotted}} macros - since you can use {{vtype}} and color class symbols from XVM.tff font. SPG class separation is now obsolete and they are no longer such threat. General {{spotted}} macro should be defined similarly to {{vtype}}, you could use pngs then. And all macros should take your team into account, like allySpottedMarker used to ;) .

I think more important is auto-loading separate config for replays - for guys who record on youtube and such... I proposed this earlier.

What about the idea of getting clan icons from game server every battle? They are on tanks anyway. They are probably stored in some temp on disk? If you can't get them easily, maybe ask WG since you are friends now.

Not exactly xvm related, but interesting read nevertheless: https://homepages.thm.de/~hg14866/forums/articles/6

OK, thanks. I'll have to edit some fonts myself :P ...