Ress

Already reported few times, Battle Observer bug, don't use it (until it's fixed). ps screenshot is nice addition, but posting logs is much better.

This is third topic that mentions PogS icons, do people even read other topics before posting? (it's been mention twice already in 2 different topics, same issue). Untill this gets sorted out use variation 4 (Clear Simple), its only one with all icons (unless it's atlas corupted as well).

They are contour icons true. But what Aslain said and what ratten shown with image are individial icons (gui\maps\icons\vehicle\contour) only used inside hangar. In battle single file is used: battleAtlas (gui\flash\atlases) with all contour icons inside. Problem was only 13 PogS icons where added inside battleAtlas and rest where vanilla contour icons (not only individual icons where missing but Atlas was incomplete aswell). EDIT: Aslain was faster to respond, but you get the idea. EDIT2: Modpack 1.5.1.0#2 Altases are still incomplete (until resolved use PogS/Clear Simple)

...all 4 crash sessions end around this point: /------------------------------------------------------------------------------------------\ INFO: [Scaleform] Change Owner on GUI Component: 'FlashGUIComponent' -> 'gui/flash/battle.swf' <-modified by xvm INFO: [gui.app_loader.loader] Space is changed: BattleLoadingSpace() -> BattleSpace() INFO: [Scaleform] Change Owner on GUI Component: 'FlashGUIComponent' -> 'gui/flash/battleCrosshairsApp.swf' <-modified by crosshair_Controls INFO: [Scaleform] Change Owner on GUI Component: 'FlashGUIComponent' -> 'gui/flash/battleCrosshairsApp.swf' <-modified by crosshair_Controls INFO: [Scaleform] Change Owner on GUI Component: 'FlashGUIComponent' -> 'gui/flash/battleVehicleMarkersApp.swf' <-modified by xvm /------------------------------------------------------------------------------------------\ Battle loads and crash?...empty log I doubt it's crosshair related (not many crosshair mods got updated, guess wg didn't change anything essential). Maybe try without crosshair mod or different one? just to be sure?

Did you read changelog... v1.5.1.0 #01 (12-06-2019): - added contour icons: Jackhammer (Patejl352) - updated Arty Log - updated Battle Observer (possible fix battle loading hang with XVM - don't use BO if it's not fixed) Did you try without BO? If it works without it, then don't use it (until its fixed).

Try reinstalling, should be resolved.

Yes, it's inside modpack.

I was about to tell you "try runing as admin", check AV and stuff...but... I checked 1.5.1.0#1 and all 4 PogS icons and got no errors. For some reason only 13 icons got installed and battleAtlas is inclomplete (with #1Color MAX, #2Color DMG, #3Color Simple). only #4Clear Simple installs all icons. Try using PogS/Clear Simple until it's resolved?

Battle Observer Try new v1.5.1.0 #01 modpack, if it doesn't work try without BO.

