Track the program,and see how it read data,maybe I can figure out how bones data work?
Using a debugger nearly everything is possible. But it might take much, much more time than just 2 hours.
Years ago I debugged games to find/enable hidden developer's consoles which was not easy
but seems to me not as hard as what you want to try out.
2 months ago I was in a render loop of a game to examine a scroll casting in "single frame mode".
Hours later I found me lost in the depth of the assembly code. (What a waste of time and life, hehehe...)
Same as with the analysing of 3D model's formats data you're required to get an idea of the code structure here
(write down the call tree of functions at least).
In a D3D9 game's ASM code I found this line in a jump table:
009F7A9A $-FF25 1816AE00 JMP DWORD PTR DS:[<&d3dx9_43.D3DXCreateMesh>
You could attach a debugger to the game you want to explore and try to find a similar line.
Set a breakpoint there. If it is hit continuously trace the code until you meet a better location to place a BP.
On refresh of a scene where new objects are to be displayed that BP might be hit.
Most important: for my experience the game will crash then if it doesn't run in windowed mode
You might search for code where the LODs of buildings are being processed for example.
Characters would be the second step, I think.
Extracting simple models: http://forum.xentax.com/viewtopic.php?f=29&t=10894Make_H2O-ForzaHor3-jm8.zip
"We are Microsoft. You will be assimilated. Resistance is Futile."