About possible crash-handler information... The article mentions hitting an obscure program bug may direct the player to this screen. I remember someone showing me a trick to unlock the level select by collecting all the rings in a level and not losing them. Granted, this was a while ago, and said person could have easily tapped the cartridge when I wasn't looking or fulfilled other requirements that I didn't notice, but that seemed to be the key to 'legitimately' accessing the screen. Can anyone verify this or something along those lines?

Seems strange that a crash handler would activate if all rings are collected without losing any, since skilled players would be able to do that quite easily. Then again, perhaps some kind of glitch causes the game to crash when all rings are collected. We'll need to look into that. Perhaps I could do some research.

[By the way, remember to sign your posts, by using four tildes.]

--AquaBat 15:43, 20 February 2013 (EST)

Ah, sorry, I usually remember to sign on wiki pages... Although yeah, like I said there could have been other unseen conditions that allowed him to reach it. LinkTheLefty 19:35, 20 February 2013 (EST)

More SFXs hidden in Sound Test

I do not know if the sound effects are used, but there are many who are beyond of 99. You can test it using this code ff0B82:009A / ff0B82:00XX
--Porcino (talk) 15:27, 13 August 2016 (EDT)

Jon Burton elaborates on the level select handler.

Apparently it was done to easily breeze through SEGA's quality assurance testing. https://youtu.be/i9bkKw32dGw

A similar technique was used for Mickey Mania, he says. --Joe411 (talk) 11:28, 30 September 2017 (EDT)

Sonic 3D Debug Mode

Another thing recently revealed by Jon Burton is a debug mode that nobody seemed to know about. This feature looks to only be in prototype versions. And even then, we don't know how to access it.
Once in the debug (noclip) mode, you can press start to begin level editing mode. Pressing B will then take you to the first object that was placed. You are invincible, however, enemies will still follow you, as if you were still Sonic. Just like the Sonic 1 Debug menu, moving close to other enemies while being another enemy will corrupt the sprites, but not because they aren't loaded yet. There isn't enough v-ram to store the sprites. Once you move further away, the sprite will get less and less corrupted.

The strings for this are not in a single released prototype (left alone the final game) and debug mode likewise is nowhere to be seen. --From: divingkataetheweirdo (talk) 21:48, 10 October 2017 (EDT)

I feel like it'll be in a prototype that hasn't been dumped yet. One of Burton's other videos shows an extremely early prototype which has (non-functional) split screen for some reason, it's also lacking any form of collision and uses a very early Green Grove tileset. I don't know if the prototype has music or if Burton overlaid the video footage with the music heard, but I digress.
https://www.youtube.com/watch?v=qH4eZcTmVM4
From: roach (talk) 12:05, 11 October 2017 (GMT)

Direction's Cut

Jon Burton planned to make his own ROM Hack of Sonic 3D that will improve the game into a notch, which is was announcement during his 25,000 sub's on YouTube. Should we add it on TCRF as a update of the game when it's release? (Then again, it should be called a official unofficial update of the game.) -- Trimint123 02:06, 3 November 2017 (EST)

I do think it's interesting. It's not everyday that someone who actually was part of the original dev team decides to look back at a project. It's not up to me to decide, but if the game isn't published I don't think it's worth making a whole article about it. There could be a small summary of the changes and fixed issues from the original on this page however. --Laenthor (talk) 18:12, 27 November 2017 (EST)