updated .csv for 1.5.1.0 [#1322] added VK 75.01 K (germany-G141_VK7501K) Drum0 added Senlac (uk-GB101_FV1066_Senlac) Drum0 added T-116 (ussr-R161_T_116) Drum0

Moved game to new hdd... hmm simple move should work without any issue i did it few times (cut-paste). make sure you don't have dupes copies of client (old leftovers) try runing game in safe mode (does vanilla client work?) try deleting entire game cache (inside %appdata%) try running check integrity on you client try re-adding game to firewall exception try running game as admin if located on system drive try reinstalling modpack as admin (does modpack auto-detect new game path)(clear cache, logs..all recommended stuff) if using, check/disable antivirus try getting ccleaner and clear your registry (leftovers from install) ..idk some of ideas

Well you can use regular notepad from windows if u are on windows10 (since it does encode UTF-8 when opened). Still not recommended since it's ugly to navigate/edit with. If you can't see status bar with line/columns you can enable it on notepad under view/status bar I use notepad++ for config editing (it's free open source).

Well then open markersalivenormal.xc go to 31.line at 25.column and see what's there and what is before it at 24.column or above at 30.line (around there is the issue). Try going left with arrows from 31:25 by 1, do you have hidden character there (does your cursor not move/skip left by 1). Hidden character is indicated if you have to tap arrow twice to move cursor once.

What is the error? Here i forcecreated error by removing , behind } just to emulate. It tells where error starts. So before that point it's error. In this case missing comma in 28.row after tankClass definiton end, since there is another definition after it. Did you change anything else, is the error inside this file or other file? What does the error say?

Just copied it to config to recheck and no problem. If you get red text error on startup it usually tells you what's the issue. Usually tells you stuff like illegal character/or expected ; or " in file.xc at row:line (example 23:57) where error starts.So you can navigate. Maybe you forgot bracket, comma or something...

Hex color codes used inside xvm are 6digit (RGB only), you can't use 8 digit hex code (RGBa/RGB alpha). When you use hex inside config you can use as 0x000000 or #000000 (example of black 000000). usually when you colorize something inside xvm you use color='#000000' or "color": "0x000000" Little explaining of macro in my example for HT color='{{vtype-key=HT?#f000ff|{{c:vtype}}}}' by default {{vtype-key}} will print class if used as format LT for LT, MT for MT, and so on... To breakdown macro above {{if {{vtype-key}} is equal HT use #f000ff as color|else use default {{c:vtype}} macro (reads color from color section vtype inside colors.xc)}} I already gave you an example above on how to setup color for each class. Gonna post it again, even more colorful rainbow example: color='{{vtype-key=LT?#color|{{vtype-key=MT?#color|{{vtype-key=HT?#color|{{vtype-key=TD?#color|{{vtype-key=SPG?#color}}}}}}}}}}' in this case you no longer need {{c:vtype}} inside color macro anymore, also you can put # in front of bracket and only 6 digits inside brackets. like this: color='#{{vtype-key=LT?000000|{{vtype-key=MT?000000|{{vtype-key=HT?000000|{{vtype-key=TD?000000|{{vtype-key=SPG?000000}}}}}}}}}}' or this: color='{{vtype-key=LT?#000000|{{vtype-key=MT?#000000|{{vtype-key=HT?#000000|{{vtype-key=TD?#000000|{{vtype-key=SPG?#000000}}}}}}}}}}' both ways should work. *Just don't copy-paste any of it above ↑ inside your config, copy from def example code bellow ↓ (to avoid risk of corrupting your config with hidden characters)* def example: "tankClass": { "enabled": true, "x": 0, "y": "{{vtype-key=HT?-5|-10}}", "alpha": 100, "align": "center", "shadow": { "enabled": true, "distance": 0, "angle": 90, "color": "#000000", "alpha": 90, "blur": 3, "strength": 2 }, "format": "<font face='xvm' size='{{vtype-key=HT?24|28}}' alpha='90' color='#{{vtype-key=LT?000000|{{vtype-key=MT?000000|{{vtype-key=HT?000000|{{vtype-key=TD?000000|{{vtype-key=SPG?000000}}}}}}}}}}'>{{vtype-key=LT?&#x3A;|{{vtype-key=MT?&#x3B;|{{vtype-key=HT?&#x3F;|{{vtype-key=TD?&#x2E;|{{vtype-key=SPG?&#x2D;}}}}}}}}}}</font>" }, ...this is all black (000000) example, you need to replace with your colors for: LT, MT, HT, TD, SPG. This entire post is colorful mess, hope you manage to navigate. EDIT: I was about to post this when you post your last reply. Yes you did wrong {{c:vtype}} at end and not enough closing brackets }}, each bracket have to be closed. You have total 10 open and only 4 closing brackets inside color=' '

0xDD4444=#DD4444 If you already found your red DD4444 for HT, why do you need to mess with colors.xc and change red for entire xvm config? I highly advice againts changing colors for vtype inside colors.xc, becase you are effectively changing colors for entire {c:vtype} macro and everywhere that macro is used inside config. That's why i gave you an option to change/bypass it individually on markers and avoid colors.xc If its D4444 then just put inside markers {{vtype-key=HT?#DD4444|{{c:vtype}}}} and if transparency is the issue set alpha to 100. At least make backup of colors.xc if you are messing with it.

Now that i seen your OTM, i am curious... Since you are using contour icons on OTM (with class icon and coloring). Why do you need double class icons? Why not just disable class icon on OTM and call it a day?

1. You didn't break entire config, that's good. (when you do default xvm config is loaded). 2. Coloring still apears to work so <font stuff> is ok. 3. Text... again, you said before it worked and you only wanna change colors. My guess you mess something inside format: <...>this part</font> with symbols macro for each class Try my example above, if still doesn't work we can try different aproach with textformat later on, but outcome will be the same. Just make sure its not some typo error on your end.

If you get no colors you probably mess something up with macro for color (forgot # or ' ' ) Hmm strange text? Try removing "textFormat" part (since it's obsolete) also make sure you still have face='xvm' and you didn't messup <...>*this part*</font> You said it worked before so whatever changes you did to format is causing weird text. Idk, individal color or shadow works fine. Example #f000ff for ht https://www.color-hex.com/color/f000ff example def: "tankClass": { "enabled": true, "x": 0, "y": "{{vtype-key=HT?-5|-10}}", "alpha": 100, "align": "center", "shadow": { "enabled": true, "distance": 0, "angle": 90, "color": "#000000", "alpha": 90, "blur": 3, "strength": 2 }, "format": "<font face='xvm' size='{{vtype-key=HT?24|28}}' alpha='90' color='{{vtype-key=HT?#f000ff|{{c:vtype}}}}'>{{vtype-key=LT?&#x3A;|{{vtype-key=MT?&#x3B;|{{vtype-key=HT?&#x3F;|{{vtype-key=TD?&#x2E;|{{vtype-key=SPG?&#x2D;}}}}}}}}}}</font>" },

Yes, inside format replace color='{{c:vtype}}' with color='{{vtype-key=HT?#YourRedHexHere|{{c:vtype}}}}' if you only need to change HT color. '{{vtype-key=HT?#8B0000|{{c:vtype}}}}' Pick your red here:https://www.color-hex.com/color/8b0000 ...or if you wanna change all without messing with colors.xc: color='{{vtype-key=LT?#color|{{vtype-key=MT?#color|{{vtype-key=HT?#color|{{vtype-key=TD?#color|{{vtype-key=SPG?#color}}}}}}}}}}' '{{vtype-key=LT?#111111|{{vtype-key=MT?#222222|{{vtype-key=HT?#333333|{{vtype-key=TD?#444444|{{vtype-key=SPG?#555555}}}}}}}}}}' EDIT: Also since HT icon is bigger you can make it smaller then the rest of them size='{{vtype-key=HT?24|28}}' or move it up/down "y": "{{vtype-key=HT?-5|-10}}"

Sorry i was away, just got home. Like i said earlier in theory should work. Therefore i just did quick test. As you can see default class icon off, custom class with coloring on. 1. Disable default class icon for allies and enemy inside: markersAliveNormal markersAliveExtended (alt key) markersDeadNormal markersDeadExtended (alt key) "ally": { "vehicleIcon": { "enabled": false, "enemy": { "vehicleIcon": { "enabled": false, 2. Inside each of those 4 configs (or only one you wanna change) Add new custom definition inside "def": { example tankClass definition i used to test this "tankClass": { "enabled": true, "x": 0, "y": 0, "alpha": 100, "align": "center", "textFormat": { }, "shadow": { "enabled": true, "distance": 0, "angle": 90, "color": "#000000", "alpha": 90, "blur": 3, "strength": 2 }, "format": "<font face='xvm' size='28' alpha='95' color='{{c:vtype}}'>{{vtype-key=LT?&#x3A;|{{vtype-key=MT?&#x3B;|{{vtype-key=HT?&#x3F;|{{vtype-key=TD?&#x2E;|{{vtype-key=SPG?&#x2D;}}}}}}}}}}</font>" }, 3. Link this new definition to "ally" and "enemy" (same section you already disabled default icons in step1) for each marker config you wanna (normal,normalalt,dead,deadalt). under "textFields": [ add ${ "def.tankClass" } Thats all there is to it. EDIT:As for me editing your config files, i don't think that's a good idea. Don't wanna change other peoples core config files (from modpack) and cause breakings. Also colors of classed depends on your settings inside colors.xc for vtype, but that can be bypassed completely inside definition with '{{vtype-key=LT?XXXXXX|}}' as color instead of {{c:vtype}}, same goes for size if you wanna equalize icons (but then that's finesse and stuff).

I just downloaded modpack to check and you are right, no option. Well in theory it should be easy enough to add to xvm as option. If you are familiar with xvm config editing inside markersAliveNormal / markersAliveExtended or dead/whatever. -First by disabling default for ally and enemy "vehicleIcon": { "enabled": false -then by adding new definition example: "ClassIcon": { "enabled": true, "x": 0, "y": 10, "alpha": "100", "align": "center", "textFormat": { }, "shadow": { }, "format": "<font color={{c:vtype}}>{{vtype}}</font>" or specific (can't remember right macro atm) <font color={{vtype=MT?#color1|LT?#color2.....}}><font face=xvm>{{vtype=MT?&#x3b;|LT?3a;.....}}</font> -and finally by linking that definition inside "textFields": [ for Ally and Enemy. ${ "def.ClassIcon" } Keep in mind this is quick draft, but doable in theory. Maybe Aslain could look into it or maybe consider adding "colored class icons on OTM" as option.

1. contour icons is one thing... 2. top score markers is another thing... If i understand correctly, you are talking about actual class icon on otm (bellow hp)? You wan't that blue for td, red for heavies, green lights and so on? (now that's another thing) first 2 are not related to this. Isn't there something like this already inside modpack? xvm section?

v0.8 - Complete