Shows how much I know then!
-
Welcome to the WDWMAGIC.COM Forums!
Please take a look around, and feel free to sign up and join the community.
DHS Star Wars: Rise of the Resistance
- Thread starter The Grand Inquisitor
- Start date
180º
Well-Known Member
Shows how much I know then!
MartinsVidsDotNet
www.youtube.com
Just hours upon hours upon hours worth of nothing? You mean to tell me I could have been watching vines and cat videos this whole time?
Thank you. I did base my comment on something four years old.MartinsVidsDotNet
Just hours upon hours upon hours worth of nothing? You mean to tell me I could have been watching vines and cat videos this whole time?
Castle Cake Apologist
Well-Known Member
You can have both! As Martin said, it's all about balance.
Castle Cake Apologist
Well-Known Member
This is true, but the amount of vehicles that Rise is currently not using isn't normal.
RSoxNo1
Well-Known Member
That seems like an additional unnecessary complication. Do doors open on both sides of the vehicles at unload as well or are there 75% of the vehicles with left hand doors and 25% with right hand doors?
flynnibus
Premium Member
So are they suggesting the operating count is being held BACK... or that WDI didn't actually deliver the full complement of ride vehicles based on TDA's input?
Parker in NYC
Well-Known Member
Castle Cake Apologist
Well-Known Member
It is my understanding that the higher-ups do not believe that the ride can handle additional vehicles being cycled in yet, but that the Cast feels they are ready to try. AFAIK, all vehicles are on-site, just not being used. I believe at least 10 vehicles are not cycling currently.
By the way, we're watching Tik Toks now. Same kind of thing, different name.
Last edited:
It can run a max of 36, currently they are being capped at 22.
Pretty much, the way it sounds, everyone below Chapek feels confident in running at least a handful more vehicles. The main problem is Chapek is an idiot when it comes to understanding ops, so him making an ops decision is a stupid one.
Parker in NYC
Well-Known Member
But it's shutting down at 22! I'll never vouch for Chapek but if you can't make it up the mountain with 20 pounds on your back, why add more weight and hope for the best?
Because the reasons for break downs has a lot less to do with the vehicle count than you'd think.
Going up to say 30 vehicles wouldn't really increase the risk of a breakdown, you'd at least get more people through the attraction before it broke.
Parker in NYC
Well-Known Member
Thank you, I didn't know that.
Rob562
Well-Known Member
Multiples of two, not four, since that's how they're dispatched.
I also doubt that the ride can run every single vehicle they have. Attractions are built with spares that are kept in reserve, both to swap out malfunctioning vehicles during the day as well as allow long-term maintenance to refurb and replace wear items on them according to maintenance schedules. Work that can't necessarily be done in a single overnight session.
-Rob
disneygeek90
Well-Known Member
This isn’t the best quality but I’ve recently noticed a little detail I found super cool. You’ll see there are no storm troopers in the hanger when you’re being pulled in but as you get closer you actually watch all the storm troopers run out and into position. Such a nice touch.
Last edited:
gerarar
Premium Member
Imagine if they had a CM as a stormtrooper run out to join the lineup last second, as the doors to the transporter open. Now that would be a nice touch on top of all the nice touches
Then one of the first order officers could be like FN ### why are you late again?! The stormtrooper could trigger one of its little prerecorded messages.
Oh man the possibilities that little show would do, as you’re being ushered by.
Purduevian
Well-Known Member
We are actually able to figure out the current throughput and average dispatch rate based on the rate that boarding groups are being called while the ride isn't broken down.
Assumptions:
-100 people per boarding group (0 no shows)
-While ride is running, Ops is keeping the line ~the same length
-End of day data is not accurate as they are building are building a 2ish hour long line
-All seats are filled
-Any errors between no shows and empty seats will hopefully balance out over the long term.
Using the data from yesterday from thrill-data:
From ~9:05 to ~12:45 pm there didn't seem to be any slow down in calling boarding groups. In those 3 hours and 40 minutes, Groups 24 to 75 were called. That gives us [74-25*100] 4,900 people over [3*60+40] 220 minutes. For a final people per hour through put of [4,900 people/220minutes *60 min/hr]= 1,336 pph.
Because the ride releases 16 people per cycle we have [1336pph/16people per cycle] 83.5 cycles per hour. Meaning the seconds between dispatches [1/83.5*3600] 43.1 seconds between cycles.
Just for fun we can compare this to Disneyland RotR yesterday Using data from Thrill-data once again:
Kinda hard to tell when they started speeding up to build the hour long time for their 9pm closing and 8pm last call, but it seems the speed up happened around 6pm. Therefore we will take the range from 2:00pm to 6:00pm where they called groups 43 to 84. That gives us [84-43*100] = 4100 people over 4 hours (240 minutes). The final people per hour through put of [4,100/4]=1,025 pph.
Looking at a dispatch time [1,025/16]=64.1 cycles per hour. Meaning there are [1/64.1*3600] 56.16 seconds between cycles.
Assumptions:
-100 people per boarding group (0 no shows)
-While ride is running, Ops is keeping the line ~the same length
-End of day data is not accurate as they are building are building a 2ish hour long line
-All seats are filled
-Any errors between no shows and empty seats will hopefully balance out over the long term.
Using the data from yesterday from thrill-data:
From ~9:05 to ~12:45 pm there didn't seem to be any slow down in calling boarding groups. In those 3 hours and 40 minutes, Groups 24 to 75 were called. That gives us [74-25*100] 4,900 people over [3*60+40] 220 minutes. For a final people per hour through put of [4,900 people/220minutes *60 min/hr]= 1,336 pph.
Because the ride releases 16 people per cycle we have [1336pph/16people per cycle] 83.5 cycles per hour. Meaning the seconds between dispatches [1/83.5*3600] 43.1 seconds between cycles.
Just for fun we can compare this to Disneyland RotR yesterday Using data from Thrill-data once again:
Kinda hard to tell when they started speeding up to build the hour long time for their 9pm closing and 8pm last call, but it seems the speed up happened around 6pm. Therefore we will take the range from 2:00pm to 6:00pm where they called groups 43 to 84. That gives us [84-43*100] = 4100 people over 4 hours (240 minutes). The final people per hour through put of [4,100/4]=1,025 pph.
Looking at a dispatch time [1,025/16]=64.1 cycles per hour. Meaning there are [1/64.1*3600] 56.16 seconds between cycles.
Attachments
flynnibus
Premium Member
The problem is this kind of 'input' analysis is very much a loose estimate. It's far more accurate and simple to simply count how many riders exit the attraction. Your estimate doesn't include any of the FP returners and assumes all riders are from this perfectly sized BG. Add in the uncertainty on when a group shows vs being called.. means you could be counting multiple BGs in the timeslot that didn't actually ride.
It's kinda the best you can do from afar... but isn't really all that valuable to stand firm with.
In the DL comparison.. if we can safely assume both sites are using BGs... the BGs/hr seems to be the safest comparison between general handling of new guests.