Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,71 @@
},
"images": [
{ "path": "preview.png", "x": 1, "y": 1 },
"$RCT2:OBJDATA/FUTRPAT2.DAT[73..164]"
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"$RCT2:OBJDATA/FUTRPATH.DAT[101..128]",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I understand correctly, this consists of 1) the ride banner, and 2) the supports? (at least the bits directly under the path)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Images 73 to 100 are the railings, images 101 to 108 are for the queue line banner, one invisible image on 109, images 110 to 128 are the path underlay/platforms (the bits directly under the path you spoke of). Then lastly images 129 to 164 are the support beams.

FUTRPAT2 has blank images for images 73 to 100 (railings) and 129 to 164 (support beams), so this PR just replicates that with our own method of having blank images.

If you want to check for yourself to be sure, i'd recommend exporting the sprites of both FUTRPATH.DAT & FUTRPAT2.DAT and inspecting their images for yourself.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I trust you on this one, especially with this breakdown you provided.

"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
""
],
"strings": {
"name": {
Expand Down
Loading