TheNoseKnows Posted August 10, 2019 Share Posted August 10, 2019 (edited) Ever since the development version fixed the save file crashing as described here, the track designs of certain wooden roller coasters have become unsaveable. 'Great White Wail', a pre-built coaster from the original RCT2, is one such example. In the save file attached, I've created an identical duplicate using the original template, except I've rebuilt certain track pieces, which are marked with red cubes. This has resulted in the creation of a saveable version of the Great White Wail that is otherwise completely identical to the original. In the save file are also two of my custom rides that I used to be able to save, but which are now unsaveable. It may be that other coaster types are affected, but the only instances I could find were of wooden coasters. I'm running Windows 10 1903, and OpenRCT2 version 0.2.3-60db202. EDIT: The error message I get is the same as the one seen here. EDIT 2: This bug was fixed a while ago, and I'm making a note here just in case anyone gets confused. unsaveable track designs.sv6 Edited October 26, 2019 by TheNoseKnows Link to comment
TheNoseKnows Posted August 11, 2019 Author Share Posted August 11, 2019 It may be that other coaster types are affected, but the only instances I could find were of wooden coasters. The Hypertwister 'Goliath' from Six Flags Magic Mountain is also affected by this bug, along with the two 'Colossus' wooden coasters from the same park. Link to comment
Dubaifreak Posted July 30, 2022 Share Posted July 30, 2022 I know this is a late reply, but, i don't have the problem! 486017945_bandicam2022-07-3021-27-38-431.mp4 2 Link to comment
Dubaifreak Posted August 2, 2022 Share Posted August 2, 2022 I knew this would get a dislike! 😑 Link to comment
X7123M3-256 Posted August 2, 2022 Share Posted August 2, 2022 11 minutes ago, Dubaifreak said: I knew this would get a dislike! 😑 You're responding to a three year old post about a bug that has already been fixed. 1 Link to comment
Dubaifreak Posted August 2, 2022 Share Posted August 2, 2022 2 hours ago, X7123M3-256 said: You're responding to a three year old post about a bug that has already been fixed. Exactly! 😑 Link to comment
Gymnasiast Posted August 4, 2022 Share Posted August 4, 2022 (edited) It’s bad forum etiquette (i.e. rude) to post in topics that are years old. This is called “necroposting”. You said “I knew this would get a dislike! 😑”, which suggests you know it would irritate people, so why did you follow through? Edit: I now locked this topic to avoid piling on more off-topic replies. Edited August 4, 2022 by Gymnasiast 2 Link to comment
Recommended Posts