Any chance you could post more/all of your modeldef? I think you *might* be making the same incorrect assumption that I made when first using modeldefs a while back.

Model numbers are for associating more than one model to a single frame. If you need 256 models, it means that at least one of your frames has 256 models associated with it at one time.

If your frames and models are sequential, and each frame only needs one model/skin allocated to it, then you just write a new definition for each frame and each one can be model 0.

e.g. this is one that I was doing today:

- Code: Select all • Expand view
`//Normal appearance and regular death`

Model NJZPoisonShroom

{

Path "Models"

Model 0 "shroom2.md3"

Skin 0 "shroompois.png"

Scale 1.2 1.2 1.2

FrameIndex SHRM A 0 0

FrameIndex SHRM B 0 1

FrameIndex SHRM C 0 2

FrameIndex SHRM D 0 3

FrameIndex SHRM E 0 4

FrameIndex SHRM F 0 5

}

//Ice death

Model NJZPoisonShroom

{

Path "Models"

Model 0 "shroom2.md3"

Skin 0 "shroompoisice.png"

Scale 1.2 1.2 1.2

FrameIndex SHRM G 0 0

}

//Burn death

Model NJZPoisonShroom

{

Path "Models"

Model 0 "shroom2extra.md3"

Skin 0 "shroompoisburn.png"

Scale 1.2 1.2 1.2

FrameIndex SHRM H 0 0

FrameIndex SHRM I 0 1

FrameIndex SHRM J 0 2

FrameIndex SHRM K 0 3

FrameIndex SHRM L 0 4

FrameIndex SHRM M 0 5

}

//Disintegrate death

Model NJZPoisonShroom

{

Path "Models"

Model 0 "shroom2extra.md3"

Skin 0 "shroompoisdis.png"

Scale 1.2 1.2 1.2

FrameIndex SHRM N 0 0

FrameIndex SHRM O 0 1

FrameIndex SHRM P 0 2

}

Two different models, 4 different skins but no model index number higher than 0

(I think the above can actually be consolidated a bit more than that, but the above layout works for me.)