|
|
Post by exciter on Nov 14, 2012 19:21:23 GMT -5
For anyone with a more in-depth understanding of how the Debug Camera feature works in the Majora's Mask debug ROM, I was wondering if disabling the camera's debug interface is a possibility.
Presently defining 'disable' as a complete removal of the Debug interface and all it encompasses, including text, associated variables, ghost camera pointers & all that jazz.
To avoid any potential ambiguity, the Debug Camera feature of the ROM allows the user to position the camera at any angle they like from any point during any part of the game;
pretty cinematic, and very helpful.
Unfortunately, the interface which displays the Debug Camera's adjustable settings takes up a sizable portion of the game's display; and although the Ocarina Of Time Debug ROM's similarly-structured Debug Camera mode appears to have the ability to hide its own respective interface, most in-depth articles on the Majora's Mask debug ROM's functions don't seem to make it explicitly clear whether or not it shares the same functions as its predecessor.
Additionally, the Majora's Mask debug ROM's debug interfaces are mostly in Japanese; further complicating feature comparisons that are not explicitly noted in articles devoted to either ROM (the alternate having its own translated version, while the ROM in question does not, as far as I know).
Would appreciate any insight
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 15, 2012 6:18:17 GMT -5
For anyone with a more in-depth understanding of how the Debug Camera feature works in the Majora's Mask debug ROM, I was wondering if disabling the camera's debug interface is a possibility. Presently defining ' disable' as a complete removal of the Debug interface and all it encompasses, including text, associated variables, ghost camera pointers & all that jazz. To avoid any potential ambiguity, the Debug Camera feature of the ROM allows the user to position the camera at any angle they like from any point during any part of the game; pretty cinematic, and very helpful. Unfortunately, the interface which displays the Debug Camera's adjustable settings takes up a sizable portion of the game's display; and although the Ocarina Of Time Debug ROM's similarly-structured Debug Camera mode appears to have the ability to hide its own respective interface, most in-depth articles on the Majora's Mask debug ROM's functions don't seem to make it explicitly clear whether or not it shares the same functions as its predecessor. Additionally, the Majora's Mask debug ROM's debug interfaces are mostly in Japanese; further complicating feature comparisons that are not explicitly noted in articles devoted to either ROM (the alternate having its own translated version, while the ROM in question does not, as far as I know). Would appreciate any insight Just don't use it, it's a fake anyway. The MM 'debug rom' is just a MM (E) rom that some guy did an assembly hack to. It's not legit. |
|
|
|
Post by exciter on Nov 15, 2012 9:39:11 GMT -5
Thank you very much
|
|
xdaniel
Full Member
[Mo0:0]
Posts: 90
|
Post by xdaniel on Nov 15, 2012 11:46:15 GMT -5
Just don't use it, it's a fake anyway. The MM 'debug rom' is just a MM (E) rom that some guy did an assembly hack to. It's not legit. I've heard that time and time again but IIRC never seen any proof. So why exactly is it a fake? What exactly has been hacked? Why does ex. the build information screen - excluding creator and build date - match another unreleased debug build (3:10), which for the most part doesn't even exist in the retail builds? Why does it have debugging features that as far as I know exist in neither the retail builds nor the MQ Debug ROM? I've seen enough proof to believe that it's the real deal, yet nothing to suggest it's fake. If you have any proof against its authenticity, I really would like to see it. |
|
|
|
Post by exciter on Nov 15, 2012 13:44:09 GMT -5
Interesting.
Not to contrast anyone's opinion on the two ROMs here, as general hacking isn't particularly my forté, but from an audio point of view, as far as I can tell, this particular 'debug' ROM is unique in comparison with the Majora's Mask (E) ROM SoulofDeity mentioned earlier.
I had extracted the audio files from the debug ROM in question as well as the Majora's Mask (E) ROM, and there is a myriad of differences between the two.
Using the same set variables, outgoing sample rate, & exporting method for both ROMs, the questionable Majora's Mask debug ROM appears to store its sounds in a completely different manner than the Majora's Mask (E) ROM.
Most instrument files (Ocarina sounds, Giant's voice samples, etc.) as well as general sound files (Link grunts, ambient sounds, etc.) on the (E) ROM seem to be organized by their classification; in other words, you'll find the instrument sounds stored near the other instrument sounds, the ambient nature sounds with other ambient nature sounds, and so on.
The questionable Majora's Mask debug ROM on the other hand, seems to store its sound files according to their usage in the game (instruments used in the Skull Kid's theme are near the other instruments featured in his theme, Gerudo screams and other associated sounds are stored near the instruments and samples used in the Pirate's Fortress theme, and so on).
The aforementioned difference could be related to the assembly hack SoulofDeity mentioned as far as I know, but to reassemble every single sound file in the entire project top-to-bottom, and still have them point where they need to in the game (Link yelling when he swings his sword, instead of screaming like Odolwa) would be an extraordinarily meticulous task, to say the least lmao
I'd be happy to confirm this relationship between the supposed debug ROM and the Majora's Mask (E) ROM as a pattern by extracting the sound files from the Ocarina Of Time debug ROM as well as its own respective (E) ROM and comparing the relationship between the two ROMs' sound storage methods, but from an observational standpoint, I am fairly certain the Majora's Mask 'debug' ROM file in question is as advertised.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 15, 2012 16:00:04 GMT -5
Just don't use it, it's a fake anyway. The MM 'debug rom' is just a MM (E) rom that some guy did an assembly hack to. It's not legit. I've heard that time and time again but IIRC never seen any proof. So why exactly is it a fake? What exactly has been hacked? Why does ex. the build information screen - excluding creator and build date - match another unreleased debug build (3:10), which for the most part doesn't even exist in the retail builds? Why does it have debugging features that as far as I know exist in neither the retail builds nor the MQ Debug ROM? I've seen enough proof to believe that it's the real deal, yet nothing to suggest it's fake. If you have any proof against its authenticity, I really would like to see it. I rember seeing the guy's comment in a forum asking "lol, who here dares me to make an Mm debug rom XD" Despite what the rom has init, unless Nintendo confirms that it acually is a debug rom, we must assume otherwise. |
|
|
|
Post by exciter on Nov 15, 2012 16:06:43 GMT -5
The primary concern here is hiding the features that accompany the 'debug' features in the ROM.
If camera angles & controlling aesthetics are features that can be performed as easily as the 'debug' ROM using codes in the (E) ROM, then that's swell as well.
I'll review the code page thinger for Majora's Mask & see what can be done using the (E) version, although I don't recall seeing too many listed codes that would achieve the desired result besides the 'disable HUD' code.
Feel free to supplement any codes you're aware of that would be of use here, of course
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 15, 2012 16:12:30 GMT -5
The primary concern here is hiding the features that accompany the 'debug' features in the ROM. If camera angles & controlling aesthetics are features that can be performed as easily as the 'debug' ROM using codes in the (E) ROM, then that's swell as well. I'll review the code page thinger for Majora's Mask & see what can be done using the (E) version, although I don't recall seeing too many listed codes that would achieve the desired result besides the 'disable HUD' code. Feel free to supplement any codes you're aware of that would be of use here, of course There's a code I've been using the past few days on MM (U) that opens a map select identical to the one used by the MQ debug rom. 811BDA04 00C7
811BDA06 ADF0
811BDA08 00C7
811BDA0A E2D0
811BDA0C 8080
811BDA0E 0910
811BDA10 8080
811BDA12 3DF0
811BDA18 8080
811BDA1A 1B4C
811BDA1C 8080
811BDA1E 1B28
D11BDA00 8077
801F331B 0000
D13E6B3A 2030
801F331B 0002
D13E6B3A 2030
813FF394 0114Not sure if it works on MM (E), and you have to have a file on file 1 |
|
|
|
Post by exciter on Nov 15, 2012 16:36:34 GMT -5
Not too shabby.
Still browsing around for codes that allow the user to control the camera in a manner similar to the 'debug camera' feature in the debug ROM from earlier.
The process itself would be much more simple if a code to disable the debug display on the questionable debug ROM existed, since it already has the camera feature. Could just turn the code on or off as desired.
|
|
xdaniel
Full Member
[Mo0:0]
Posts: 90
|
Post by xdaniel on Nov 15, 2012 16:43:29 GMT -5
I rember seeing the guy's comment in a forum asking "lol, who here dares me to make an Mm debug rom XD" Despite what the rom has init, unless Nintendo confirms that it acually is a debug rom, we must assume otherwise. That was Cen if I remember correctly, so I dunno - I'm used to taking everything he says with a pinch of salt. I'm more inclined to believe that, by the time of that comment, he had actually acquired the ROM, then joked about making it prior to anyone else knowing about it, so that people might think "omg he's done it in a matter of days! wtf?" I'm still convinced it's real because of ex. it's contents, but 100% proof is impossible unless Nintendo does come out and confirms it, yeah. |
|
