[SOLVED] [WotLk] Custom Tabard Models glitching?

[Recycle]

Hi!

I've been working on a project, and it's time to add modified tabards. However, everytime I modify the tabards they end up looking like this:
http://i.imgur.com/8LBoc90.png

Textures seem to be the issue. It only affects "new" items with new itemdisplayid, I can modify a .blp and name it the same as a existing one but as soon as it's a "new" one problems arise.

For instance, I've edited these blp's in photoshop:
Tabard_A_49ArenaBlue_Chest_TL_F.blp
Tabard_A_49ArenaBlue_Chest_TL_M.blp
Tabard_A_49ArenaBlue_Chest_TU_F.blp
Tabard_A_49ArenaBlue_Chest_TU_M.blp

And if I add them to the correct folders, Relentless Tabard which uses those files works fine. But as soon as I've added them to a new entry of ItemDisplayInfo.dbc that's how they end up looking like. Belly-area is chest textured, and first part of bottom is leggings textured. It also looks wrong if I attach actual .blp files to the new items(as in Screenshot, custom displayID with existing, non-modified .blp files)

What am I doing wrong? What did I forget/miss?

Thank you for taking the moment to check it out, and even better, if you have a solution.

Edit: Solved it. Apparently cloning a line in MyDBCEditor causes it to break, and using CSVEdit to fix it up made it work nice. Odd but.. at least it works!

http://i.imgur.com/FC85Uxb.png

Regardless, thanks to those who checked the thread!

[Amaroth]

I am not sure what happened to you wrong with MyDBCEditor, buuut... Whenever you work on any texture of clothing (texture items), follow 3 simple rules:
1. keep correct size of textures (f. e. 128x64 or 256x128 or 512x256 for upper part of torso)
2. convert your textures as clothing textures (BLiPster is great GUI tool for doing that)
3. always put name of texture into DBC without _u.blp/_f.blp/_m.blp ending. For example when you have textures named like this:
Tabard_A_49ArenaBlue_Chest_TU_F.blp
Tabard_A_49ArenaBlue_Chest_TU_M.blp
write only Tabard_A_49ArenaBlue_Chest_TU to DBC in order to make item work (no matter if you use 1 _u texture or 2 _m and _f textures, always do like I said).

I know you solved this already on your own, but this might be of use for some others. Your "glitch" seems a lot like wrong name (rule #3) for TL texture.

[Recycle]

I am not sure what happened to you wrong with MyDBCEditor, buuut... Whenever you work on any texture of clothing (texture items), follow 3 simple rules:
1. keep correct size of textures (f. e. 128x64 or 256x128 or 512x256 for upper part of torso)
2. convert your textures as clothing textures (BLiPster is great GUI tool for doing that)
3. always put name of texture into DBC without _u.blp/_f.blp/_m.blp ending. For example when you have textures named like this:
Tabard_A_49ArenaBlue_Chest_TU_F.blp
Tabard_A_49ArenaBlue_Chest_TU_M.blp
write only Tabard_A_49ArenaBlue_Chest_TU to DBC in order to make item work (no matter if you use 1 _u texture or 2 _m and _f textures, always do like I said).

I know you solved this already on your own, but this might be of use for some others. Your "glitch" seems a lot like wrong name (rule #3) for TL texture.

Despite fixing it, I'll comment since you were kind enough to reply!

The problem was somehow in the dbc editor, simply because changing the texture name to a existing item it worked flawless, but new displayID didn't work at all. Once I added them through CSVed, to a new entry it worked on a new entry too. I figured _F and _M were Male and Female since all _F ones seemed to have more shadows in the chest area for tabards.

Never heard of BLiPster, I'll take a look into that. Thanks!

[Amaroth]

I know, I read your post, and your issue seems quite unusual. Like I said, I wrote it here only because it might be useful for someone else.

Btw, BLiPster is GUI app using BLPConverter. Its great for mass conversions and more practical than setting everything by hand in command line tool. I also wasn't aware of that tool for a very long time.