• 🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
  • It's time for the first HD Modeling Contest of 2024. Join the theme discussion for Hive's HD Modeling Contest #6! Click here to post your idea!

Beware Of Corrupted Model Files!

Status
Not open for further replies.
Level 32
Joined
Oct 23, 2006
Messages
5,291


warningsign.gif


During the model creation and development process certain model files may become corrupt.

These rare types of models:
  • Do not display or function properly in Warcraft III itself;
  • can inflict temporary changes upon the World Editor shell;
  • may completely destroy maps into which they are imported!
BEWARE!

Model files become corrupted for these reasons:
Rao Dao Zao said:
  1. GeosetAnims that do not point to a geoset (ie no 'GeosetId' line).
  2. Dodgy extents -- negative maxes and positive mins (beware when editing the Marine and Tauren).
  3. Team-colored particles (when not modified from an existing emitter).
  4. Animations which last 0 seconds.
  5. Lights when attached to root bone (only sometimes).
  6. Certain texture animations (if not done properly).
  7. Polycount (if higher than 100000).
  8. Faulty Ribbon Emitters.
All Warcraft III mapmakers are strongly encouraged to:

  1. Download only reliable, fully tested models from sites like The Hive Workshop.
  2. Carefully test each downloaded model before using it.
  3. Backup important maps (save using a different filename) BEFORE importing any new .mdx file.
Maps damaged by corrupted models may be repaired using this procedure:

  1. Obtain and install MPQ editing software.
  2. Open the MPQ editor and select: Open File.
  3. Set the file type selector to All File Types.
  4. Browse to the folder that contains the damaged map and open it. Remember to open the correct .w3m or .w3x map, NOT a .mpq file.
  5. View the map's list file which displays all imported resources.
  6. Note: Occasionally, especially during protection / optimization, files are renamed so they are not recognizable. In this case, you should make quite a few backups, and perform trial & error tests until you get the right one.
  7. Delete each and every .mdx file (and any associated .blp texture files) which are suspected of being corrupt.
  8. Exit the MPQ editing software; no need to save the map: once the unstable files have been deleted, the map's MPQ archive will be restored.
  9. Test the map in Blizzard's World Editor and in Warcraft III.
 
Last edited by a moderator:
Status
Not open for further replies.
Top