Dismiss Notice
This Section is READ ONLY - All Posts Are Archived

[Repro Needed]Health Bar Bug still exists

Discussion in 'Release 44 Dev+ Bug Forum' started by Jens_T, Jul 20, 2017.

Thread Status:
Not open for further replies.
  1. Jens_T

    Jens_T Avatar

    Messages:
    641
    Likes Received:
    1,483
    Trophy Points:
    93
    Location:
    Zurich
    07/20/2017 19:32
    Title:
    Reproduction Rate:
    Blocker?
    Details: If buffs expire the actual health displayed cannot be healed to the maximum. Actual HP are correct.

    Steps to Reproduce:
    User Specs:
    OS: Mac OS X 10.11.6
    CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (8) System RAM: 16384
    GPU: AMD Radeon R9 M295X OpenGL Engine GPU RAM: 4096
    SotA.EarlyAccess.QA.OSX.64.523.Date.07.20.17
    Area: HiddenVale_Forest02_Tier5
    Area Display Name: Deep Ravenswood
    Loc: (-114.4, 28.6, -117.1)
    Debug: SGlkZGVuVmFsZV9Gb3Jlc3QwMl9UaWVyNXx8KC0xMTQuMzgsIDI4LjY0OCwgLTExNy4wOTQpfCgwLCAwLjU2OCwgMCwgLTAuODIzKXwxMTUuNDk5NHwxMy4yMjE3Nnw4Ljk0MzU0Mg==
     
  2. Attenwood

    Attenwood Portalarian Emeritus Dev Emeritus

    Messages:
    6,910
    Likes Received:
    5,863
    Trophy Points:
    153
    Are you able to reproduce this reliably? It's been around for some time without a repro case being found. : /
     
  3. Jens_T

    Jens_T Avatar

    Messages:
    641
    Likes Received:
    1,483
    Trophy Points:
    93
    Location:
    Zurich
    @Attenwood the best way to reproduce it is to heal to max after buffing (Earth strength & crystal shield) and then dismissing either of the buffs.
     
  4. Attenwood

    Attenwood Portalarian Emeritus Dev Emeritus

    Messages:
    6,910
    Likes Received:
    5,863
    Trophy Points:
    153
    Yes, we've tried this internally, and it hasn't provided the results desired. There's some special sauce to get it to occur which simply buffing, healing, then removing buffs provides.
     
  5. Jens_T

    Jens_T Avatar

    Messages:
    641
    Likes Received:
    1,483
    Trophy Points:
    93
    Location:
    Zurich
    Do the debug logs help in finding the error? It's strange because I can reproduce the effect and don't seem to be the only one?
     
  6. Jens_T

    Jens_T Avatar

    Messages:
    641
    Likes Received:
    1,483
    Trophy Points:
    93
    Location:
    Zurich
    @Attenwood the following spell combination often - but not always - leads to the effect.

    0) Full Health (403/403)
    1) Cast "Strength of Earth" (+13,4 Strength) = 428/428
    2) Cast "Enlightment" (+13,3 Intelligence - 13,3 Health) = x / 415 (Net Health Gain due to Intelligence boost = 12HP 415-403)
    3) Dismiss "Enlightment" (-13,3 Intelligence + 13,3 Health)

    The last step often leads to the actual HP being displayed by 12/13HP lower than the max HP. It's the same difference as after applying the second buff.

    If I dismiss a HP buff while I have an active healing spell, the change in HP is shown as "critical damage" of the spell, even though the drop comes from the dismissed buff (cf my bug report for this)

    IF I combine "Strength of Earth" with "Crystal Shield" and dismiss the "Strength of Earth" the same effect as above can happen, i.e. the 13,x HP gained from Strength of Earth are subtracted from the max and actual HP and cannot be healed.

    When testing this I did not move and I don't think the time changed enough to have an impact on the sun innate giving strength. There's something funky with the way buff expiration affects actual & max HP. Sometimes it looks like the effect is subtracted twice from the actual HP.


    07/21/2017 18:31
    Title:
    Reproduction Rate:
    Blocker?
    Details:
    Steps to Reproduce:
    User Specs:
    OS: Mac OS X 10.11.6
    CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (8) System RAM: 16384
    GPU: AMD Radeon R9 M295X OpenGL Engine GPU RAM: 4096
    SotA.EarlyAccess.QA.OSX.64.523.Date.07.20.17
    Area: Novia_R6_Hills01_SuperstitionCanyon
    Area Display Name: Superstition Canyon
    Loc: (458.8, 12.4, 365.3)
    Debug: Tm92aWFfUjZfSGlsbHMwMV9TdXBlcnN0aXRpb25DYW55b258fCg0NTguODM2LCAxMi4zNTcsIDM2NS4yOTEpfCgwLCAtMC45OTcsIDAsIDAuMDczKXwxODguNjM5OXwxMHwxMy4xOTAwMQ==
     
  7. Attenwood

    Attenwood Portalarian Emeritus Dev Emeritus

    Messages:
    6,910
    Likes Received:
    5,863
    Trophy Points:
    153
    Even following these steps, we are unable to reproduce. :(
     
  8. Jens_T

    Jens_T Avatar

    Messages:
    641
    Likes Received:
    1,483
    Trophy Points:
    93
    Location:
    Zurich
    could it be client based, only Mac clients affected?
    I never had somebody else checking my health bar while I was seeing this bug.
     
  9. jiirc

    jiirc Avatar

    Messages:
    2,853
    Likes Received:
    2,893
    Trophy Points:
    153
    No I have the health issue showing up on my client, which is Windows based.

    However, I not been able to effectively reproduce this myself.

    Thinking about this my first questions would be:

    1) devotional buffs present
    2) stacking versus non-stacking
    3) order that buffs are applied

    But I'm sure some of this have been examined already.
     
  10. Jens_T

    Jens_T Avatar

    Messages:
    641
    Likes Received:
    1,483
    Trophy Points:
    93
    Location:
    Zurich
    For me no devotionals, I don't stack buffs and the order doesn't seem to matter - as long as an effect is removed that increased HP.
    Did you check with a second person if your HP is also affected on their client?
     
  11. jiirc

    jiirc Avatar

    Messages:
    2,853
    Likes Received:
    2,893
    Trophy Points:
    153
    @Lexie, @Attenwood, I ran into this on Live today and had an additional comment to make. This seems to be a real loss of health, I read somewhere about that. I had this occur to me today and quickly grabbed a /stats. I looked for two values, current health and health. Current health was different than health, when they should have been the same. I was just standing around and the health wasn't regenerating.

    I still haven't found a reason for this occurring in the first place though.
     
Thread Status:
Not open for further replies.