Horned Dragon sword outfit style - skill\effect vfx not aligned properly

colossalvoids

A followup to my previous post about misaligned vfx on Stonekeeper Arms Pack's shield outfit style.

Since Summerset (?) when this style was released as a reward for Battlegrounds it was not displaying applied VFX right, some examples as shown there:

Horned dragon outfit style applied and Nightblade's skill Grim Focus\Merciless Resolve applied as a VFX on top shows precisely what i mean:


Meanwhile, for example, Doctrine Ordinator outfir style swords are showing same VFX properly:


It also affects enchantments, same testing goest there with first screenshot being Horned Dragon sword style in one hand + Maelstrom Arena one in the other and second being Doctrine Ordinator style ones:



@ZOS_GinaBruno
@ZOS_JessicaFolsom

Fennwitty

Wow what? I wonder how that can even happen.

wrote

jesus lmao how the hell did they mess that up its literally horizontal instead of vertical

colossalvoids

wrote wrote: »

jesus lmao how the hell did they mess that up its literally horizontal instead of vertical

Was the same issue with horned dragon staff, they placed effect box horizontally on a pummel I believe, fixed like a year after release but swords stayed the same. Top-notch testing here.

colossalvoids

@ZOS_GinaBruno would appreciate any word about it, years passed already:)

colossalvoids

@ZOS_Kevin hey, saw you being active recently so tagging for a chance those visual issues might get noticed and resolved someday, there was a lot time since Summerset released:)

Also a link to similar issue but with crown store arms pack: https://forums.elderscrollsonline.com/en/discussion/572931/stonekeeper-arms-pack-shield-skills-vfx-not-aligned-properly

Thanks in advance!

ZOS_Kevin

Hi @colossalvoids. Thank for the follow up here. We have confirmed with the Dev team this issue will be fixed in Update 31. If you still have any issues with this after Update 31 is out, please let us know.

colossalvoids

ZOS_Kevin wrote: »

Hi @colossalvoids. Thank for the follow up here. We have confirmed with the Dev team this issue will be fixed in Update 31. If you still have any issues with this after Update 31 is out, please let us know.

Thank you for passing this to the team and additional information, your work is much appreciated