Spiegator

Hi, you had the hp macro in your PalyersPanel file. it's still there but it has been deactivated via comment comand. "hp": { "hotKeyCode": 56, "onHold": "true", "visibleOnHotKey": true, "x": 142, "y": 4, "bindToIcon": true, "align": "center", "alpha": "{{alive?100|0}}", "format": "<font face='$FieldFont' size='11' color='#D9D9D9' alpha='{{alive?{{ready?#FF|#80}}|#80}}'><b>{{alive?{{hp|{{l10n:No data}}}}|{{l10n:Destroyed}}}}</b></font>", "shadow": { "enabled": true, "color": "0x000000", "alpha": 100, "blur": 4, "strength": 1, "distance": 0, "angle": 0 } } I'd like to know if it's working or how to activate it. i already tried to comment out the appropriate line in the correct filles (both in palyersPanel.xc then in palyersPanel_large.xc, but the total HP left for the enemy is not shown durign game. Is the problem related to xvm or what?

Done, downloaded the build #5 and get stucked immediately after first battle. The tank shows up, but nothing else and cannot do anything but to close the game. To start it again I've to close the WoT program with the Task Manager. Log Attached as requested. Thanks for your effort and if you need some testing just let me know. Aslains_WoT_Logs.zip

I tried it in #4 and getting same problem. What files do you need to analize the issue?

I know how to move those panels and the hitlog. I use my own setup actually (examples below), i simply always update my personal one. I have my own panels, minimap and hitlog. I take some configfiles and play with them. Hitlog for example is based on Aslain one, Panels are based on OMC and personal taste for data. I just reported it because during tests i used standard setup from patch to save time and since i saw that error i reported it.

Then that script is buggy. Because I confirm I get teh ESC CTRL issue only whe installing crosshairs that are using it...

Ok, tested teh RC 11. With the Taipan 2 crosshair I got the error at 4th and 5th game. Checked again with the J1mb0 test 1 crosshair and in 10 games... nothing about the error. It did not show up. Attached the Aslain's logs. So if the sight file was changed only in the J1mb0 crosshairs then we have the solution to the bug. If also the taipan 2 has it... then "Huston, we have a problem." Aslain 11 with J1mb0 test 1 crosshair.rar

I tested it... error showed up at 4th and 5th game with the Taipan2 by demon2597. Now testing again but with the J1mb0 - test version 1

Try without any crosshair mod please. For me it was 15 games in a row without any problem, once i installed teh crosshair, in 5 games I got the problem. To acces teh file U need to click on the "Additiona information" and the new option to run the file it's going to appear!!!!

So done the testing. First with no crosshair at all. 15 straight games no problem. Changed teh set up installing now the Taipan 2 crosshair.... at my 5th game the bug come up. Now I'm trying teh RC candfidate... using always Taipan 2 crosshair. One question now... which crosshairs do have teh modified sights script? Just to make sure!!! Aslain 10 no crosshair.rar Aslain 10 with crosshair.rar

Hi, some problems with misisng Dead tank icon on enemy side in the right panel and overlapping DAMAGE Log with left panel in the PapaDigi config as for attached pic.

I will once i check for 15 times in a row taht without crossair is working ok and then confirm that J1mb0 crossair is creating the problem and so confirming the pyc file issue. Once i get this i try your RC. BTW I've a couple of issue with the position of some panels in your set up. Where can I post the screenshot and the issue?

Ok, finally i can start working on this, vacation and kids are gone, back to work so the afternoon is finally free . I'll start immediately downloading your latest patch and checking installing without any crossair and my custom XVM file. If I found no issue then i will install only the crossairs and check again. I kow that the issue is actually random, so i will perform at least installations of each type untill I find 15 installations in a row with no issue. Up to now I've noticed that the issue either raises at first start up at first mod installation or after that it's very random and generally not showing up...

Hi Aslain, I think too that the problem is the damn custom sight. Can U tell us which are teh crossair using that file? I can try tomorrow all different ones so to check if the issue is really with that file or not. I can use my kids account so no problem wasting time on it. I think we just need to find out what is the issue. BTW I send U my pyton.log, but cannot send U all the other files since I'm using a mix of OMC + single mods installed by my self. python.log