Expedition Everest Line

[surferdave]

It suspect it will be at least a year before everyone gets used to this and keeps the FP+ return line moving.

I doubt that most users on any given day will be getting used to it. A large percentage will always be first time users and another large percentage will only use the system once a year or less.

 

[JimmyV]

The 2 scanners are too close for two people to scan at the same time comfortably - I won't step behind someone I don't know that closely just for fear they will take a step backward.

This is an excellent point and one that they should address. In fact, they would be better served if they moved the scanners closer to one another, but had people walk on the outside of them instead of having people pass through the inside of them. It is really close quarters now, and it asks too much of strangers to rub up against one another so that they can "tap" the two posts simultaneously.

 

[Paging Tom Morrow]

I don't see why anyone would take one instance of a problem at Expedition Everest on one particular day and make an indictment of the entire FP+ system.

We can all speculate as to the cause:

• Network Down
• Mechanical Delay
• Passenger Medical Situation
• Abnormally high number of people returning at that particular point in time
• Cast members forced to respond to a nearby emergency (lost parent?)

...but the fact of the matter is that none of us really know. It is easy to blame FP+. It is an easy target, particularly because those of us on this board, who had learned how to maximize our Disney experience need to find a new way to do so.

I used FP+ for the week between Christmas and New Year's Day. It was a game changer in a very good way. We had FP+ reservations for Test Track on New Year's Eve for 5PM. We didn't enter the park until almost 3PM and under the old system, FP- would have been distributed for the whole day by then. Standby for Test Track was 5 hours when we entered the FP+ queue. We easily made our 6PM dining reservation at Teppan Edo.

We are using it again in two weeks (Palm Sunday through Easter Monday) for an offsite visit. If my experience changes considerably, I will be more than happy to report such.

 

[surferdave]

I don't see why anyone would take one instance of a problem at Expedition Everest on one particular day and make an indictment of the entire FP+ system.

We've actually seen this reported more than once, it seems to be one of the most common new problems that sometimes occurs since at least October.

 

[sonofanarchy]

I don't see why anyone would take one instance of a problem at Expedition Everest on one particular day and make an indictment of the entire FP+ system.

This is part of the reason why I have so little patience left with FP+. Every time we see another example of the problems the system has (and we see them quite often), people defend it by saying "It was an isolated incident" or "It wasn't like that when I was there." It's as if people think the videos, pictures and reports are all made up. And if the defenders DO admit there's a problem, we get the canned Disney response of "It's still in testing."

All I can say is this: I have yet to personally experience FP+. July will be our 1st go-around. We have vacationed at WDW about 40 times over the years. The majority of those times have been during peak season, the past 10 years in July. We've seen it RIDICULOUSLY crowded at times. However, for regular loading rides like Everest, Thunder Mountain, Space Mountain, we have NEVER experienced Fastpass lines that have run outside the attraction. I've never seen waits like reports we've had on here for Pirates, Haunted Mansion, It's A Small World, etc., since the beginning of FP+. Going by that, honestly, what else is anyone supposed to think other than this system is not working in it's current state? Or worse, maybe it is working the way Disney intended, but we've been given a system that is far less efficient than the prior one.

 

[Kate and Family]

We've actually seen this reported more than once, it seems to be one of the most common new problems that sometimes occurs since at least October.

Yea... but it is so hard to tell when it is multiple postings of the same occurrence and when it is multiple occurrences.

 

[surferdave]

Yea... but it is so hard to tell when it is multiple postings of the same occurrence or multiple occurrences.

I experienced it in October and I didn't start this thread so that's at least two.

 

[JimmyV]

I don't see why anyone would take one instance of a problem at Expedition Everest on one particular day and make an indictment of the entire FP+ system.

We can all speculate as to the cause:

• Network Down
• Mechanical Delay
• Passenger Medical Situation
• Abnormally high number of people returning at that particular point in time
• Cast members forced to respond to a nearby emergency (lost parent?)

...but the fact of the matter is that none of us really know. It is easy to blame FP+.

Apply Occam's Razor.
I experienced what the video shows. The network was not down. There was no mechanical delay. There were no medical issues. The CMs were not called into action elsewhere. As for an abnormally high number of people returning at the same time? I suppose that has to be the case, but what is an "abnormally high number" when the system doles out evenly spaced FPs? Shouldn't the system be designed to handle the very crowd it invites? But the real reason is/was that Disney underestimated the clunkiness of the Mickey Tap process and put tapstiles outside of the queue entrance forcing people to line up in order to line up. It really is that simple. And it really is fixable. Lose the first Mickey tap and that entire line (and more) gets swallowed by the ordinary ride queue and people walking around the park won't see what you see on the video. The line becomes invisible. It may still be 20 minutes long. But I don't think a 20 minute "invisible" line would get nearly the press nor raise nearly the eyebrows as an exterior visible 20 minute line. Hide the line and the problem disappears, IMO.

 

[Kate and Family]

I experienced it in October and I didn't start this thread so that's at least two.

Thanks surferdave. Time frames do help quite a bit. At the very LEAST once in October and once in March

 

[JimmyV]

I experienced it in October and I didn't start this thread so that's at least two.

