Convert flyby camera system to use dynamic allocation with std::vector #4
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.
Checklist
CHANGELOG.mdfile on the branch/fork (if it is an internal change, this is not needed).Links to issue(s) this pull request concerns (if applicable)
N/A
Pull request description
Converts the flyby camera system from using static arrays with a hardcoded limit to dynamic
std::vectorallocation, removing all hardcoded limits on flyby cameras.Changes
TombEngine/Game/spotcam.h:MAX_SPOTCAMSconstant (was 1024)SPOTCAM_MAX_SEQUENCE_IDconstant (256) for sequence number indexingSpotCam,SpotCamRemap, andCameraCntfrom static arrays tostd::vectorTombEngine/Game/spotcam.cpp:std::vectorClearSpotCamSequences()to useclear()methodGetCameraTransform()to useSPOTCAM_MAX_SEQUENCE_IDTombEngine/Specific/level.cpp:SpotCamis sized to actual camera count from level dataSpotCamRemapandCameraCntare sized to 256 and zero-initialized (indexed by sequence number, unsigned char range 0-255)Impact
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.