-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add photo mode to TR2 #2278
Add photo mode to TR2 #2278
Conversation
Download the built assets for this pull request: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great overall 👍
- The camera is too high during starting animations (Rig and HSH). Other in-game cinematics seem OK (dagger pull, shower)
- Should we change the default input to F11 in TR1 to match?
Fixed, but it'll be good to have this thoroughly rechecked.
Oh yeah I forgot to ask about this. I wouldn't touch TR1 TBH, and instead, I'd remap TR2 controls. WDYT? For example something like this:
|
Remapping TR2 inputs as above sounds ideal 👍 |
Updated the bindings. |
Looks great! Just 2 issues to report:
|
07342bd
to
ee06350
Compare
@aredfan both fixed. I might've introduced one-frame-off glitches with the game camera and/or with the cutscenes, though. |
Thank you. 👍 I found a couple of bugs in cutscenes. Cutscene 2 in PR build: |
Thank you @aredfan for the patience – I only tested cutscene 1. Thanks to Lahm's fix it should be fixed now. |
Checklist
Description
Resolves #2277.
The controls UI got bloated – we'll address it later.
I added a couple of ugly
#if TR_VERSION
throughout the photo mode code, but that's because the viewport module APIs are fundamentally different in both games for now.I reduced the flicker when capturing the screenshot to minimum, and added a fade-out effect when exiting the game while in photo mode (TR2 only).