News TRON Lightcycle Run Standby Line and Lighting Lane status

[gerarar]

I'm curious how you compiled these stats. It is great information. Thanks.

Basically monitor the VQ backend and time when the various queues open at 7am/1pm/6pm.

Store all the information in a database which then generates various stats and graphs like the scatterplot above.

 

[Ayla]

The following is the process that I have come up with combining mine and other people's tactics. I have gotten boarding group #1 everytime I've used the virtual queue, which is about 10 times between all the rides that required it.

*NO WIFI* turn off wifi. Disney property wifi has a history of being unreliable. Unless you truly can't get a cell signal.

• During this process you will use the phone that is the latest model with the fastest hardware. Have a secondary backup device with you in case you run into issues with the primary device.

• Make sure the My Disney Experience app is updated to the latest version and you are logged in on the primary device and backup device.

• Download a Atomic clock app on a backup device and familiarize yourself with it and make sure the audible beep is on and loud.

• On all devices in the phone settings change your screen off/lock timer to the longest time so the screen won't turn off at the worst possible moment.

• Recon the area around the hotel and find the best cell signal. Don't be inside your room because the walls might make the signal slightly slower. If possible get a elevated position like a balcony or exterior walkway on a upper floor. If necessary do speed tests to see which signal location is the fastest.

• Well before 7a the app will let you confirm your party that is eligible to get in the virtual queue, complete that process. If for some reason a party member is not eligible don't get hung up on fixing that issue, you just need one person eligible to be able to get in the virtual queue and then you can fix the issue later when you get in the park. Guest services will be able to add members to your boarding group.

• If for any reason at anytime you run into a issue in the process of the virtual queue that is preventing you from getting a boarding group take a screenshot because there is a good chance guest services will give you a boarding group if you can prove the mistake was on their end.

• Well before 7a restart both phones to get them to run at optimal performance. After restarting do not open any other apps except the Disney app and on the secondary device have the atomic clock app and Disney app the only apps open. Kill all back round apps.

• On the secondary device get on the screen to join a virtual queue and then open and stay on the atomic clock app and have the volume up to hear the beep for the minute mark. Place that phone down and keep it so it is easily accessible in case you need to use it.

• While on the primary device in the Disney app in the virtual queue section, hover your finger over the white button that says "refresh". Do not use the pull to refresh as that places your finger in a different spot on the screen. Don't visually watch the Atomic clock app, use the audible beep to time yourself to push the "refresh" button.

• The millisecond before the audible beep of 7a RAPID fire tap the "refresh" button and it will turn to a blue "Join Virtual queue" button, don't stop rapid fire tapping, keep tapping in the same location and you will hit the blue button. Remember DON'T stop tapping, your finger is in the exact location of the screen that the button appears to join.

• If for some reason the rapid fire tap is not working/feasible, after tapping refresh just push the blue buttons. Don't stop to read the blue button. If it is blue it is the one to tap

• Congratulations you got yourself a boarding group!

• It is perfectly acceptable to have multiple people trying for a boarding group in the same party at the same time. Just make sure you still have a separate device with the atomic clock

All that hassle for a 90 second ride...

 

[gerarar]

1pm drop lasted for 4.876 secs.
Saturday 1pm Drop Average: 5.0s -> 5.0 (+0)

Up to BG 54 called at 1pm, 1 less than yesterday.

 

[gerarar]

Final Day 19 Stats (4/8):
7am: 3.5 secs
1pm: 4.9 secs

BG 142 (-3) is the last BG called for the day at 10pm.

Notable stoppages:
10:39 - 10:57am

Average pace: 6mins/BG

VQ Drop Mean/Average:
7am: 3.9s -> 3.8s (-0.1s)
1pm: 5.0s -> 5.0s (+0)

That does it for Day 19 of TRON Lightcycle / Run!

 

[gerarar]

