[Question] Adding texture to WoD items - WMV

[Azantrox]

Good evening,

To keep a long story short, I would love some guidance on how to add texture to a model in WMV. Atm I want to create an orc warlock with the Tier 17 set. I managed to find the items needed for it and imported them into WMV.
If anyone could point me in the right direction, would be very much appreciated!

Thanks in advance,

Azantrox

PS: My apologies if there would be a guide or so up explaining how to do this. I tried to search for it both on this forum as on google, but without any luck so far.

[[Soul Eater]]

Since it's WoD I wonder if there is already a model viewer that is capable of reading those models. As far as I know, back then you need a WMV that was able to read the model info or else it wouldn't display it at all. As far as assigning texture to models, I don't really understand that question. Aren't the textures already pre-loaded when you open the MPQ file? If you want to "add" textures onto a model, it needs to be done on the MPQ side since WMV only loads the MPQ + the models that it contains. Could be wrong on this one but that's for me the logical step, since WMV is just a viewer.

[Trixiap]

It is pretty hard to add them. WMV reads some dbc. files that contain info about items, but WoD changed them, so you must convert them back to MoP. There is no app for it so if you are not programmer or you don´t have someone that can help you with it, it is almost impossible for you to do it. I am making app that can do it, but I don´t have time right now so I am not sure when I will be able release it.

Anyway, items texture and models are in ItemDisplayInfo.dbc. In WoD Blizz changed that table, so now it only contains reference to FileData.dbc (models) and TextureFileData.db2 (textures). You must replace this reference with real path to model/texture (look how MoP dbc looks like for reference). Also you must remove some new columns (I don´t have number).

But this was the easier part. Real problem is with Item.db2 that is database that hold info about Item ID and Item Display ID. In WoD Blizz did change, so now every ItemID can have multiple DisplayID (in MoP it was 1 ItemID=1 DisplayID). New Item.db2 only holds info about ItemID and Icon. Items ID and Display ID can be "linked" via ItemAppearance.db2 where you will find Icon and DispalyID. It means that you must build your own Item.db2 (MoP style) and iimport it in WMV.


Ps. Machinima Studio is able to "manualy" put texture on Item, but since it is dead project you will not able to put these (I think it support items until late MoP) items on model, because devs must release some infofile with IDs.

[Azantrox]

Thanks both!

@Soul Eater: I was able to use the latest build of WMV to import the new models. For example I can see the Tier 17 warlock item models, but without any texture. Just added them into an MPQ as allnei instructed me in another post. Just had to fool around with the paths a bit. So should be possible afaik.

@allnei: well there go my days off No harm in trying, doubt I'll succeed though. Cheers again for the info!

[k1ngk1ll]

But this was the easier part. Real problem is with Item.db2 that is database that hold info about Item ID and Item Display ID. In WoD Blizz did change, so now every ItemID can have multiple DisplayID (in MoP it was 1 ItemID=1 DisplayID). New Item.db2 only holds info about ItemID and Icon. Items ID and Display ID can be "linked" via ItemAppearance.db2 where you will find Icon and DispalyID. It means that you must build your own Item.db2 (MoP style) and iimport it in WMV.
.

It's more ****ed up then you can imagine. Blizz does more database normalization since MoP.

For the item icons you have to go the following way - structure first.

ItemModifiedAppearance.db2
ID (Int)
ItemID (int)
dummy (int)
ItemAppearanceID (int)
dummy (int)
dummy (int)

ItemAppearance.db2
ID (int)
AppearanceType (int)
FileDataID (int)

FileData.dbc
ID (int)
FileName (string)
FileCategory (int)

ItemID -> ItemModifiedAppearance.ItemAppearance -> ItemAppearance.FileDataID -> FileData.FileName