On PS5, the premium mount armor Hellbound, when using the boost, displays the incorrect graphic effects.
It is displaying the effect from the ‘Invincible’ mount instead, which blue and a dragon. The Hellbound mount armor is a hellish theme with cinders, flames and is dark with red and orange effects.
This happens with any mount used with this armor.
This needs to be fixed to its proper and intended graphics effect.
As a premium cosmetic, this incorrect effect destroys the fantasy of the product purchased and takes away from the intended expectation for the buyer.
sadly the blizzard team assigned to diablo 4 do absolutely 0 support for store, and this situation still persists even tho people bought the armor before they added this blue dragon head, which, for me and for many others, makes it useless and ugly and its NOT what i paid for.
i stopped buiying cosmetics after this, and id advise everyone to do the same till they start taking notice of this small things.
I am playing on Xbox Series X and I purchased the “Hellbound” mount armor & trophies bundle this morning for 1700 Platinum, and as of today May 12th, 2024, this bug still persists. As a premium cosmetic purchase from the shop, this needs to be fixed as the fantasy of a fiery hell bound mount is not achieved with the current blue animation. Please address this Blizzard. Thank you kindly. 
I purchased the “Hellbound” mount armor & trophies bundle for 1700p on 5/26/2024 (today) and would take a refund if that were possible. This blue dragon on a fiery hell mount is extremely disappointing. Simply removing the blue dragon animation or replacing it with a similar fire animation would be better than nothing. This happens regardless of what mount I have selected. I doubt I will use the mount armor and due to this will rethink my shop spending in the future unless resolved. Between issues like this and the memory leaks that still exist as of 5/26/2024 I haven’t been able to get the enjoyment I expect out of Diablo 4 hardcore.
still no fix, they just ignore the buyers
This issue is now fixed for me!