[TUTORIAL] Custom WMO's Survival Kit

[abdalrahman9]

Hello there Met@, thanks for the amazing tutorial as i was looking on how to insert doodads in my own wmo's. I am truly thankful. However, i have stumbled upon some kind of a bug among some of my wmo's. The bug is weird and i have attempted to fix it many times but to no prevail. The problem is that when i spawn a wmo in a land and go to that place ig, some parts or sometimes all of the model are totally transparent. However, this isn't the most weird part. When i re-spawn to that same spot without closing the wow client, it appears normally. Here is an example(Just a heads up, this doesn't happen to all of my wmo's):

When i first log in to at the wmo it is like this:  


Than when i re-spawn or use the reload command it becomes normal:


Please, if you have any idea on how to fix this, i will greatly appreciate it. Otherwise, i am still thankful for your effort in creating this tutorial!

[Met@]

Hmmm... I don't really know the cause of the bug, I haven't had this kind of problem. Maybe from the indoor/outdoor flag? But I assume it's not because of that. Or maybe, if it's a big model, it needs to load several adts to wrok fine. Sorry, I can't help you more with this.

However, I'm glad this tutorial was helpful for you.

[phantomx]

Have you tried removing the ground below the wmo?

That's what blizzard does and what I do.

[abdalrahman9]

What do you mean by 'ground'? Are you referring to the adt ground or the ground of the wmo which is what the character is standing on in the picture?

[phantomx]

What do you mean by 'ground'? Are you referring to the adt ground or the ground of the wmo which is what the character is standing on in the picture?

The ADT ground, blizzard always removes the ground underneath a WMO and so should you.

[abdalrahman9]

It would seem the problem persists...

[schlumpf]

Blizzard does not remove ground below WMOs unless there is a part being underground, e.g. a cellar in the inns.

[abdalrahman9]

Ya, i never saw it remove the ground before. I was wondering about that. However, even if that was true, how does that relate that if you reload it works?

[Laduguer]

Thanks so much for this tutorial, looking forward to the installment on lighting.

[TheBuG]

Awesome tutorial, I might be tempted to start working on something again sometime soon .

Wow, this is a fantastic guide. I'm tempted to try porting in some of my models.

I'd love to see your Lordaeron ingame .

[Ohai]

Hey nice tutorial, everything works for me except my UVs are completely off does mirrormachine flip them? like a mirror lol? because it does almost that, like the spot where my texture should start from the bottom it shows it starting from the top, and vice versa?
And also double sided ✓ checked normals on object data panel doesnt show the texture on both sides of a face, whats the solution for that anyone know?

EDIT: also i kept my textures tga from blender to wow if that matters anyway, and I changed the file paths for textures in the MTL file from D:3.3.5_modsworldimg/image.tga to just worldimg/image.tga ..? I did that so that wow reads it like that in the patch? if that makes any sense, and also so I dont have to change it in 010, cba editing text there so I thought changing it before might be better.. but anyway it does read the path the only problem is the textures get inverted somewhere in the process

meh, I just inverted those 2 textures y axis and i guess its fine now :b come to think i almost wrote alice behind the mirror sequel here..  :roll:

[abdalrahman9]

Hello there, something weird has just happened to me. So i was working on a new model that has 68 subparts to the wmo and when i was trying to load it to wmo editor, it loaded and i could see it but the file didn't load in root file section and the doodad section of wmo editor. Does anyone have a clue why this would occur? It happened right away after i had inserted the MDOM chunk beside the NDOM chunk.

EDIT: it would seem i found the problem. It was that i accidentally put one of the MDOM chunks beside a wrong NDOM as there were multiple ones in one file so i was a little confused. But all fixed now!

EDIT 2: I am not sure if this happens to others but why is it that after i insert the MDOM Chunk the model loses its collisions? Before i had inserted it, all the model had collisions but after i inserted MDOM chunk into the model, the whole model didn't have collisions. Does the MDOM Chunk remove the collisions and if so, how can you put collisions back?

[Met@]

@ Ohai : I have the same problem, the program flip the textures like a mirror, I don't know why. I just flip the blp's to fix it.

[Ohai]

Hey I've got 2 questions; Whats the command to make my object show textures on both sides of a face, so it shows it later on the WMO ofc. I think this is invert normals, becuase I've noticed while doing my last WMO I was redoing grizzlemaw that the new faces/vertex Ive added came up inverted ingame later, but only some so I'm not sure what the problem was there exactly

and second does anyone know what to do if i want a certain object/geoset in my wmo not to have collision? Where do I disable that?

[abdalrahman9]

Hey I've got 2 questions; Whats the command to make my object show textures on both sides of a face, so it shows it later on the WMO ofc. I think this is invert normals, becuase I've noticed while doing my last WMO I was redoing grizzlemaw that the new faces/vertex Ive added came up inverted ingame later, but only some so I'm not sure what the problem was there exactly

and second does anyone know what to do if i want a certain object/geoset in my wmo not to have collision? Where do I disable that?

For the second question, this is probably not the best solution but i realized that if you add a MDOM chunk to the geoset of choice and edit that geoset by checking the 'have doodads' in wmo editor. Then making sure you don't place any doodad on that geoset, then it will make the geoset not have collisions. However, this is probably a very long process and  i am pretty sure there is a faster/easier way to remove collisions.