Due to overwhelming demand, I'm starting a thread to summarize the current knowledge of .3 files, and to spur a new thrust for additional insights. The idea is to break down this task into smaller chunks, producing simple tools as necessary.
The .3 files are scripts which tell the game engine how to draw objects. On first glance, they are just binary data. But, after some research, it has been found that the files can be broken down into lines of 'opcodes' which describe how the vertices and polygons go together.
First, we need a tool to take the binary data and reformat it into ASCII text, so it can be edited more easily, then be able to produce a binary file again for testing in the game.
I've created an extremely user-unfriendly tool here:
http://rapidshare.com/files/239704747/parse_3.zipYou can put any .3 files you want to process in the '3_in' directory. When you press the 'Convert to Text' button, all the files in the directory will be processed and the results placed in the '3txt_out' directory. A similar procedure is used to convert back to .3 format again.