RSoxNo1
Well-Known Member
I think that is an unrealistic expectation. The logistics of scheduling a limited capacity venue, like a restaurant, and attractions that can handle (in most cases) 1000s of people an hour are radically different. Will this have some impact on standby wait times? Probably. Will it be drastically negative? Probably not.
Well stated. Let's say for argument's sake that Test Track handles 2000 riders per hour. In a 10 hour operational day that is 20,000 riders. If fastpasses are based on 25% of capacity that means 5,000 are available. No matter what no more then 20,000 people can ride Test Track per day. There are only so many people visiting Epcot in any one given day.
If you assume that Disney's computers spread out the fastpass distribution over the course of the day then fast pass effects the standby time between 2.5-3 percent.
The "scheduling" of xPass would likely eat into or replace the current Fastpass system. Using your Test Track example (the numbers are less than 2000 per hour, but that's irrelevant for the purposes of this), my understanding of the FP system is that Disney distributes 6% of the rides Hourly Capacity in FP tickets for every 5 minute interval available. For some attractions not all of the 6% are distributed before the time is bumped up.
If the 6% # is correct than it means that as you get deeper into the day, the percentage of guests that can ride the attraction using fastpass will continue to approach 72% (6% x 12 - the # of 5 minute intervals) of guests riding the attraction will ride using the Fastpass system. I've always heard this 6% #, and it's always seemed high to me - I don't know if it's correct for sure, but again, I'll assume that it is for this explanation.
If xPass replaces Fastpass and also enforces the end time, the 72% number will be harder to reach, and as such it will actually improve standby times.
If xPass is used in conjunction with Fastpass, I would expect some system where the xPasses will replace a percentage of Fastpasses, either as a fixed percentage or as part of a scheduling procedure. For example:
- xPass would allow guests to schedule 1 attraction every 2 hours. They would pick the times for these attractions and the 1 hour window
- For the Test Track example above, each 5 minute interval would have 120 xPasses or Fastpasses available
- If you want to Schedule Test Track for 10:00 AM - 11:00 AM using xPass, you would get one of these 120 passes meaning that those people in the park would only have 119 Fastpasses left
The other combination option would be switching to 3% Fastpass and 3% xPass (or 4 and 2, again, this is simplified for explaining purposes).
- This could be somewhat more favorable simply because it stops the % of scheduled xPasses all while making a limited number of Fastpasses also available.
All in all, this could work, but there are a few other things to consider.
- Enforcing the end times will improve Standby times
- Will this change touring patterns - Guests won't ride an attraction if the wait time exceeds a certain time. Previously they could "spontenously get a Fastpass" to solve this issue - xPass might not cater to this.
- How will the end times be enforced in the event of a ride closure?