PINK: Handle animations with non standard start frame #4942
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are a few animations with start frame greater than 0 and also greater than (or equal to) framecount
It seems that for such animations, the decoder is supposed to start at 0 and play framecount number of frames. So for these cases we deduct a _startFrame ammount before sending them to decoder. This addresses crash bug #14438 PINK: Crash in Egypt when using the digger on the characters for Passport to Peril
This was tested for Passport to Peril US English version. I am uncertain about potential side-effects on Hocus Pocus.