My observations so far: Okay so there's certain unskippable cutscenes that will prompt you if you want to save when Alt-F4-ing to close the game. Usually after placing a Bahos and warping (after the 12-star, the bat, the arrow) or after playing the casette.

When selecting a response, the game will either crash with an error, or exit without error.

It seems this skip only works when it crashes with error (for example after playing the casette tape)

When prompted, choose "Yes" to save the game, then quickly reload. This starts the cutscene animation but skips the sound/content. In particular, you will be able to Map-warp out of the cutscene.

If you do so before the Ghost fades out, the game will crash. If you do so AFTER the ghost fades out, it will not. In particular, the Ghost fadeout time is unrelated to the original dialogue length.

The only cutscene I personally observed this to be feasible is the one after playing the casette tape. Waiting until the end of the cutscene without skipping takes 16-ish seconds, whereas the skip, when executed, takes about 15 seconds.

That might not be much, but further research may lead to something.

I have created safety saves after each Bahos, so the casette skip would be right after the save labelled "12 final"

For all other cutscenes so far, either exiting doesn't crash, or it's faster to just let it play. In particular, the one after "8 Arrows" is very long, but since it has the selection in the middle, I was unable to skip here. I'd encourage to test it yourselves and see what you can come up with. A proper consistent cutscene skip can shave off about 1m30s of the entire run.

Dear Community,

a new submission has been made by @mostly_unrelated in the 100% category, with a record shattering time of 30:39

It does contain glitches at video timestamps 3:22 and 21:40, so congrats on discovering those. Kindly provide a documentation in the Guides section.

The run does not violate any rules, so will be approved after the documentation.

This might be a legitimate reason to split the board though, and I'd like to hear your thoughts.

If the glitches cannot be replicated on every console (that has had runs submitted) the boards must split, as otherwise systems that have the glitch would get an advantage.

The run is labelled as MS-DOS emulator, so I presume that means dosbox.

When the documentation is made, I would kindly ask @MilkToast to test it on Amiga, and @yett2000 to test it on ScummVM Floppy

SRC: https://www.speedrun.com/sam_and_max_hit_the_road

Timing starts on Sam's first movement (best to start the timer JUST BEFORE the first click or the click might not register).

Evidence: https://www.twitch.tv/mikespeedyadventures/clip/BombasticTawdryLeopardGrammarKing-E00in6uiHFDtx35k

SRC: https://www.speedrun.com/ct

Timing is /generally/ from the "A" press at pendulum screen (which starts the game)

Still requires evidence

SRC: https://www.speedrun.com/series/tower

Evidence:

SRC: https://www.speedrun.com/indiana_jones_and_the_last_crusade_graphic

Evidence:

Let me say from the get-go I'm happy to retime all submissions here, both mine and the others, we just need a standard that can be agreed on.

I'll explain all methods at the example of this run:

Method 1: Autosplitter. Probably reliable and consistent, but hacked together by me, also only splits AFTER hitting enter on the "The chapter is finished" prompt, and splits EARLY on chapter select. This is what we usually use for splitting in runs, but would be a disadvantage for people who don't want to use it/ when it breaks. I do NOT recommend this method. Would time the above run to 42.490

All following methods are seen together with the regular starting frame from chapter select.

Method 2: Last frame before the "The chapter is finished" prompt. Unambiguous, always exists, never up to interpretation. I recommend this method. Would time the above run to 40.883. (Thanks to Bernie for the correction from "First frame of" to "Last frame before")

Method 3: Proper Last input: The last input (usually a cutscene skip) before the prompt. Not sure if all chapters end in cutscene, could be ambiguous. I'm not too keen on this method but can get on board with it. Would time the run to 40.867

Method 4: Technical last input: The last input after which only cutscenes are played. This is based on the timing for the end of the game. We split on the last character input. Again, not keen but can get on board. Would retime the run to 40.783

Let me know which of these you prefer and why, or if you have any other. If there's no feedback I'll choose option 2

Hi, I experienced a crash while running the game. Using Bizhawk emulator.

Here's the VOD with timestamp:

Has this happened to anyone else before? Otherwise looking for recommendations of more stable ROM or emulator sources.