Jump to content

Spiegator

Regular Member
  • Posts

    14
  • Joined

  • Last visited

Posts posted by Spiegator

  1. 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?

  2. 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.

    shot_039.jpg

    shot_040.jpg

  3. 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

  4. 10 minutes ago, 6bits said:

    This problem keeps reoccurring for me too! I have removed mods and it seems to be fixed and working fine for awhile but  then its back again. Escape and control quit working seems to always happen when I exit game for awhile and then re-enter without shutting down computer first.

    That patch file you offered several answers ago doesn't not work! Windows says I can not access required file type???

     

    WargamingGameUpdater.log

    WargamingGameUpdater.log.bak

    PhysXLoader.dll

    _Aslain_logs.zip

    python.log

    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!!!!

  5. 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

  6. Just now, Aslain said:

     

    Use this modpack rc: it has updated sights script

    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?

  7. On 22/8/2016 at 9:03 AM, Aslain said:

     

    Currently these crosshairs are using mod_sight.pyc:

    - standard and more...

    - taipan 2

    - overcross

    - minimalistic sights shtys

    - sword of damocles

     

    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...

  8. 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

    • Upvote 1
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.