How to get a valid Z coordinate

[schlumpf]

No changes in WotLK on these things, Apoc.

[Apoc]

No changes in WotLK on these things, Apoc.

Ah thank god. Should be simple to parse the new terrain data then. Thanks schlumpf

[schlumpf]

Only if you want to include M2s and their bounding boxes, you will have to correct some offsets (just in the header, the rest is like it was again). WMOs and ADTs are held compatible since Vanilla beta iirc. alpha was different.

[rspaeth]

FYI, tons of things in ADT's (and a few things in WMO's) have changed since beta, and most notably since the WOTLK expansion. Notable changes: MH2O chunk addition (with a few maps still retaining the MCLQ chunks), MCSE and a few other "per chunk" blocks have been repositioned and offsets will now be out of order, and some sizes are no longer fixed. ADT parsers will not work "out-of-the-box" from TBC to WOTLK, but only minor changes need to be made. I believe the ADT and WMO wowdev wiki's have most of the current information as it stands. Or at least what you'd need for retrieving the heightmap for your Z coordinate.

Also, with a very minimal amount of work, you can tweak the Storm.lib imports to allow for reading the bytes right from the MPQ, without extraction. Once the file handle is open, jumping to the exact chunk and vertices is trivial and can happen VERY quickly, so no lag needed!

Hope this helps, and by the way, I should have my extremely robust wow file toolset available within the month.

[Apoc]

FYI, tons of things in ADT's (and a few things in WMO's) have changed since beta, and most notably since the WOTLK expansion. Notable changes: MH2O chunk addition (with a few maps still retaining the MCLQ chunks), MCSE and a few other "per chunk" blocks have been repositioned and offsets will now be out of order, and some sizes are no longer fixed. ADT parsers will not work "out-of-the-box" from TBC to WOTLK, but only minor changes need to be made. I believe the ADT and WMO wowdev wiki's have most of the current information as it stands. Or at least what you'd need for retrieving the heightmap for your Z coordinate.

Also, with a very minimal amount of work, you can tweak the Storm.lib imports to allow for reading the bytes right from the MPQ, without extraction. Once the file handle is open, jumping to the exact chunk and vertices is trivial and can happen VERY quickly, so no lag needed!

Hope this helps, and by the way, I should have my extremely robust wow file toolset available within the month.

The Storm.dll has been able to open a file from the MPQ without extraction for 3-4 years or so. People currently making any real use of it? 3-4.

All the changes in WotLK are already documented, and those that actually use those files are already updated. (Myself included)