An intro-cinematic crash was reported during the follow-up to #123, after replacing a malformed MD5 mesh with stock meshes. The later comment says the save loaded, but does not establish whether this separate cinematic crash still occurs.
The supplied intro log reaches active game/airdefense1 gameplay and autosaves, then ends with:
ERROR: idRenderModelMD5::NearestJoint: surfaceNum > meshes.Num()
This is distinct from the repaired ReadTrace save-layout mismatch. Current source still contains this fatal guard in idRenderModelMD5::NearestJoint; the log alone does not identify the model/surface pair that reached it or prove the cause.
Next step: confirm whether this still reproduces on current main with the same map/mod. If it does, collect the fresh log and the exact map/model setup and inspect the render surface ID passed to NearestJoint.
Original report: #123 (comment)
An intro-cinematic crash was reported during the follow-up to #123, after replacing a malformed MD5 mesh with stock meshes. The later comment says the save loaded, but does not establish whether this separate cinematic crash still occurs.
The supplied intro log reaches active
game/airdefense1gameplay and autosaves, then ends with:This is distinct from the repaired
ReadTracesave-layout mismatch. Current source still contains this fatal guard inidRenderModelMD5::NearestJoint; the log alone does not identify the model/surface pair that reached it or prove the cause.Next step: confirm whether this still reproduces on current main with the same map/mod. If it does, collect the fresh log and the exact map/model setup and inspect the render surface ID passed to
NearestJoint.Original report: #123 (comment)