it’s been a while since this thing is out but i never managed posting it somewhere else
it kinda goes hand in hand with ydnar’s md3fix.
original post: http://www.reloadnet.com/board/viewtopic.php?t=134
i took the time and coded a tool that makes the modder’s life a tad easier: a gui version of md3check. it is used to error-check md3 model files (validates vertex counts, etc.). highly recommended for all people messing with md3s.
md3check (gui version) -
(c) 2003 sea[LD] (sea@reloadnet.com)
author details:
author : [email]sea@reloadnet.com[/email]
website: http://www.reloadnet.com
forums : http://www.reloadnet.com/board
irc : #liquiddesign @ gamesnet
contributors:
ydnar (co-author of picomodel library)
changelog:
1.1 (2003-05-21)
- merged latest picomodel library from cvs (0.8.20)
- new: now checks model shader name lengths
- new: now checks surface poly counts
- fixed: info text still shown when md3s specified as cmd-line param
1.0 (2003-05-03)
- initial gui version using old picomodel library (0.6.x)
0.1 (2002-XX-XX)
- initial command-line version. internal and unreleased.
description:
this simple helper utility allows you to error-check your md3 model files.
ever seen q3a spit out ingame error message like "too many verts on surface"
or similar? that for example is caused by a md3 model surface exceeding the
1000 vertex limit. ever wasted time finding the mesh group that causes this
error? and this is exactly where md3check comes in handy. basically it saves
you from having to check your model vertex counts in game. but it also
displays additional useful information about your md3 models. so how do i
use it? well, just open up a md3 model file in md3check and watch for red
error/warning messages. no further explanation required. md3check utilizes
the picomodel library written by ydnar and me which is also being used by
gtkradiant and q3map2 for native model loading support of static meshes
saves as md3, ase, 3ds, etc.
download it from here:
http://www.reloadnet.com/misc/apps/md3check-1.1.zip
some screenshots (v1.0):
main window
full output in main window
feedback always welcome.
makes using ydnars tool very easy