OtakuTAS, can you explain how you are calculating the percentage completion for this TAS? I can't see how 110% is derived. At this point, I am closer to thinking this should be classified a "Glitched" run instead.
It was moreso a word for just going "overboard" rather than actually being accurate.
If you can think of something to accurately reflect the glitched level but also reflecting accessing level 4, that would be cool. Whatever works.
From what I've read this is the first time a person has accessed level 4 through normal gameplay.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Looks pretty good! Giving it a yes. I tried doing this 2.5 years ago but gave up and lost interest. Glad to see somebody else got around to it.
I wonder if you can save same frames bonking on Bow-Wow but looking at the time you waited at the chest, maybe not. idk
I noticed you didn't do the post-game scene, so I did it for you. You do not have to credit me for input since it's literally just alternate A and B every frame. Contact a judge to have the submission file replaced.
Luckily this doesn't affect the encode since the gameplay is unchanged
User movie #638270575743921578
They will usually set that up for the encode to let the viewers see but for timing purposes and the site's files, you just need to get to that screen instead. There was a ruling on it a while back. Which would suck without it because it's long! Thanks for your nice comments!
I got curious and checked, 64 (last possible frame of the last possible hex digit I could activate the chest if I could magically get there) is 606 frames away, potentially more if it only works NOT at the end (buffer).
I triple checked and spent a good hour or two polishing the run to be frame perfect (not knowing where I would end up and not necessarily caring because it would be firm), for style, thankfully when I checked at the end I ended up on 6A/6D. If I was like a frame away from a good number, thankfully I was closer to the future numbers than the past, otherwise I'd be going over it like crazy. Even moreso if that was the last good number in the row of few, imagine that! There's a few runs out there when they're like a frame away from a huge break but can never reach it, thankfully it was the other way around, where the waiting wasn't long, and the possibility for an earlier number is impossible. Unless a huge glitch is discovered, but this has been it for 4 years.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
dwango, I would like to apologize for my tone in the earlier posts now that this has bumped up again. I was shocked to read my own comments and the tone they were written in.
Unfortunately I was in a very bad place from February to April in life, and it clearly also affected my attitude on the site. Apologies. I do think this should be accepted, hopefully (again) without major site changes.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Running 2.9.1 and still getting it opening the zip file trying to get me to choose a file (not how arcade games work) even when starting through "Open advanced..."
Does it on a few different games but right now I'm trying superman.zip.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Call me a party pooper if you want, but I think this submission should be console-verified to make absolutely sure that being able to access Level 4 in this case isn't due to an emulation error...
I agree, although the majority of people have played this game on emulator compared to console, and I've never seen it go to level 4. I haven't yet worked on my normal TAS for this game, so I haven't confirmed that for some reason BizHawk just does it, but I doubt it.
I think it's pretty simple, I believe playing the second level twice (or is it the first) increases the level counter in a way that allows for the 4th level to play. Definitely worth checking out though. Unfortunately RNG is so dumb in this game that it's not as simple as splicing out the two deaths and the glitched area. A casual playthrough would suffice, on BizHawk 2.9.0 which is the emulator used.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
383 frames saved:
https://tasvideos.org/UserFiles/Info/638268067837152127
Level 1 is now impossible to be faster. Had a little less work cut out for me as you actually can't kill the blue guys. So I had to jump over them anyways. Nonetheless, the changes allowed to both minimize jumping to the minimum to save a few frames, and more importantly also removed the only moment in the run where I needed to let go of a control/stall. Now I'm holding right for the entire level so it's impossible to be faster. The only thing movable in this run for this level would be the jumping, but that's kept to the absolute minimum. It doesn't change your run speed, but again, it causes a frame of delay in the... err... "engine".
These changes rearranged the RNG for the rest of the run so I ended up having to redo most of it in quick time. Turns out the enemy selection is just "throw a ton of enemies on the screen in this random RNG pattern and see what happens".
Level 3 I was able to mostly reuse the same movement inputs, since ironically shooting doesn't slow you down, so I basically just was doing an on-rails-shooter of rearranging shot inputs to match the new RNG while keeping the same exact movement.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Realized jumping delays the game by a frame and another timesave in level 1.
Level 1 is currently being redone with shooting enemies instead of jumping over. However, this affected the results of the glitched level likely due to memory differences. Decided to continue submission and check within my 72 hour window if the glitch is still possible (likely is).
Also not sure if I selected the wrong branch or what (hot mess TASer tonight), but you can drive the car faster into the pillars (but not too fast or you go through them LOL) to kill yourself faster.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Can anyone make a livestream of this TAS? 16K encodes take too long to process. 1gbps makes too big of a file. (7.50 GB for 1 minute of video cannot fit on a VCD)
What? Just encode it like everybody else does in BizHawk. Takes a minute or less to upload.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Honestly, I would hope anybody doing a glitchless run would be doing it just as much to suit the category as it is to be fast.
Seems like there's a few people in here so hellbent on being as fast as they can, that they would be willing to skirt the idea of the rules for this category, and to say that I'd say stick to standard runs.
Perhaps I'm the only one thinking this way, but I would find a certain pride in specifically trying to avoid all glitches for this sort of thing, just as I take pride in FINDING glitches in glitched runs. "How fast can I push the boundaries of this game without breaking it?" As in, even doing a single glitch would feel like a total bummer to me, because you're doing it for a reason and that reason certainly isn't to be faster that record. So you're either playing incredibly slow, or playing a little less incredibly slow, by using a glitch or two. Using glitches in a glitchless run, even one or two, would just kill the whole idea and mood for me.
Not sure what else you'd get out of it besides the pride of not using any glitches. It's not like you're settings any records with the speed. It's not like you're showing off any cool stuff. Really the only thing the category has is the genuine faithfulness of living up to it's name, and if that isn't there, I really don't see a point of having it at all. Then it's just an unoptimized bastard child of a standard TAS.
Plus it's a slippery slope. Judges let one glitch go, then suddenly it's five. Then ten.
Oh, and this is just discussing acceptance of a submitted run. This is going to be a dumpster fire when it's a submission that wants to obsolete somebody else's run, if any sort of glitches are involved. That's going to be one hell of a thread.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Here's some concrete examples of games I am interested in:
1. Tiny Toon Adventures 2: Montana's Movie Madness (there's a single clipping bug used in 1 room, but old VBA so that needs resync)
2. Bishoujo Senshi Sailor Moon R (a single clipping bug in stage 2)
3. Nanashi no Geemu (A single npc bypass in stage 3, but it is in desmume, so bleg)
4. Sabre Wulf (a single npc despawn bug iirc)
5. Jenga world tour (a single stage where the blocks spontanously all fell, but it got rejected for being a board game)
6. Yuu Yuu Hakusho: Makai no Tobira (I'm not sure if the current route of making the bosses in place counts as bug, but if so then just change the fights I guess so they actually move around)
I am mainly concerned for 5 and 6. If you can, please answer do those count as bugs.
I don't have enough info on 5-6, but I would sure hope 1-4 would rule out any sliver of involvement in a "glitchless" category.
I don't see the point in having the category unless it's seriously glitchless.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
That already exists as a lua, under movieclock.lua or something along those lines. Although no “stopwatch” feature exists for it where you can make it split or stop.
Oh cool. Thanks.
I'll have to try it out. Would still be cool to see it hardcoded in, but just a suggestion.
I mostly just meant the stopwatch thing for counting up, as long as it follows the frame counter no matter what (jumping around in TAStudio) that's great.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Would love if we could get a stopwatch-style timer (counts up) toggleable under the "View" tab, that would display in the GUI alongside of the frame counter, lag counter, and re-record counter.
Probably easy enough to add in from pressing play, but I suppose with the tracking back and forth it would need to calculate the frames alongside of the frames per second for that specific console for jumping around in TAStudio. Sometimes after hours of work I'd like to see how far in the game I actually am in "real-time". I guess it some ways it would also make comparing branches a tad easier, although the frame counter serves that purpose better, so I'm mostly just interested in it for the comparison to RTA.
Thanks for all you do BizHawk team.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
You are literally killing it with all these C64 TASes.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Okay, I checked my TAS [5267] GBC Barbie: Magic Genie Adventure "Activity Mode, Genie Master" by OtakuTAS in 02:28.50 and was able to determine the Field Of Flowers movement is ON the 9th frame (so 8 frames inbetween).
I think I was thrown off in this TAS because PinkyNoice must have mashed inputs throughout, so I thought instant turns were possible, they are not. It had been a few months and I was very tired.
I think I've worked on this as much as I want to at present. I thought it was a few easy fixes but there's a lot of movement stuff, and I especially don't want to do anything until ThunderAxe31 combs over it because right now it feels like new stuff is still popping up that PinkyNoice TASed and I either didn't view, or just glanced over.
This is one of those TASes where just going in from scratch would be easier and require less time than it would be to patch up much more of this.
The field of flowers instaturn thing is just a thing i didnt know about till you told me, always though it was in a rhythm, that also includes the fact that a faster pegasus is possible and a weird movement thing where bumping the walls is slower. I dont think the previous tas was that unfixable that starting anew would be better.
There isn't an instaturn but rather just confusion because there was way too many inputs, it all fixed up now
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Glad to see this was accepted. Sounds like you fixed the dark room error I mentioned as well. I was going to suggest a LUA script to light up the room too, or just a locked memory value instead.
Apparently there's a separate encode with the room lit up but honestly not sure if it's intriguing enough to post... the darkness is cool. (Obviously it would be seperate)
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Okay, I checked my TAS [5267] GBC Barbie: Magic Genie Adventure "Activity Mode, Genie Master" by OtakuTAS in 02:28.50 and was able to determine the Field Of Flowers movement is ON the 9th frame (so 8 frames inbetween).
I think I was thrown off in this TAS because PinkyNoice must have mashed inputs throughout, so I thought instant turns were possible, they are not. It had been a few months and I was very tired.
I think I've worked on this as much as I want to at present. I thought it was a few easy fixes but there's a lot of movement stuff, and I especially don't want to do anything until ThunderAxe31 combs over it because right now it feels like new stuff is still popping up that PinkyNoice TASed and I either didn't view, or just glanced over.
This is one of those TASes where just going in from scratch would be easier and require less time than it would be to patch up much more of this.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
The A press is not the only problem, the other problem is he kept moving right during this error, so the positioning creates an ever bigger disadvantage than the A press being late. More frames are lost on movement than the simple 2 frame error. I let Pinky and Retro know on Discord
OtakuTAS wrote:
B) In the "dark room" the NPC is activated 2 frames late with an "A" push
C) In the "dark room" the NPC is then overshot by those 2 frames in the wrong direction, losing 4+ frames and more momentum (two frames right prior to speaking, two frames left post speaking to compensate back) of movement. Compensating for this causes it to desync, game has pretty simple movements so it's an easy fix and doesn't have to be precise whatsoever but I can't see with the damn lights off! Lol just kidding, but I just didn't have time at the moment to finish it up
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Whoever does that should also fix the 4+ frame loss in the dark room as I haven't gotten to that yet. See the details in one of my previous posts
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
You are correct, Pinky needed to go left sooner. It's going to be a busy couple of days for me, so I can't get to it as you have to redo/resync the rest of the level. Maybe Retro or PinkyNoice can.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
Had a nice long conversation with Pinky on the Barbie speedruns discord and it turns out the credits show up idling on the title screen. Lol.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
The longplay additional does not feature credits: https://www.youtube.com/watch?v=iO9p51dl7KA
I sent an e-mail to the guy who uploaded the video, let's see if he responds.
I'm wondering if it's a cheat code or was never in the final game and accessed via memory hacking/GameShark.
Published TASes: #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12Please consider voting for me as Rookie TASer Of 2023 - Voting is in December 2023My rule is quality TASes over quantity TASes... unless I'm bored.
