|
Forum > Tools
[TOOL] Convert WoD adts to Legion (010Editor script)
<< < (3/3)
Arektor:
Dunno about the dbcs, the _lgt changed in Legion but it's related to light.
About the .tex, I just said that the _tex1 got removed (not all _tex). It most likely was just a full copy of _tex0, and if anything was supposed to be different in tex1, it doesn't seems like theres anywhere this different data got moved to.
barncastle:
From memory, all maps in Legion have the 0x40 MPHD flag set, so in your case it should be 0x42.
Unrelated to your issue, but FYI, I found any custom or edited maps will need the 0x100 flag removed unless you've created a valid _lod.adt. This is something to do with continents and how their lod is applied.
On topic: Nice work, good to see something Legion related! One thing I noticed; each MLDD entry should have a flag of 0x20 if you are to 0 fill MLDL.
Arektor:
--- Quote from: barncastle on December 29, 2017, 02:45:50 pm ---One thing I noticed; each MLDD entry should have a flag of 0x20 if you are to 0 fill MLDL.
--- End quote ---
According to the wiki, for each mldl entry, "if the corresponding MLDD has a flag of 0x8 this has a value otherwise 0". And as we don't know what kind of value we're supposed to set in case of a 0x8 flag, that's why I 0 filled it.
Most of the mldd entries I have on my converted adts (if not all) don't have this 0x20 flag, and it still works well. According to the wiki (again), this flag is related to liquid.
barncastle:
--- Quote from: Arektor on December 29, 2017, 03:12:36 pm ---According to the wiki, for each mldl entry, "if the corresponding MLDD has a flag of 0x8 this has a value otherwise 0". And as we don't know what kind of value we're supposed to set in case of a 0x8 flag, that's why I 0 filled it.
Most of the mldd entries I have on my converted adts (if not all) don't have this 0x20 flag, and it still works well. According to the wiki (again), this flag is related to liquid.
--- End quote ---
You're right, sorry, I meant to 0x8. The point still stands, you're not explicitly setting 0x8 on the MLDD flags - I only mention it as I had issues with this on certain MoP ADTs. (I was the one that wrote that on the wiki btw :) )
Arektor:
--- Quote from: barncastle on December 29, 2017, 03:28:52 pm ---You're right, sorry, I meant to 0x8. The point still stands, you're not explicitly setting 0x8 on the MLDD flags
--- End quote ---
Wait, I'm starting to get lost right there. So when the MLDL value is 0, the MLDD should have the 0x8 flag? Cause what you wrote on the wiki says the exact opposite
Navigation
[0] Message Index
[*] Previous page
|