Rework widescreen camera and actor handling - #490
Open
JeodC wants to merge 3 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This will resolve #471. The widescreen camera fix has been reworked entirely and should be easier to modify in the future if needed. A camera tools menu has been added to Dev Tools and assisted with finding the right scales to use. The camera angle adjustments scale cleanly among different aspect ratios on demand.
In addition, transitions now scale properly where previously on wider aspect ratios they did not, which caused them to appear to play slowly. Specific actors in the Rareware Intro and Concert maps are also handled to be hidden until needed. This affects the buzz bombs in the sky with the Rareware logo, and the two bulls and frog in the Concert cutscene.
Additionally, the toggle for it has been commented out since there is zero logical reason anyone would want to disable this feature.