Oh hell yes! Admittedly, I'm not an SADX modder myself, but this stuff should be immensely-helpful for figuring out how the game works. Me and Cucky were able to make a full decompilation of the original Windows version of Cave Story, using debug data found in the Linux port. Granted, I don't think SA1 has ever had the luxury of an unoptimised EXE like Cave Story did, but that didn't stop people from decompiling Diablo.
The short answer is 'no', sorry - it can be used to create something similar to the original source code, but it would still require months, possibly years, of work. Technically, decompilations are possible without debug data (just look at the Super Mario 64 decompilation project), but stuff like this makes it a lot easier. Me and Cucky would never have been able to make our decompilation without it.
Wow, this is amazing! That chao_garden_info stuff looks like is the main chao save struct, while CHAO_PARAM_GC is what we called "ChaoDataBase" in the disassembly (sizeof matches and everything), which still has a lot of missing fields that would be useful to know for editors (I would have never thought those first fields are all GBA stuff, I figured the first one is but not all the other ones) I would appreciate it a lot if you could send that struct early cuz I can't wait to see it, this has been the longest two days ever lol EDIT: thought i would also elaborate on some other neat details, task is ObjectMaster which has been evident from some SA2 object names and some debug messages in SADX, taskwk* is probably what we call "Data1". CCL_Init is probably Collision_Init, which will also be nice to look into since the collision data wasn't ever really clear. Back to the chao, I noticed in that screenshot that there's AL_MOTION_INFO, which based on the size is probably MotionTableEntry, the naming convention is odd because motiontable's where used for other things other than chao, yet the AL_ prefix suggests it's a Chao-only thing. AL_SHAPE_ELEMENT is KarateOpponent, which is used in RaceTimeData, which seems to be called AL_RECORD here. There's also EDIT_FUNC_ENTRY which is ChaoDebugFunction, the name probably comes from the chao debug menu being called EDIT MODE MENU in that one SADXGC proto.
Question: is there any indication that this is an optimized binary, or are we dealing with a full fat unoptimized debug build?
Bumpy bump, build is released! please share your findings! Link is in first post and here just to make things easier: https://mega.nz/#!SV8z1QzJ!Gl32PiekzukRikiu_wALU-l7lMB9wPnCaTK6pEHQLKU
Legitimately been waiting for this the second you posted about it earlier this month. Cannot WAIT to see what gets found out / made easier with this!!
Bumping again, a user on ObscureGamers just dropped 5GB of new Sonic Adventure 360 builds! Build dates as follows, Jan 08, 2010 Jan 22, 2010 Jan 29, 2010 Mar 25, 2010 Aug 01, 2010 Some are passworded, but you can extract with WXPIRS I believe to give access to files. https://mega.nz/#!hkkTVTCC!cf6b49228pWMt6VJoJwwVrddSj0d_kBcOlX54rzwSgY
Hmmm interesting! Some of these symbol names are familiar. They got carried over to Heroes. Wasn't expecting that.
Do these builds contain any art assets? I'd be curious to see if anything from the source tree accidentally got included in the build(s) that didn't end up in retail. It would be awesome to see some unused SA1 assets that have been lost.
There's a few builds that have a "Password" The one for Build 147 - as indicated in the ArcadeInfo.xml with the file name "783A4111AAE08A4C4F8F2F8C50593253A04D3D1658" is Sonikudamoxi The one for Build 209 and has the file name "5DD1F1516B2BFF7639F7B9B99E18C07E529BF92A58" is damoxifL Follow the capitalization. This will get you past those troll screens Enjoy! <3 also Special Thanks to Lance McDonald @manfightdragon on twitter who helped pull the strings.
