- Posts: 1026
- Joined: 16-June 04
- Gender:Male
- Wiki edits:109
I kinda wanted to make a full fledged topic full of stuff from this game (since the .ar format has been cracked open). But I don't have a lot of free time these days, so I'm mainly going to talk about debug crap that might possibly still be in the game in some shape or form.
Before I begin, just a reminder that you can get more information about unpacking the files from Unleashed in this topic over at CulT. Much much much much much thanks to Link for everything.
First of all, the files are sorta formated like this (sorry for any inaccuracies or an error in my terminology):
1.) Anything with a # next to the file name are where the .xml files are stored. The object layouts in levels, menu positions, configs, etc are all in these files for everything.
2.) The .arl files contain the list of filenames that the .ar files have.
3.) Any other .ar.## files are where the actual files are kept. Textures and GUI/Menu graphics are in .dds format for easy viewing. The models themselves, I have no idea (but it's easy to differentiate what's a model, material, etc because the filenames are a direct representation of what they are). Most of the sfx for each stage are in the .ar files in .csb format, so if you can listen to all the sound effects and music using CriWare's publicly released tools.
Now onto the debug stuff. First of all, let's start with the executable (the .xex file). After decompressing and unencrypting the .xex with XexTools, I was able to see all the strings in the .xex. The .xex contains the graphics for the achievements, so if you were wondering where they were, they're in here. Upon further investigation, the debugs that were featured in the Hedgehog Engine presentation are still in the game. The title bar of each application is written in Unicode, so that's why it probably went undetected. Not sure where the graphics are for the actual menus are, but I'm sure they're tucked away in the .xex somewhere. But how do you possibly activate these debugs? Well...
In #SystemCommon.ar, the .xml file for possibly activating this debug is located here. While it isn't clear what setting would cause the actual debug to show up, I think it's safe to assume that you have to choose the "Person" (programmers last name) who's debugging to bring it up. Again, I'm not sure if this is all you have to do, but it would be nice wouldn't it? It seems that it might be the only thing that needs to go from false -> true, since the Params are already activated by default, they just need something to permit the debugs to load.
Of course, there's also a version of SystemCommon without the #, which holds the files used by the debug. It has your debug models (arrows, cameras, etc), and possibly some other stuff.
Now of course, the actual debug needs configurations too. I think this is where #Applications.ar comes in, which has the .xmls for a Stage list, a stage jump, a movie player, a flag list, etc. But from the looks of the stage list, there are no test maps. The only reference to a test map is in the .xex, but the actual files for it are all gone.
Unfortunately, this is all I kinda care about for the moment. If I have time, I'll go through the game with a comb and see if I can find anything interesting. But I don't want to end the topic with just text so, I did find a few weird ass graphics pertaining to the debug:
Another thing you have to note, I don't HAVE A JTAGGED 360. So I can't really mess around with anything. I'm hoping Saz, or Jimmy, or someone who cares could possibly try to investigate a little bit more.
But I hope you found this interesting. There has to be a way to get the debug out of this game somehow...
Before I begin, just a reminder that you can get more information about unpacking the files from Unleashed in this topic over at CulT. Much much much much much thanks to Link for everything.
First of all, the files are sorta formated like this (sorry for any inaccuracies or an error in my terminology):
1.) Anything with a # next to the file name are where the .xml files are stored. The object layouts in levels, menu positions, configs, etc are all in these files for everything.
2.) The .arl files contain the list of filenames that the .ar files have.
3.) Any other .ar.## files are where the actual files are kept. Textures and GUI/Menu graphics are in .dds format for easy viewing. The models themselves, I have no idea (but it's easy to differentiate what's a model, material, etc because the filenames are a direct representation of what they are). Most of the sfx for each stage are in the .ar files in .csb format, so if you can listen to all the sound effects and music using CriWare's publicly released tools.
Now onto the debug stuff. First of all, let's start with the executable (the .xex file). After decompressing and unencrypting the .xex with XexTools, I was able to see all the strings in the .xex. The .xex contains the graphics for the achievements, so if you were wondering where they were, they're in here. Upon further investigation, the debugs that were featured in the Hedgehog Engine presentation are still in the game. The title bar of each application is written in Unicode, so that's why it probably went undetected. Not sure where the graphics are for the actual menus are, but I'm sure they're tucked away in the .xex somewhere. But how do you possibly activate these debugs? Well...
CODE
<?xml version="1.0" encoding="utf-8" standalone="no" ?>
<Debug.prm.xml>
<Flag>
<Category>
<EvilEnemy>
<Param>
<DisableBodySparkle>false</DisableBodySparkle>
<DisableFrustum>false</DisableFrustum>
<DrawDrivingBehavior>false</DrawDrivingBehavior>
<DrawEyeSight>false</DrawEyeSight>
<DrawInformation>false</DrawInformation>
<DrawMoveDirection>false</DrawMoveDirection>
<DrawWayPoint>false</DrawWayPoint>
<EnableDebugDraw>false</EnableDebugDraw>
</Param>
</EvilEnemy>
<NPC>
<Param>
<DrawNPCInfomation>false</DrawNPCInfomation>
</Param>
</NPC>
<Person>
<Param>
<Naito>false</Naito>
<Nakazawa>false</Nakazawa>
<Okada>false</Okada>
<Takeshima>false</Takeshima>
</Param>
</Person>
<SonicEnemy>
<Param>
<DrawDayEnemyInfo>false</DrawDayEnemyInfo>
</Param>
</SonicEnemy>
<System>
<Param>
<DrawNavigationMesh>false</DrawNavigationMesh>
<DrawPlayerPosition1D>true</DrawPlayerPosition1D>
<eAlwaysChanceAttackBackward>false</eAlwaysChanceAttackBackward>
<eAlwaysChanceAttackForward>false</eAlwaysChanceAttackForward>
</Param>
</System>
</Category>
</Flag>
<Trace>
<Category>
<Category>
<Param>
<Camera>false</Camera>
<Enemy>true</Enemy>
<Havok>true</Havok>
<Hedgehog>true</Hedgehog>
<Hoge>true</Hoge>
<Memory>true</Memory>
<Sound>true</Sound>
<SoundError>true</SoundError>
</Param>
</Category>
</Category>
</Trace>
</Debug.prm.xml>
<Debug.prm.xml>
<Flag>
<Category>
<EvilEnemy>
<Param>
<DisableBodySparkle>false</DisableBodySparkle>
<DisableFrustum>false</DisableFrustum>
<DrawDrivingBehavior>false</DrawDrivingBehavior>
<DrawEyeSight>false</DrawEyeSight>
<DrawInformation>false</DrawInformation>
<DrawMoveDirection>false</DrawMoveDirection>
<DrawWayPoint>false</DrawWayPoint>
<EnableDebugDraw>false</EnableDebugDraw>
</Param>
</EvilEnemy>
<NPC>
<Param>
<DrawNPCInfomation>false</DrawNPCInfomation>
</Param>
</NPC>
<Person>
<Param>
<Naito>false</Naito>
<Nakazawa>false</Nakazawa>
<Okada>false</Okada>
<Takeshima>false</Takeshima>
</Param>
</Person>
<SonicEnemy>
<Param>
<DrawDayEnemyInfo>false</DrawDayEnemyInfo>
</Param>
</SonicEnemy>
<System>
<Param>
<DrawNavigationMesh>false</DrawNavigationMesh>
<DrawPlayerPosition1D>true</DrawPlayerPosition1D>
<eAlwaysChanceAttackBackward>false</eAlwaysChanceAttackBackward>
<eAlwaysChanceAttackForward>false</eAlwaysChanceAttackForward>
</Param>
</System>
</Category>
</Flag>
<Trace>
<Category>
<Category>
<Param>
<Camera>false</Camera>
<Enemy>true</Enemy>
<Havok>true</Havok>
<Hedgehog>true</Hedgehog>
<Hoge>true</Hoge>
<Memory>true</Memory>
<Sound>true</Sound>
<SoundError>true</SoundError>
</Param>
</Category>
</Category>
</Trace>
</Debug.prm.xml>
In #SystemCommon.ar, the .xml file for possibly activating this debug is located here. While it isn't clear what setting would cause the actual debug to show up, I think it's safe to assume that you have to choose the "Person" (programmers last name) who's debugging to bring it up. Again, I'm not sure if this is all you have to do, but it would be nice wouldn't it? It seems that it might be the only thing that needs to go from false -> true, since the Params are already activated by default, they just need something to permit the debugs to load.
Of course, there's also a version of SystemCommon without the #, which holds the files used by the debug. It has your debug models (arrows, cameras, etc), and possibly some other stuff.
Now of course, the actual debug needs configurations too. I think this is where #Applications.ar comes in, which has the .xmls for a Stage list, a stage jump, a movie player, a flag list, etc. But from the looks of the stage list, there are no test maps. The only reference to a test map is in the .xex, but the actual files for it are all gone.
Unfortunately, this is all I kinda care about for the moment. If I have time, I'll go through the game with a comb and see if I can find anything interesting. But I don't want to end the topic with just text so, I did find a few weird ass graphics pertaining to the debug:
Another thing you have to note, I don't HAVE A JTAGGED 360. So I can't really mess around with anything. I'm hoping Saz, or Jimmy, or someone who cares could possibly try to investigate a little bit more.
But I hope you found this interesting. There has to be a way to get the debug out of this game somehow...
This post has been edited by evilhamwizard: 20 July 2010 - 01:01 PM
