That reminds me, any news on the 1000$ bounty that was posted a while back? I don't follow news of this game very often.
The prevailing thought is it's not an exploitable glitch, but instead it was a cosmic ray bitflip. The Y position does not seem to have changed to the ceiling, but instead to a value that is a single bit flip from the original Y value.
Build a man a fire, warm him for a day,
Set a man on fire, warm him for the rest of his life.
That reminds me, any news on the 1000$ bounty that was posted a while back? I don't follow news of this game very often.
The prevailing thought is it's not an exploitable glitch, but instead it was a cosmic ray bitflip. The Y position does not seem to have changed to the ceiling, but instead to a value that is a single bit flip from the original Y value.
The solution is obvious. We just need someone to code a universe emulator, and then someone can make a TAS in which Super Mario 64 is played on an emulated physical N64 and the RNG of the universe is manipulated to produce the cosmic ray consistently (the system requirements for such an emulator could be a problem, but should not be much worse than BizHawk).
That reminds me, any news on the 1000$ bounty that was posted a while back? I don't follow news of this game very often.
The prevailing thought is it's not an exploitable glitch, but instead it was a cosmic ray bitflip. The Y position does not seem to have changed to the ceiling, but instead to a value that is a single bit flip from the original Y value.
The solution is obvious. We just need someone to code a universe emulator, and then someone can make a TAS in which Super Mario 64 is played on an emulated physical N64 and the RNG of the universe is manipulated to produce the cosmic ray consistently (the system requirements for such an emulator could be a problem, but should not be much worse than BizHawk).
You'd only need to emulate the console and cosmic rays, QRNG is hard to emulate though.
So much of the vc vs console discussion has been revolving around the 4f it takes to lock the camera aye?
You can't lock the camera in the castle lobby, and there was a 0x star strategy that required entering parallel universes in the castle lobby, which as a result crashes on a real N64 with no possible workaround.
Joined: 9/21/2009
Posts: 1047
Location: California
Synx wrote:
I really hope somebody wants to and is able to complete the new any%
Funny coming from you of all people, who never TASes anything. No need to be sarcastic when I gave a real answer.
Secondly, no one is doing anything unless it's our tiny group that got into VCutM with 0 stars...because no one else would be able to do the aforementioned task with how technical and specific the numbers are. So basically, you're waiting for us no matter how you look at it.
Moderator, Senior Ambassador, Experienced player
(907)
Joined: 9/14/2008
Posts: 1014
I really hope someone is able to find the free time to complete the new any% because I think it would be so cool and I'm very excited!
(sonicpacker, you seem to be taking offense when none was likely intended - I think we're all just happy to see something interesting on the horizon and can't contain ourselves.)
I for one will patiently await whatever happens... so it can be console-verified. :)
Is it a case of waiting until you guys are on holiday?
Just wait until they have the time, making frequent posts here won't make it happen any sooner. (I expect it will actually get you less updates in the long run.)
Snark's video digest by star:
Chip off Whomp's Block: Used a misalignment(?) between two falling grey blocks to cut a corner. This allows Mario to take a slightly wider turn before the jump for more horizontal speed during it.
To the Top of the Fortress: Same as Chip off Whomp's Block.
Top O' the Town: Unknown (lag reduction?)
Shocking Arrow Lifts: Replaced the first jump-kick and double jump with a long jump against the fence and a second one onto the fence. This trick lands on the fence sooner.
Vanish Cap red coins: Sliding right away rather than wall-kicking reaches the first red coin sooner but appears to lose some of that before the second; however, it also allows grabbing the second red coin at a better angle to clear the extra life platform, which itself allows approaching the third red coin from a better angle to preserve speed for the jump from the fourth coin onto the wall. A glitched wall kick at the first elevator saves a bit of time, and Mario still has the vanish cap effect to pass through the wall around the star rather than going all the way over it. Every single time saver except the glitched wall kick was dependent on the approach to the first two red coins.
In the Deep Freeze: The initial dive recover came off a downward slope, letting Mario maintain a bit of extra horizontal speed. But it didn't save time.
Behind Chain Chomp's Gate: I couldn't tell exactly what happened, but the frames were saved at some point during the dive up the slope.
Shoot to the Island in the Sky: As with the previous star, I couldn't tell what the improvement was.
Slip Slidin' Away: The time saved is due to a major route change, which should be obvious from watching the video.
Cruiser Crossing the Rainbow: The first jump is delayed to get a better angle on the wall kick. The wall kick is also lower. This allows an earlier jump to Lakitu with more horizontal speed.
Swingin' in the Breeze: The time is saved on the first wall kick, but I can't tell how.
Coins Amassed in a Maze: The time is again saved around the first wall kick, but I can't tell how.
BitFS red coins: All time was saved during the final BLJ's route change.
Bowser 2: Used BLJ momentum to carry Bowser closer to the bomb during the grab animation.
Blast Away the Wall: Major route change; a tree jump let Mario take a more direct route to the star, and a triple jump with a glitched wall kick gave the height necessary to snag it.
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
telnet: Unable to connect to remote host
