Void Elf Mount Visual Bug

Please see the image below. Something happened in 10.1 and now my Void Elf is afraid to rest his legs on any non-Dragonriding mount (and even then, his legs are just as far out, but it happens to “fit” those mount models)! :upside_down_face:

Crazy Legs

UPDATE: Upon relogging in, using my Felsteed and other smaller mounts like the Dark Iron Core Hound resulted in the correct leg/body graphics being used. Only AFTER using a Dragonriding mount did using other mounts look… gymnast-like! :stuck_out_tongue: What a silly bug!

3 Likes

Huh, I noticed that too on this too. I just thought she was spreading her legs like that since she’s on MG haha

I haven’t hopped onto my other characters and since I don’t have a belf, not sure if it’s all thalassian models or just velves.

1 Like

LOL that is the silliest looking thing I’ve ever seen.

2 Likes

13 Likes

Good god what is happening to this game.

2 Likes

I know, right? Like, this should be a very simple fix: while it does look good on some larger mounts, it should NOT apply to smaller ones. Ironically, this would look fine on the Uncorrupted Voidwing… if I wasn’t so high up on the saddle.

2 Likes

Budget cuts.

lol right? Ya idk what on earth is going on that’s crazy looking.

2 Likes

I feel like unhappy employees are letting all these random bugs go through out of spite.

1 Like

The new client update fixed the bug.

1 Like

Id be down for this

10.1.0.49426 to be specific.

1 Like

It’s not just void elves. Blood elves are also experiencing this bug.

1 Like

We never, ever skipped leg day.

I have this client version, just logged in and was able to recreate the issue. Note that I updated my original post and upon logging in, mounting graphics are normal UNTIL a Dragonriding mount is used. It has something to do with initiating those mounts that cause future mounting graphics to be bugged. This is true even if you cancel summoning a Dragonriding mount before it completes (i.e. just engaging any of those four, soon to be five, mounts causes a problem in the game code).

This seems to be fixed, fyi! :slight_smile: