Alright, with the DVD version byte set to 0x91 as per Treeki in the TP thread and a controller plugged into port 3 of the GCN (or emulator), the debug console Dark Linkaël posted about before opens up on its own, without the need for additional codes.

Some things I noticed while messing around with it in WW NTSC-J - maybe some of it is known already, I'm not sure.

Anyway, the game starts up with some performance indicators at the bottom of the screen, which probably do not exclusively show sound activity. I assumed the same for OoT's indicators back in the day, but as we later assumed and got confirmed through MM Debug's descriptions, those are for both graphics and audio at the very least.



Next up, there's the memory information printed on the right hand side of the screen, which you can cycle through with R+Z on controller 3. "RelUsed Blk/Bytes" is the default, while you can also make "ARAM Free" and "TotalFree", "TotalFree/MaxFree", "MaxUsed/HeapSize" and "Used Blk/Bytes" appear.

Going on, pressing Z on controller 3 alone opens up the console, which you can control following the instructions printed on the screen.



In addition to those instructions, you can also press Left, Up and Right on the D-Pad of controller 3 to print some more information to the console:





Up and Right print some memory allocation stats, while Left prints a bunch of information about the current map, like archives used, actors loaded, etc. which is quite interesting to see (or at least for me )

And... that's pretty much all I could find straight away, not sure if there's more to the debug console or the performance bars. Does anyone know if the DVD version byte also enables the map select menu or any other debugging features?


____________________

Using Dark Linkaël's code 04000004 30310091, this also works perfectly on real hardware - PAL Wii with original PAL WW, using NeoGamma to run the game with codes:





____________________

The performance indicators at the bottom of the screen are handled by a class named "JUTProcBar".

I haven't studied the code for them very thoroughly, but the data it shows is related to two main things:
- Frame rate/how long it takes to do specific things
- How much space is available in specific Heaps

The fourth controller is also used for debug things. Don't know what for exactly.



Anyway, about the map select: It's a scene on its own, and handled by the following functions:
dScnMenu_Create(scene_class *)
dScnMenu_Draw(menu_of_scene_class *)
dScnMenu_Execute(menu_of_scene_class *)
dScnMenu_IsDelete(menu_of_scene_class *)
dScnMenu_Delete(menu_of_scene_class *)
phase_1(menu_of_scene_class *)
phase_2(menu_of_scene_class *)

All the scene management stuff is handled by functions prefixed with fopScn. In particular, this is the function that executes a scene change:
bool fopScnM_ChangeReq(scene_class *currentSceneCls, short newSceneID, short unk1, unsigned short unk2);

The scene ID is actually a profile ID (the profile is obtained using the function fpcPf_Get(short)). The profile is a small structure that tells the game how to construct a specific object/scene/etc.

Here are all the ones I can find:
5 - ScnLogo
6 - ScnMenu
7, 8, 9 - ScnPly variations
10/0xA, 11/0xB - ScnTitle
12/0xC, 13/0xD - ScnName
14/0xE, 15/0xF - ScnOpen
20/0x14 - ScnRoom

But unfortunately, there's no function that calls fopScnM_ChangeReq with 6 So the map select menu is totally inactive, even when the debug mode is enabled using version >= 0x91.

The code in the TCRF article works by changing profile 12 so it makes a ScnMenu instead of ScnName.


If there's anything else you'd like me to look at in the code, let me know...

____________________

Originally posted by Dark Linkaël

---

Very interesting your explanations, I already know a little about the subject.

To find the map select, I had to replace "l_dScnName_Method" by "l_dScnMenu_Method".

---

Yeah, that's the same thing I'm talking about. It's just that I never loaded the names for that section for some reason. I've done it now.

Originally posted by Dark Linkaël

---

Otherwise, there is nothing in this debug mode? There is just the debug console and what is mentioned in this topic?

---

I'll check that out now...

____________________