Skip to content
View in the app

A better way to browse. Learn more.

Kings Island Central Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

pkiknex25

Members
  • Joined

  • Last visited

Everything posted by pkiknex25

  1. pkiknex25 replied to fryoj's topic in Kings Island
    Some of the zoomed in, detailed blueprints of the station and queue area show 8 lines and gates in the loading station. EDIT: Credit to @Banding Banshee
  2. pkiknex25 replied to fryoj's topic in Kings Island
    I've always gone by a qualifying height OR drop length for determining hypers, especially when a drop reaches the threshold. I don't see why we shouldn't be calling our coaster with a 301 ft drop a giga. Granted, I also thought that this method was the norm, but who knows.
  3. pkiknex25 replied to fryoj's topic in Kings Island
    It's gonna be 4 seats across per row with 8 rows per train, just like Fury 325.
  4. pkiknex25 replied to fryoj's topic in Kings Island
    I did that went the first blueprints of the foundations were found. The track in the lot for Project MCT matched perfectly with the footer labels, and still match perfectly today. Project MCT is our coaster.
  5. pkiknex25 replied to fryoj's topic in Kings Island
    122 normal pieces (including turn between brake run and transfer) + 1 transfer + 9 brakes/station + 16 lift/drop pieces = 148. You are right. Certainly not a bad way to guesstimate a track length. Thanks. Where'd you find Fury's 192?
  6. pkiknex25 replied to fryoj's topic in Kings Island
    You nailed it. This is not gonna be DB2.0. And thanks for making and sharing those pictures, because it just saved me some work. I wanted to share my thoughts on some of the elements on this coaster. I think before with the blurry overview, there was a misconception on what elements would be, and unfortunately, those seem to have stuck with the public. So, I want to give my opinion after seeing these detailed prints. Picture 1: This is not a reverse treble clef. The top point is not on a straight section like it is on Fury, and there's no large gap between banking and turning. I think this turnaround is going to be a non-inverting cross of an overbank and a dive loop. If you can imagine what a normal dive loop would look like from an above view like this, the high point would be very similar to what we see on our blueprint. An element like this would also explain why, from a top view, the turn would appear to get sharper as it decreases in altitude (assumption based on moving away from an early high point). It's not taking a sharp turn, but a steep downward turn. Picture 2: Now this looks really similar to the banked floating hill of Fury's treble cleft. While lacking the full turnaround that helped give Fury's element its name, this will still give us that amazing sideways airtime it's known for. Picture 3: I don't think this will be the ampersand we see on Shambhala. It actually looks really similar to the helix on Apollo's Chariot. We have the entrance low point (745 ft) at the very start of the turn, and it seems that the curve is getting consistently tighter until we hit the top point (854 ft) nearly 360 degrees later. We then quickly drop while turning 135 degrees where we hit the bottom (747.5 ft) after leveling and straightening out. Now at 110 feet from low to high, I can see a little bit of ampersand influence, but if this were to be more like Shambhala's, I'd have expected to see the high point be closer to the middle of the helix. I expect something closer to Apollo's helix. Of course, I'd love to hear everyone's thoughts on this as well. That's the point of discussion afterall.
  7. pkiknex25 replied to fryoj's topic in Kings Island
    Top of lift is 1035.9, not 1065.9.
  8. pkiknex25 replied to fryoj's topic in Kings Island
    It's expensive clearing wooded land, and it's more expensive doing so on rugged terrain. Based on the earlier discussions when we just had the clearing, it seems that KI picked the best topography to work with for this coaster, and has no qualms about leaving the rest undeveloped.
  9. pkiknex25 replied to fryoj's topic in Kings Island
    You're looking at "Bottom #6", which is after the ampersand/helix. Bottom #1 is the bottom of the main drop.
  10. pkiknex25 replied to fryoj's topic in Kings Island
    With the amount of brown track pieces visible, I would guess that Candemonium is at or near completed production. Although until Hershey track starts shipping, I think it'll be difficult to track progress on MCT. @Logan: Yes, the only MCT track we've seen so far are for the brakes, a flat turn, transfer, and station. The track labeled MCT ST9 is the entirety of our station, going into the lift.
  11. pkiknex25 replied to fryoj's topic in Kings Island
    This. 100%. And remember that this was pulled straight from the Mason Municipal Building, so we know it's legit.
  12. pkiknex25 replied to fryoj's topic in Kings Island
    https://drive.google.com/file/d/1h6qKpT4jW4JwgNh9uXq4dD39iLwbyAmJ/view Provided by @Bansheeback, who got copies of the available plans at Mason Municipal Building and scanned them in for us.
  13. pkiknex25 replied to fryoj's topic in Kings Island
    The 4 across cars handle transitions and curves better because of the shorter length of each car. And I would guess the shorter train length benefits the design as well.
  14. pkiknex25 replied to fryoj's topic in Kings Island
    Fixed it for ya. Red cross through the wrong ones, and the orange ones were missed.
  15. pkiknex25 replied to fryoj's topic in Kings Island
    B&M isn't doing anything different. The distance may be wider between them, but it's not different.
  16. pkiknex25 replied to fryoj's topic in Kings Island
    ST1 and ST2 should be the initial flat elevated brake run, seen on both Fury and Leviathan. ST3 curves down into a downward slope, as also seen. Now there are no footer labels for ST3 as there are no supports for ST3, likely unnecessary because it's a shorter track piece. ST2 has a set of supports and ST4 has 2 sets, so it'll be well supported. There's no error there.
  17. pkiknex25 replied to fryoj's topic in Kings Island
    To me, it looks like the Firehawk queue isn't being used at all. I see the big red section between the brake run and the station as a new large queue for the coaster. It looks like a gift shop will be in the old Firehawk queue area.
  18. pkiknex25 replied to fryoj's topic in Kings Island
    Thanks again Liz! One thing I'd like to point out is that on Fury and Leviathan, the supports equivalent to L8R and L8L are positioned still well on the lift portion and a good bit before the crest. What if we used the center point of a line between L13L and L13R as an estimate for the crest?
  19. pkiknex25 replied to fryoj's topic in Kings Island
    Here is the photo he used.
  20. pkiknex25 replied to fryoj's topic in Kings Island
    Except he used information on the coordinate sheet to prove that the actual scale of the drawing is off from the provided scale by a factor of exactly 2. His logic and process is sound.
  21. pkiknex25 replied to fryoj's topic in Kings Island
    Nobody has it. The original poster quickly deleted it, Ben23065 at least saw it, and codyfryguy had it saved but deleted before PMing anyone. Unless a mod reverts the original post to reveal it (snowball's chance in hell), it's gone.
  22. pkiknex25 replied to fryoj's topic in Kings Island
    Disappointed, but understood and respected.
  23. pkiknex25 replied to fryoj's topic in Kings Island
    Thread is moving quickly, so I'll quote myself.
  24. pkiknex25 replied to fryoj's topic in Kings Island
    Still giga. Nothing accurate to say it's not.
  25. pkiknex25 replied to fryoj's topic in Kings Island
    The last 3 sets of footers and the dotted lines for the supports are the drop, and are an identical set up to Fury and similar to Leviathan (Dragon Fire likely influenced it's design).
Background Picker

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.