Nanawatai

Just upgraded to version 6.5.7 and I can confirm that these are working fine alongside this morning's mini-patch update: mouse-over works fine on Service Record screens switching/selecting equipment in garage is working no delay in loading Tech Tree

Ah, great news. Thank you, gentlemen.

Is it just me, or is there an issue with the armor values in tooltips.xc? (specifically, turretArmor and hullArmor) I am using a default copy of this file in my XVM config, copied straight from \World_of_Tanks\res_mods\configs\xvm\default\, and all I see is skipped space where the information should be present: Something I'm doing wrong, or is this a known issue? Thanks/Спасибо!

Thanks for your response, @scyorkie. I ended up disabling def.hitlogBody and modifying def.hitlogHeader like so: "hitlogHeader": { "enabled": true, "updateEvent": "ON_DAMAGE_CAUSED, ON_PANEL_MODE_CHANGED", "x": 242, "y": -30, "width": 420, "height": 160, "screenVAlign": "bottom", "textFormat": { "color": "0xF4EFE8", "size": 15 }, "format": "{{hitlog-header}}\n{{hitlog-body}}" // Format of the full hitlog (header and body) // "format": "{{hitlog-header}}\n{{hitlog-body}}" }, You were right - adding "screenVAlign" made all the difference. The only thing I couldn't figure out was the Y coordinate -- it took several tries before I landed it where I needed the hitlog to sit on the screen. I have no idea what the negative 30 pixels is in relation to. Thanks again.

I am attempting to move my hitlog to the bottom left-hand corner, in the space where the current damage log resides (which is disabled now and will be moved elsewhere). In the past, I populated the "y" coordinate with a negative value so that it would hug the bottom of the screen regardless of screen resolution. Here was the code that I used: // X position (negative values - bind to right side of screen). "x": 250, // Y position (negative values - bind to bottom side of screen). "y": -100, // Width. "w": 400, // Height. "h": 100, // Number of lines with hits. Old lines will be pushed out. "lines": 4, // Log direction: up - lines will be added from up to down, down - from down to up. "direction": "down", However, that no longer seems to work. I've modified the two hitlog entries in battleLabelsTemplates.xc, like so: "hitlogHeader": { "enabled": true, "updateEvent": "ON_DAMAGE_CAUSED, ON_PANEL_MODE_CHANGED", "x": 250, "y": -228, "width": 400, "height": 20, "textFormat": { "color": "0xF4EFE8", "size": 15 }, "format": "{{hitlog-header}}" // Format of the full hitlog (header and body) // "format": "{{hitlog-header}}\n{{hitlog-body}}" }, "hitlogBody": { "enabled": true, "hotKeyCode": 56, "onHold": "true", "visibleOnHotKey": false, "updateEvent": "ON_DAMAGE_CAUSED, ON_PANEL_MODE_CHANGED", "x": 250, "y": -218, "width": 400, "height": 180, "textFormat": { "color": "0xF4EFE8", "size": 15 }, "format": "{{hitlog-body}}" }, ... but when I use a negative integer in the "y" variable, the hitlog disappears from view. I noticed that def.damageLog uses Python macros for its X,Y assignments, but I don't think it will be suitable for my purpose. What do I need to do in order to place the hitlog in the bottom left corner, next to the damage status, and have it work for different users and their different screen resolutions? Is there a Python macro that will give me screen resolution width and height, allowing me to apply py:math.sub(a, b)? Спасибо, and thanks in advance.

Ah, that's the one. Thank you, sir! Спасибо!

At the log in screen, there's a display of version information in the upper left-hand: The text reads: World of Tanks v.0.9.17.1 #363 | XVM 6.5.5 (WoT 0.9.17.1) Now, what are the chances of me being able to append a string to the end of this line as a means of identifying or "branding" my mod's configuration? For example, so that it would now read: World of Tanks v.0.9.17.1 #363 | XVM 6.5.5 (WoT 0.9.17.1) | GenericXVM Mod v.1.0 (by Nanawatai) ... indicating to users the configuration version that they are using. (I can see how popular modders like Aslain, J1mB0, Solo, etc., would find this useful.) Anyway, thought I would ask -- or suggest. :-)

Ah, thank you gentlemen! Worked like a charm. I was able to consolidate all of my marker def.* values into marker.xc which cleaned things up immensely (using scyorkie's suggestion so that I could put everything in its own "def" section). Now, when I change a variable, I only need to change it in one place and the value is shared throughout all four files. For future reference, don't forget to modify your textField lists by doing the same: // Block of text fields (extended format supported, see extra-field.txt). "textFields": [ ${ "markers.xc":"def.iconEnemyTankWR" }, ${ "markers.xc":"def.tankName" }, ${ "markers.xc":"def.tankPtsInteger" }, ${ "markers.xc":"def.topTankers" }, ${ "markers.xc":"def.position" } ]

I have attributes in all four markers files (AliveExtended, AliveNormal, DeadExtended, DeadNormal) that are the same. Is it possible to consolidate them somewhere, say like in markers.xc, where they can be in only one spot and easily read by all markers files? For example, I have the value "def.healthBar" defined in all four files and they share the same values. If I make a change to the healthBar in one file, I have to remember to make the same edit in the other three. I'd like the values for "healthBar" to exist in one location and in one entry. What is the easiest way of accomplishing this, or is there something that I can put at the beginning of markers.xc? Thank you in advance.

That makes sense. And, of course, I haven't gotten around to editing the markersDead*.xc files yet. Thanks, konrad509.

I have a possible bug that I wanted to mention, or maybe I'm editing the wrong entry in my custom XVM config? The problem is here in markersAliveNormal.xc: // Floating damage values. "damageText": { // false - disable / не отображать. "enabled": true, // Axis field coordinates "x": 0, "y": -67, // Opacity (dynamic transparency allowed, see macros.txt). "alpha": 100, "align": "center", // Font options. "textFormat": { "font": "Impact", // Font name "size": 18, // Font size // Color (dynamic colors allowed, see macros.txt). "color": null, "bold": false, // True - bold "italic": false // True - italic }, // Shadow options. "shadow": { // false - no shadow "enabled": true, "distance": 0, // (in pixels) / offset distance "angle": 45, // (0.0 .. 360.0) / offset angle "color": "0x000000", // "0xXXXXXX" / color "alpha": 100, // (0 .. 100) / opacity "blur": 3, // (0.0 .. 255.0) / blur "strength": 1 // (0.0 .. 255.0) / intensity }, // Rising speed of displayed damage (float up speed). "speed": 3, // Maximum distance of target for which damage rises. "maxRange": 50, // Text for normal damage (see description of macros in the macros.txt). "damageMessage": "{{dmg}}", // Text for ammo rack explosion (see description of macros in the macros.txt). "blowupMessage": "{{l10n:blownUp}}\n{{dmg}}" }, I have set up the font face as Impact, and for the most part, it works. When you deal damage to the enemy, you'll see the damage points float up correctly in the Impact font. However, when it comes to the killshot, the last number that is displayed when the enemy dies switches to $FieldFont. Likewise, the "Blown up!" message is displayed in $FieldFont as well (not Impact). Do I need to edit the font face elsewhere? I would assume the "font": "Impact" attribute in textFormat would be enough. I tried putting <font face='Impact'></font> in the "blowupMessage" field but there was no effect. Thanks in advance.

Would it be possible to add a personal macro for the player that displays current number of shots fired? I would like to add this value to my config's Hit Log so that I can display the statistic showing the number of shots attempted versus shots that hit. And if possible, adding another macro showing the calculated hit ratio (shot attempts divided by shot hits) would be appreciated. Thank you, keep up the great work! ~ Nanawatai

I was hoping to expand my config's hit log statistics and display number of shots fired compared to shots that hit. Does a macro exist that would display the number of times you've pulled the trigger, and if there isn't, how would I go about requesting such a attribute be created? Thanks, Nanawatai

Surely OP must be joking. Some days I spend more time working on my clan's XVM config than playing the actual game... and I enjoy it! All the changes are documented in the changelog, readily available. It also helps to run a diff utility, comparing your XVM config to that of the default (which is kept updated throughout XVM releases).

You could just edit minimap.xc and adjust the "iconScale" value to your liking. That might fix your issue, especially if you're running an older config that has a iconScale of less than 1. For the record, I used to run .8 on my XVM, but ended up changing it to 1 for XVM 5.4.1.1.