This topic is for the purpose of discussing #5596: DrD2k9's C64 Donkey Kong (Atarisoft) in 02:55.74

Can you maybe do encodes? I can't encode all your submissions just to let people post, since, you know, they aren't watching in emulators these days.

I agree feos, because honestly, it's a problem, I must boot on win10 or 8 to watch, then than I work on fedora & than BIZHAWK don't run on this boot! I think it's easy to encode C64 video and add this with your submissions, indeed it's short and don't very heavy file. I don't request you to make the best video encode, but just do it for can easy watching, please.

I've never looked into encoding. I'll read up on it and see what i can do.

Temp Encode Link to video I also edited the submission post to have the temp encode instead of a screenshot.

I don't know how I feel about speed/entertainment trade-offs in general, specially when they are applied in a game which isn't very entertaining anyway. I personally would prefer this to be as fast as possible. As this game is kinda slow, voting meh.

Isn't it possible to avoid waiting for the last barrel through RNG manipulation here? Also, voting No because the average-looking performance does not compensate for this bad port.

Incomplete. Look for the game loop, don't just prematurely end it at the end of the conveyor level.

I agree Spikestuff. You start a new game loop, then you stop prematurely, because next levels are an copie of the first levels! But you haven't finish the game in this case. And I think it's not optimized at the maximum, I'm sure than you have possibility to manipulate "RNG" for don't wait to climb, & in the level where DK fall, isn't it possible to won time with this solution? Vote no, for the first reason that you don't finish this run.

I was gonna say it was probably vault material, until I realized the run wasn't even complete. Voting no.

in the level where DK fall, isn't it possible to won time with this solution?

I think this route is slower, because it was slower in the atari port, and this version of the games doesn't change the distances between the stairs in a way to justify it being faster here.

I think this route is slower, because it was slower in the atari port, and this version of the games doesn't change the distances between the stairs in a way to justify it being faster here.

ok, Thank for this answer, because, I watched "DK NES" and i had to be ask, because i had a doubt!

Why is this played at PAL speed? It's really slow and more boring this way, plus NTSC is the speed it was designed for.

Due to the concerns of this run being incomplete due to not finishing the level loop, I'm going to cancel this submission. I will likely revisit this game in the future (even if it isn't the most entertaining watch). Unfortunately many C64 games aren't very exciting to watch, but I feel that the system still deserves some TAS runs even if they are only vault worthy. The C64 is part of video gaming history and deserves it's space on this site if only for history's sake. As far as the PAL vs. NTSC situation. I didn't realize my BizHawk settings were for PAL instead of NTSC. That being the case, I'm going to have to revisit all of my Commodore 64 submissions as they've all been done with default settings...which means that they are all likely in PAL and may be faster if converted to NTSC. Ugh. Now I have a ton of unexpected work to do.

Isn't it possible to avoid waiting for the last barrel through RNG manipulation here?

I cannot deduce the RNG well enough to manipulate it. I can't figure out anything regarding the barrels or conveyors. I believe the spawn point and movement of fireball enemies is impacted to some degree by your position on the screen, but subtle movements don't seem to have much impact. I can't get breakpoints to work in the debugger. So attempting to reverse engineer the RNG is currently not an option. This leaves trial & error as the only option (at least for me--someone else may have other ideas/skills that I'm not aware of).