Full comparison (Ex. screen on GG has a Sega logo so cropped that out for fair comparison, GG takes a LOSS there(!!!!!)) Link to video examples of time saves (few, not all). you can see the game is the exact same i jump past boulder, he waits for it Link to video (spikes look slower but we just start and stop crouching at different times but the same amount of frames crouching, as seen the level ends sooner on mine despite spike illusion) Link to video moving back and forth saves a significant amount of frames Link to video

jumping for the sword saves time and i kill himfaster Link to video

Saved 64 frames in the cave level by doing most things sooner: User movie #638177837869179697 There are maybe other ways to tighten that level up, and probably other levels too. We don't use rerecord count as argument in our judgments, but so far it does indeed feel like 3607 rerecords in 9.5 minutes is all that went into this submission (my rough test is already at 5k).

Well, 4 levels of the game are autoscrollers I did by hand in real time using maybe... 5... re-records, so it's probably not too off base. Other than that it's what 2, 3 minutes? I'd assume appending to a file would add to the count quite a bit rather than anew. You say you did things "sooner", what exactly does that mean? 64 frames is definitely a big time save for a run I spent perfecting every jump, etc., so I'm curious where the slip-up is and if it's a single incident or a widespread problem. I did every jump, slide, stairs down, stairs up, frame perfect... and there isn't much else to the game. What exactly did you change so I can look into it? 5k for a single level that you're not even TASing and just error checking is pretty hardcore. (Is that including my 3,700?) I'll see if I can spot your changes when I get a chance.

and probably other levels too.

Boss fight is as tight as it gets, the rest are autoscrollers, which leaves the palace level. You're welcome to double check it. At the beginning of the palace I went back and added a timesave to the cave, which ended up causing a desync that required a lot of patching. I assume that is likely the source of any deficiency, if you found it to be "most things". I'll see what my time was at pre-adjustment.

Also wondering if something you did early on saved a lot of lag or altered the pattern of the lag frames in a large way, 64 frames is a lot and especially if it was widespread as you insist, that is very odd and obviously would be extremely noticeable to myself and others

I checked the palace too and couldn't find any easy improvements. Not sure myself what's the deal with the caves, maybe lag alignment played a role. You'd have to make a table of actions and their frames to see how long each of them takes in your and my version. There were several places where running was available quicker, and then I was able to dodge a boulder at 8235 instead of waiting for it. My guess about later levels was probably wrong, but when judging improvements it's usually either clear from using the same setup as the old movie (same emulator, game version, mode, options), or if it's on a different setup, the new run looks clearly superior by comparing gameplay, or a whole bunch of improvements is listed, and it isn't easily improvable itself. Subjectively, a version with a smaller screen is inferior, so I'm unsure why it was chosen. I'm not saying this movie isn't acceptable, I just mean it's unclear how to approach this. Maybe it's already fine as is, then I'd just need some opinions.

This movie has been published. The posts before this message apply to the submission, and posts after this message apply to the published movie. ---- [5241] GG Aladdin by OtakuTAS in 09:32.12