Modcraft - The community dedicated to quality WoW modding!
Wrath of the Lich King Modding => "Retro-Porting" => Topic started by: Vortalex on March 23, 2016, 09:07:46 pm
-
So I think it'd be best to just explain the problem with this picture:
(http://i.imgur.com/UtPyo1C.png)
The Kodo Mount scales your character to 2.5 the size of normal when mounted. I've looked around in the model data, I've looked in the dbcs, I'm not sure what controls the character scaling. Anyone know where it's located?
-
Haha it looks so funny, you should keep it that way!
-
Haha it looks so funny, you should keep it that way!
No thanks. I'd like it fixed.
-
thats doing bone in model of kodo that is supposed to handle player
-
thats doing bone in model of kodo that is supposed to handle player
That statement was pretty confusing, could you elaborate a little bit?
-
I had same issue, from which build you got it ? Did you try a newer version ? Cause i think they fix that problem in newer builds and since its alpha state you should expect such things. I had twice to update legion to see if a model was fixed by bliz in the new build.
-
https://wowdev.wiki/M2/WotLK#Bones (https://wowdev.wiki/M2/WotLK#Bones" onclick="window.open(this.href);return false;)
-
I had same issue, from which build you got it ? Did you try a newer version ? Cause i think they fix that problem in newer builds and since its alpha state you should expect such things. I had twice to update legion to see if a model was fixed by bliz in the new build.
I used the most recent build. Guess I'll just wait a while for them to fix it.
-
CreatureDisplayinfo.dbc has its own Internal size.
-
both, creaturedisplayinfo and creaturemodeldata, to be exact.
-
They have their own internal size for the model, not for the unit mounted on the model. Only thing that affects mount variables in those dbc files is the height a player mounts the creature from.
-
Just as an update, this problem I'm having with the kodos is not a problem during conversion. It's the same way on legion alpha right now on live servers. lmao
So I guess it's not an issue on my side alone. Will just have to wait for Blizz to fix em.