120 replies to this topic

[Sherlock]

You automatically get 1 d/l per hour as a new member. For every upload, you get an extra d/l per hour, and for every 10 posts you contribute to the community you get another d/l per hour. (Some forums don't increase your post count).

So d/l per hour = 1+ uploads + int(posts/10).

I appreciate that this may mean that it takes a long time to download a lot of rides, but:

• we have very powerful search features that you can use to find just what you're looking for
• we don't have this limit on RCT1 rides, and many of them work with RCT2
• we have hundreds of RCT1 rides available in a single download at http://www.rct2.com/...?...=file&id=31 where there are no restrictions on d/l per hour. Thw rides available in that download can be seen at http://www.rct2.com/.....20Read Me.htm

Is this different for the Steve Franks Track Packs? I still get only 1 per hour for those (have not yet tried the ridex since uploading) even though I have uploaded 5 tracks.

[rcthelp]

No, SFTP is based on posts only.

[Nobak]

I don't know how much this is still being supported or what, since there probably aren't many people still playing RCT2, but I guess it won't hurt to report it...

I tried uploading a maze and received a message that it matches another one in the database (Micro Maze). So I downloaded that and it doesn't match at all. Micro Maze is two cells with an entrance and exit, while my layout looked like this:



I've managed a successful upload on another ride (not a maze) before that one, FWIW.

[rcthelp]

Sent you a PM about this.

[Woodpecker]

The ridex stats on my newly-uploaded coaster, 'Shockwave 2', are wrong.

The ridex stats:

Max speed: 52 mph
Average speed: 20mph
Negative vertical g's: -1.28
Lateral g's: 1.92
Max ride height (feet): 74
Max drop height (feet): 37
Length (feet): 4393

The REAL stats:

Max speed: 53 mph
Average speed: 21 mph
Negative vertical g's: -1.22
Lateral g's: 2.12
Max ride height (feet): 85
Max drop height (feet): 82
Length (feet): 4,396

---------

Note that the real stats are taken from within the game when I was testing it - no peeps were on board. These were also the stats registered when I saved the track, so why is there such a huge discrepancy with the ridex results?

EDIT: I've just read the notes on the ride exchange, which say there may be rounding/truncating errors... even so, from 82 to 37 feet seems a little excessive.

Edited by Woodpecker, 23 April 2009 - 04:45 PM.

[rcthelp]

Not helped by the fact that I cannot download it to test, and just get the zip file as a web page instead. Anybody else having this problem?

[rcthelp]

OK, there are 3 parts to this:

• The maximum drop height is CONFIRMED as a bug. The actual maximum drop height is approximately 2.5 times more than we are displaying, for every single RCT2 ride in the Exchange.
• The maximum ride height is being calculated by us, it isn't calculated by the game. I *think* [99.5% certain] that this is being calculated correctly, but then converted incorrectly, for the same reasons as item 1 above.
• In investigating this bug report, I have discovered that every ride uploaded since we moved servers on March 22nd this year, does not download properly.

The first 2 above are already fixed, it's amazing that this has never been either reported or picked up by me before, in the 5+ years that the Exchange has been open.

However, the 3rd item is a problem that needs further investigation, and I have closed the Ride Exchange until I have found, debugged and fixed it.

[Woodpecker]

Thanks for all your hard work sorting this out.

Edited by Woodpecker, 23 April 2009 - 10:47 PM.

[rcthelp]

OK, the bug reported [and the download bug found as a result] are now fixed and the Ridex is reopened as v2.17.

You will see that the Ridex now calculates ride height and drop height as 84 feet for your ride.

[beginner2]

There's a problem. I attempted to download a few coasters recently, one that was uploaded yesterday (Thriller) and the one right under it, for RCT2. It downloads successfully as a zip, but both zips were corrupted, and, to be sure that they weren't renamed, not RCT2 track files renamed. I have also tested with some other tracks from further down the list, and the problem persists. Is this a bug, or just bad uploading?