- Joined
- Nov 11, 2004
- Messages
- 1,986
I would like to use this thread to keep discussing the secrets hidden in the MDX format.
Hmm can't find the cinematic models in the mpq, any hints?
Constant color makes your model not be affected by time of the day coloring, like in night models get a little bluer.
Full Resolution, does indeed ignore mipmapping. It's used for loading screen models.
PrimesFarZ and NearZ changes how your model is rendered in the 3d space. They have to do with which objects are rendered over others. Not sure pretty well how the exactly work.
Layers also have more unknown flags:
ShadingFlags;
//#1 - Unshaded
//#2 - SphereEnvironmentMap
//#4 - ???
//#8 - ???
//#16 - TwoSided
//#32 - Unfogged
//#64 - NoDepthTest
//#128 - NoDepthSet
There's also this property which I don't know what it does:
CoordId
There's also this in geosets:
I know that it looks chinese, but I think coordId has to do with it. Geosets appear to be able to handle two or more unwraps.
Here's what I was saying about faces:
funny thing is that we only use triangles, but other shit is apparently allowed. The question is what are their numbers.
There are also some unknown flags on geosets:
DWORD MaterialId;
DWORD SelectionGroup;
DWORD SelectionFlags; //0 - None
//#1 - ???
//#2 - ???
//#4 - Unselectable
Sadly if you want to experiment by changing this glags, you require a hex editor: http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm
There's also one thing that should be explored which are:
I've only seen them used by models like dragons to drop many bones when they die. This type of emitter, emits models and behaves different to particle emitters 2. Here's a bit of what I know about them:
Things I don't know about them:
Their potential:
Hmm can't find the cinematic models in the mpq, any hints?
Constant color makes your model not be affected by time of the day coloring, like in night models get a little bluer.
Full Resolution, does indeed ignore mipmapping. It's used for loading screen models.
PrimesFarZ and NearZ changes how your model is rendered in the 3d space. They have to do with which objects are rendered over others. Not sure pretty well how the exactly work.
Layers also have more unknown flags:
ShadingFlags;
//#1 - Unshaded
//#2 - SphereEnvironmentMap
//#4 - ???
//#8 - ???
//#16 - TwoSided
//#32 - Unfogged
//#64 - NoDepthTest
//#128 - NoDepthSet
There's also this property which I don't know what it does:
CoordId
There's also this in geosets:
Code:
DWORD 'UVAS';
DWORD NrOfTextureVertexGroups;
DWORD 'UVBS';
DWORD NrOfVertexTexturePositions;
struct VertexTexturePosition[NrOfVertexTexturePositions]
{
FLOAT2 TexturePosition;
};I know that it looks chinese, but I think coordId has to do with it. Geosets appear to be able to handle two or more unwraps.
Here's what I was saying about faces:
Code:
DWORD 'PTYP';
DWORD NrOfFaceTypeGroups;
struct FaceTypeGroup[NrOfFaceTypeGroups]
{
DWORD FaceType; //4 - Triangles
//??? - Triangle fan
//??? - Triangle strip
//??? - Quads
//??? - Quad strip
};
DWORD 'PCNT';
DWORD NrOfFaceGroups;funny thing is that we only use triangles, but other shit is apparently allowed. The question is what are their numbers.
There are also some unknown flags on geosets:
DWORD MaterialId;
DWORD SelectionGroup;
DWORD SelectionFlags; //0 - None
//#1 - ???
//#2 - ???
//#4 - Unselectable
Sadly if you want to experiment by changing this glags, you require a hex editor: http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm
There's also one thing that should be explored which are:
Code:
// Observe properties of an Object.
// EmitterUses___ is a flag that appears only when there is a Path
// in Particle and their appropriate flag is set.
// Maximum length of path is 256 characters (0x100 bytes)
ParticleEmitter <string_name> {
ObjectId <long>,
Parent <long>,
<EmitterUsesMDL|EmitterUsesTGA>,
static EmissionRate <float>,
static Gravity <float>,
static Longitude <float>,
static Latitude <float>,
(Visibility <float>)
Particle {
static LifeSpan <float>,
static InitVelocity <float>,
Path <string_path>,
}
(Translation { <float_x>, <float_y>, <float_z> })
(Rotation { <float_a>, <float_b>, <float_c>, <float_d> })
(Scaling { <float_x>, <float_y>, <float_z> })
}I've only seen them used by models like dragons to drop many bones when they die. This type of emitter, emits models and behaves different to particle emitters 2. Here's a bit of what I know about them:
- They are based on a type of particle system in 3ds max called SuperSpray.
- Basicly you use them for emitting models.
- Emitted models will only play Stand animation.
- Longitude and Latitude use radians instead of degrees. They say the scope of the emission.
- Converting them in magos from mdl may erase them.
- Guesst's MDL-MDX convertor crashes if your model has them.
- Only Yobsul's MDL/X Convertor can convert them properly.
- NeoDex, unlike Art Tools, can export them, but they seem to be hard to set.
Things I don't know about them:
- Can the emitted models have ribbon emitters and/or particle emitters 2?
- What are the MDX chunk names for animated latitud, longitude, gravity, lifespan, emission?
Their potential:
- Imagine emitting ribbon emitters, crazy effects could be achieved.
- Emitting models with other particle systems could be nice for reproducing effects like blood splats or shit.