Add my queue on 2/15 and we are up to three.

 

[LilyWDW]

This is part of the reason why I have so little patience left with FP+. Every time we see another example of the problems the system has (and we see them quite often), people defend it by saying "It was an isolated incident" or "It wasn't like that when I was there." It's as if people think the videos, pictures and reports are all made up. And if the defenders DO admit there's a problem, we get the canned Disney response of "It's still in testing."

The issue of this is that some people take the reports when these things happen and act that this is what always happens. Even though I don't see them as the majority of reports. So both sides are guilty of acting like the other side doesn't exist and can't be right.

Do these lines happen? Yes. Do I think it is 100% due to FP+ every single time? No. Why? Because we don't know what could be happening in every single instance. I also don't think we have enough data. Not personal experiences, but actual data to make a factual conclusion.

 

[2Tiggies]

This is part of the reason why I have so little patience left with FP+. Every time we see another example of the problems the system has (and we see them quite often), people defend it by saying "It was an isolated incident" or "It wasn't like that when I was there." It's as if people think the videos, pictures and reports are all made up. And if the defenders DO admit there's a problem, we get the canned Disney response of "It's still in testing."

Perfectly stated.

I was initially partly entertained when example after example would be posted whether it be photos, video or a personal report from a recent trip, and yet every single one of these are isolated incidents. I'm finding it a bit less amusing now.

 

[Kate and Family]

Add my queue on 2/15 and we are up to three.

Thanks Jimmy. Again time frames are helpful.

BTW, I liked the suggestion (I think it was yours) to bring the mickey FP posts closer together and forming lines on either side.

 

[sonofanarchy]

Yea... but it is so hard to tell when it is multiple postings of the same occurrence and when it is multiple occurrences.

With all due respect, it really isn't. If you read the threads, these incidents aren't all related to 1 or 2 attractions.

 

[2Tiggies]

I also don't think we have enough data. Not personal experiences, but actual data to make a factual conclusion.

When I've had to decided 60 days out what I want to ride, where and what time and then have to make sure I get my behind over there within that window, only to be met by a snaking long line, quite frankly I don't care about the data. I see a line that is unacceptably long. We are never going to get all the data. Disney does not disclose much of this and a good deal is left to speculation.

Data is the problem of the company receiving my payment. As a guest I should not have to worry about it. A ride breaking down is a little different. Stuff happens and you accept it as bad luck and get over it. A poorly implemented system that was rolled out prematurely and the details of which are being made up as they go along using paying guests as their guinea pigs is just bad form.

 

[sonofanarchy]

The issue of this is that some people take the reports when these things happen and act that this is what always happens. Even though I don't see them as the majority of reports. So both sides are guilty of acting like the other side doesn't exist and can't be right.

Do these lines happen? Yes. Do I think it is 100% due to FP+ every single time? No. Why? Because we don't know what could be happening in every single instance. I also don't think we have enough data. Not personal experiences, but actual data to make a factual conclusion.

At this point, it shouldn't be happening at all. The fact that it is, to me, is unacceptable and indicates there is a major problem.

 

[sonofanarchy]

When I've had to decided 60 days out what I want to ride, where and what time and then have to make sure I get my behind over there within that window, only to be met by a snaking long line, quite frankly I don't care about the data. I see a line that is unacceptably long. We are never going to get all the data. Disney does not disclose much of this and a good deal is left to speculation.

Data is the problem of the company receiving my payment. As a guest I should not have to worry about it. A ride breaking down is a little different. Stuff happens and you accept it as bad luck and get over it. A poorly implemented system that was rolled out prematurely and the details of which are being made up as they go along using paying guests as their guinea pigs is just bad form.

 

[Kate and Family]

With all due respect, it really isn't. If you read the threads, these incidents aren't all related to 1 or 2 attractions.

Absolutely. And I might add, that even if the March-Everest event was not FPP related, that would not mean that there are not problems with lines being caused by FPP elsewhere. And visa versa, for that matter. Even though FPP may be causing long lines, that does not mean that there are not problems at attractions that are independent of FPP.

In the end, what it comes down to is the individual experience of the whole experience. I say this not to ignore/discount/or disagree with your view of things. But consider this.. When someone says how much fun he had after getting back using FP+, it is ok. Just because someone has a different experience/enjoyment does not invalidate your reasoning or view point.

OH no... are we working our way back to the thread regarding cause and correlation!


EDITED That there is good evidence that there are problems with lines, seems evident. Regardless of the reason- that needs to be handled.

 

[2Tiggies]

I think the fact that they have made available signs marking where some of the extended FP lines actually begin says a lot in itself. If these were isolated incidents there would be no signs. A CM for an unexpected problem would be sent over to help the guests locate the end of the line. But to have ride specific signs all ready to grab and go says this is happening often enough that they are prepared for it.

 

[erin1715]

I think the fact that they have made available signs marking where some of the extended FP lines actually begin says a lot in itself. If these were isolated incidents there would be no signs. A CM for an unexpected problem would be sent over to help the guests locate the end of the line. But to have ride specific signs all ready to grab and go says this is happening often enough that they are prepared for it.