lara: add responsive jumping

[lahm86]

Resolves #157.

Checklist

• I have read the coding conventions
• I have added a changelog entry about what my pull request accomplishes, or it is an internal change

Description

The new injection file here will amend the relevant anim range low/high frames as detailed in the issue. It wasn't possible to combine this with the lara_animations.bin file as that is always injected, whereas this one needs to be tied to the config option.

Demo: https://www.youtube.com/watch?v=mqi9EDz0FYU

A bit more detail on the jump lock workings. It's effectively to allow animation 0 to behave differently the first time compared to subsequent times during continuous running jumps.

1. Lara wants to run so enters animation 6 (RUN_START)
2. The game sets a lock saying jumping is not allowed
3. Animation 6 completes and moves to animation 0 (RUN)
4. Lara wants to jump immediately
   • The jump lock is still in force, so frames 0, 1, 2, 3 play out as normal
   • Frame 4 is reached, the jump lock is lifted
   • Lara can jump from her left foot if frame < 11
   • Lara can jump from her right foot if frame >= 11
5. The jump animation completes and she (via a few other interim animations) returns to animation 0 (RUN) frame 1
6. The jump lock is lifted this time around, so she is free to jump on any frame
7. Lara stops, or grabs a ledge, or anything else
8. She wants to run again, GOTO 1

[walkawayy]

Just a style comment from me.

[lahm86]

I just realised that this broke the Lost Valley demo - Lara ends up not leaving the pool. I've gone for the same approach as disabling enable_enhanced_look temporarily while in the demo.

[rr-]

I believe this boolean logic can be simplified, I'll follow up tomorrow

[rr-]

Would this work?

    if (g_Config.enable_tr2_jumping) {
        int16_t anim = item->anim_number - g_Objects[item->object_number].anim_index;
        if (anim == LA_RUN_START) {
            m_JumpPermitted = false;
        } else if (anim != LA_RUN || item->frame_number == LF_JUMP_READY) {
            m_JumpPermitted = true;
        }
    }

[lahm86]

That looks much better - I'll test it out tomorrow. Thanks.

[rr-]

An ideal outcome would be to forgo introducing a new global variable and set it always in the local scope. But I don't think that's possible since frame number resets to 0 and cycles, so even comparing it with >= will work in an unintended way.

[lahm86]

Yes, it is a shame but thankfully this is a short snippet of code now so looks much tidier. I've tested it out and all is good 👍

[lahm86]

Sorry, just remembered to rebase following #867 (for the changelog).

[walkawayy]

LGTM