This thread is full of wrong.
First, C3 files aren't encrypted forms of a public 3D format, they're really their own format. TQ really did make a 3DS plugin to model their meshes.
Don't believe me?
Code:
struct C3Phy
{
char *lpName; // 名字
DWORD dwBlendCount; // 每个顶点受到多少根骨骼影响
DWORD dwNVecCount; // 顶点数(普通顶点)
DWORD dwAVecCount; // 顶点数(透明顶点)
PhyVertex *lpVB; // 顶点池(普通顶点/透明顶点)
LPDIRECT3DVERTEXBUFFER8 vb;
DWORD dwNTriCount; // 多边形数(普通多边形)
DWORD dwATriCount; // 多边形数(透明多边形)
WORD *lpIB; // 索引池(普通多边形/透明多边形)
LPDIRECT3DINDEXBUFFER8 ib;
char *lpTexName; // [ be used by plugin ]
int nTex;
int nTex2;
D3DXVECTOR3 bboxMin, bboxMax;
C3Motion *lpMotion;
float fA, fR, fG, fB;
C3Key Key;
BOOL bDraw;
DWORD dwTexRow;
D3DXMATRIXA16 InitMatrix;
// 12-20-2002 : "STEP"
D3DXVECTOR2 uvstep;
};
Well there's a C3 phy for you.
And next, the EO C3 files are the same, and are compatible with CO. The only thing is they're usually the wrong size or wrong rotation. If they weren't `compatible,` they wouldn't load in the first place.