5 replies to this topic

[rcthelp]

I am trying to save a track design to include the queue that was built, and some other scenery. There are 2 weird things going on.

• Even though I design and test it in the Rollercoaster Designer, and build it at ground level, it absolutely refuses to go in any park at ground level. It's always 5 feet above, on supports.
• Then in a park, where I place it, then build the entrance and exit, some footpaths and queue tiles, and a few other pieces of scenery, and save it with the scenery, 2 more things happen
  • In the preview mode, the game doesn't show a picture of what it will look like. I don't mean that it shows the ride with some red text about the scenery not being available, I mean no picture at all!
  • When I do place it in the park, the footpaths are 5 feet too low, so placing the entrance and exits back where they were, they don't join up with the paths!

Has anybody else ever seen anything like this?

[Doctor J]

Is it only one track that has the problem? Or is it a recurring issue?

[rcthelp]

I've only seen it happen with one ride Doctor J, but I do not use the Designer often. I describe a test case at OpenRCT2 in the hope that it may be fixed by that project. You can download a copy of the ride saved with scenery (called Spin Drier) in our Ride Exchange

[Doctor J]

I should have tested things before hitting the keyboard

I got similar results including variants that were higher off the ground on attempt to build after saving. One of them would only show the footprint and attempting to build would give the message: "cannot build that here, too high for supports."

 

Anyway, the bug is triggered if the terminus of the reverse portion of a powered launch looping coaster is a sloped curve. You can add a single straight piece at the end of the helix and your ride will be "normal".

[rcthelp]

Anyway, the bug is triggered if the terminus of the reverse portion of a powered launch looping coaster is a sloped curve. You can add a single straight piece at the end of the helix and your ride will be "normal".

 

Has that bug be known about for some time, or did you just find it based on this test case?

 

I've uploaded a debug version of my ride to the Ride Exchange. Thank You! 

[Doctor J]

I had not heard of this bug before. I tried some variations of your track and noticed a pattern that curved pieces (in the reverse part of the track) had the bug while purely straight pieces did not. Further testing revealed that it only mattered if the terminal piece was a sloped curve. I suspect it involves the code that interprets a track file and determines it's 3D space requirement.