I think this is ROTR's biggest long-term issue. They cannot afford for significant numbers of non-AP guests to sink all the effort and expense into a trip, only to go home without having experienced their new flagship attraction. If days like yesterday end up being common for more than a month or so, they're going to have a real mess on their hands.I'm hoping this calms down a bit before we get there in July. Otherwise, I'll have a disappointed 8 year old to deal with.
I think you're right that the rush will drop significantly 3-6 months out. But, I'm not sold that this virtual queue is a temporary thing. I'm not sure we'll ever see it go away, and I definitely don't see it going away until the ride becomes much more reliable. As much as they can't afford to have paid guests walking away without a chance to experience it, compounding that issue with the risk of hours of wasted time in a physical queue is an even worse scenario.I'm guessing things will settle down by June if not March. The AP crowd will have already figured out a way to see it and the virtual fast pass will be gone. It happen that way for Target Run and Pixar Pier.
Very stable. I haven't been messing with the join request whatsoever.How has the response time been on the query? Consistent or have you seen any jitter? I would hope the status query would be stable... while the join request may take the brunt of the delay
Nah, Disney is very good about this. Everything is in it's own bucket basically. Fastpasses vs the Virtual Queue vs Tickets vs everything else. Anything not public (think your passes and tickets) are very secure. General statuses are still pretty secure.
Polling the info the server is willing to share is not the same as hacking the server and forcing it to give info it normally wouldn't share.
This is not indicative of security. It would be interesting if it's behind authentication or not.. but even that is usually done with common technologies. When your app is on a platform like android that everyone has developer access to... you don't rely on secrecy for security. You effectively have none.
And yet they had another morning where they couldn't open with the park. For the fourth day in a row.Luckily, they’re chugging along today, already at group 28 before 10AM.
Yep! When I rode it I waited maybe 15-20 minutes tops in line.I’m glad I wasn’t that impressed with the ride and don’t have to ride it again. This system is a mess.
Good luck to everyone with this process.
Based on my experience living in LA, "The AP crows will have already figured out a way to"....exploit itI'm guessing things will settle down by June if not March. The AP crowd will have already figured out a way to see it and the virtual fast pass will be gone. It happen that way for Target Run and Pixar Pier.
Facts! The ride is not worth all this effort and hassle, but I understand folks wanting to experience it for the first time.Yep! When I rode it I waited maybe 15-20 minutes tops in line.
I couldn't imagine going through this much hassle to ride any ride, let alone this one.
While I'm not surprised there's issues (as any new ride would have), I'm surprised they're having this big of issues. I would've thought since it was "done" before DHS's and the extra month after DHS opened would've helped.Double big yikes. I thought I was being a tad conservative with my 800 guesstimate. 700 per hour is truly abysmal.