This topic is for the purpose of discussing #6839: KietTezend's PSX Lucifer Ring in 21:28.27

>Movie begins from save state I don't know how you did this since you showed that you did it correctly before. Was it not odd to you that you didn't see the PlayStation bios sequence? I do want to recover this input. However, from just the first stage alone there are issues with your movement as you ran into a wall followed by jimmying out. This TAS is basically superhuman play with loads used sparingly. Abstained Vote. It has 1854 frames of blank input at the end, probably more due to the fact the author mashed their input. It'd be nice to see them respond to the comments laid out here for them. I'm gonna repeat myself again.

Please, go back to the drawing board and take your time with the next movie you create for this game. In a TAS world this can be easily improved on. And upload your movies to your user movies area until you're confident that it's optimal.

Yeah I didn't have to look into it hard. Your Input: My Input: Quick Comparison

Very good game choice! Looking forward to an improvement.

Greetings KietTezend's I want to point out a few things, which have been mentioned in this thread so far. For one, not seeing the bios start up sequence is a good indication that something could be carried over from a previous session that gives an advantage to the game play that wasn't demonstrated by a previous movie. Using a savestate properly can open up possibilities that can boost the performance of your movie; however, if a "Verification Run" is not supplied, unfair advantages can exist that do not represent the game's true capabilities. This would be necessary in order to prove that any savestate hasn't been altered by exterior tools, other than what the game produced. Apparently, this is not your intention...but just a note as to why your movie must have a clean start. Please see movie rules in regards to this scenario. http://tasvideos.org/MovieRules.html#WeDoNotAllowSaveAnchoredMovies I am not familiar with this game, but Spikestuff has mentioned obvious flaws. Movement optimization is the highest priority of a submission. If a movie can be easily beaten by members of this site, judgement will be passed unfavorably to your efforts. One item that doesn't sell well for you submission is the low re-record count (1103). A normal amount of effort would show around 25% to 50% for the most common type of work produced. In rare occasions, re-records can exceed the movie length and beyond. I don't wish to discourage you, but this is the trend of new TASers. I can only encourage you to take the time necessary to prove that you have exhausted your knowledge of the game...to the point that your experimentation can show if alternate inputs can make changes for the best. One good point though, is that you have chosen a very good game to TAS. It would be great to see how far this can game can go, in terms of time. As it stands, this movie should be rejected for use of a savestate as a starting point. If it is possible to recover these inputs, as Spikestuff is hopeful of, then the next step is analyzing it for optimization...which apparently doesn't hold with the expectation of this community.[/url]

A normal amount of effort would show around 25% to 50% for the most common type of work produced.

I know that you mean 25% to 50% of total frame count, and you know that you mean that, but when explaining this to new people, it helps to be explicit. :)

A normal amount of effort would show around 25% to 50% for the most common type of work produced.

I know that you mean 25% to 50% of total frame count, and you know that you mean that, but when explaining this to new people, it helps to be explicit. :)

Oops. :)

om, nom, nom... minty!