7am drop lasted for 3.224 secs.
Sunday 7am Drop Average: 3.6s -> 3.5s (-0.1s)

BG's 1-15 called at 8:15am as part of the initial wave.

 

[gerarar]

1pm drop lasted for 5.019 secs.
Sunday 1pm Drop Average: 4.7s -> 4.8s (+0.1s)

Up to BG 52 called at 1pm, 2 less than yesterday.

 

[gerarar]

Final Day 20 Stats (4/9):
7am: 3.2 secs
1pm: 5.0 secs

BG 145 (+3) is the last BG called for the day at 10pm.

Notable stoppages:
10:38 - 10:54am

Average pace: 6mins/BG

VQ Drop Mean/Average:
7am: 3.6s -> 3.5s (-0.1s)
1pm: 4.7s -> 4.8s (+0.1s)

That does it for Day 20 of TRON Lightcycle / Run!

 

[arich35]

How do these times compare to the VQ drops with Rise and Guardians?

 

[gerarar]

7am drop lasted for 3.701 secs.
Monday 7am Drop Average: 3.5s -> 3.6s (+0.1s)

BG's 1-15 called at 8:45am as part of the initial wave.

 

[DisneyCane]

What is the typical wait time once you join the queue when your group is called?

 

[Tuvalu]

What is the typical wait time once you join the queue when your group is called?

We waited 50 minutes on Thursday. 30 outside and 20 inside. This was in the morning, BG 25.

 

[wdwmagic]

How do these times compare to the VQ drops with Rise and Guardians?

The ~4 second 7am drop has been fairly consistent anytime a VQ has been offered. Same with the 1pm initially, although that got longer over time.

 

[gerarar]

1pm drop lasted for 24.502 secs.
Monday 1pm Drop Average: 4.8s -> 11.3s (+6.5s)

Up to BG 58 called at 1pm, 6 more than yesterday.

 

[TheMaxRebo]

1pm drop lasted for 24.502 secs.
Monday 1pm Drop Average: 4.8s -> 11.3s (+6.5s)

Up to BG 58 called at 1pm, 6 more than yesterday.

Nice to see a bit of an increase, was wondering impact of Easter week combined with it being new

 

[gerarar]

Final Day 21 Stats (4/10):
7am: 3.7 secs
1pm: 24.5 secs

BG 152 (+7) is the last BG called for the day at 10pm.

Notable stoppages: None

Average pace: 6mins/BG

VQ Drop Mean/Average:
7am: 3.5s -> 3.6s (+0.1s)
1pm: 4.8s -> 11.3s (+6.5s)

That does it for Day 21 of TRON Lightcycle / Run!

 

[gerarar]

7am drop lasted for 3.283 secs.
Tuesday 7am Drop Average: 3.8s -> 3.7s (-0.1s)

BG's 1-15 called at 8:45 am as part of the initial wave.

 

[networkpro]

It will be interesting to see if the crowd levels drop off this and the following week.

 

[gerarar]

1pm drop lasted for 6.452 secs.
Tuesday 1pm Drop Average: 3.4s -> 4.2s (+0.8s)

Up to BG 56 called at 1pm, 2 less than yesterday.

 

[Coaster Lover]

1pm drop lasted for 24.502 secs.

24 seconds? That's enough time to get a pass without needing to rely on an atomic clock to make sure you hit refresh at just the right moment! Gives me hope that when I go in July I won't have to worry that much about getting in on one of the two drops...

 

[gerarar]

Final Day 22 Stats (4/11):
7am: 3.3 secs
1pm: 6.5 secs

BG 152 (+0) is the last BG called for the day at 10pm.

Notable stoppages:
2:48 - 3:04pm

Average pace: 5-6mins/BG

VQ Drop Mean/Average:
7am: 3.8s -> 3.7s (-0.1s)
1pm: 3.4s -> 4.2s (+0.8s)

That does it for Day 22 of TRON Lightcycle / Run!