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

[Repro needed] Visual fx for Ignite longer than weapon, lasting after combat exit

Discussion in 'Combat, Skills, & Magic' started by redfish, Apr 24, 2018.

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

    redfish Avatar

    Messages:
    11,366
    Likes Received:
    27,674
    Trophy Points:
    165
    Reproduction rate: u/k
    Blocker? no

    Details:
    Sometimes, the visual fx for Ignite Weapon will appear longer than the weapon, and then will remain attached to the model's hand even after the weapon is sheathed and combat is exited.

    See screenshots,
    [​IMG]
    [​IMG]
    [​IMG]

    Other times, this hasn't happened. I'm unsure of what the conditions might be to cause this.
     
  2. redfish

    redfish Avatar

    Messages:
    11,366
    Likes Received:
    27,674
    Trophy Points:
    165
    Some related issues,

    For some reason, Ignite Weapon would produce the light radius and some small fire effects without the full fire graphics around the sword,
    [​IMG]

    This would remain even if I entered and exited combat and dismissed and re-ignited my weapon.

    I then un-eqipped and re-equipped my weapon, and that fixed it; save that the first time I did it, there was a needle of fire pointing out from the pommel of my sword,
    [​IMG]

    Exiting and re-entering combat, the needle disappeared,
    [​IMG]

    The needle as described comes back every time I use Ignite Weapon and stays as long as I remain in the combat session.
     
    discipleofweb likes this.
  3. Lexie

    Lexie Bear Queen Emeritus

    Messages:
    842
    Likes Received:
    2,902
    Trophy Points:
    93
    @redfish
    How frequently are you seeing this? I could not repro on build 673. What sword are you using?
     
  4. redfish

    redfish Avatar

    Messages:
    11,366
    Likes Received:
    27,674
    Trophy Points:
    165
    It came up pretty often, but not always. I was using a plain Longsword.

    I'll log in again later today and see if I can notice anything that might bring up the bug.
     
Thread Status:
Not open for further replies.