News TRON Lightcycle Run Virtual Queue and Lighting Lane status

[gerarar]

7am drop lasted for 5.181 secs.
Sunday 7am Drop Average 11.3s -> 10.6s (-0.7s)

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

 

[gerarar]

1pm drop lasted for 1302.254 secs, or ~22 mins.
Sunday 1pm Drop Average: 2hr 0m -> 1hr 50m (-10m)

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

 

[gerarar]

Final Day 69 Stats (5/28):
7am: 5.2 secs
1pm: 1302.3 secs, or ~22 mins

BG 185 (-20) is the last BG called for the day at 9pm.

Notable stoppages: None

Average pace: 4mins/BG

VQ Drop Mean/Average:
7am: 11.1s -> 10.6s (-0.5s)
1pm: 2hr 0m -> 1hr 50m (-10m)

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

 

[gerarar]

7am drop lasted for 193.523 secs, or ~3 mins.
Monday 7am Drop Average: 5.7s -> 24.5s (+18.8s)

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

 

[gerarar]

1pm drop lasted for 14493.992 secs, or ~4 hours 2 mins.
Monday 1pm Drop Average: 2hr 3m -> 2hr 15m (+12m)

Up to BG 65 called at 1pm, same as yesterday.

 

[gerarar]

Final Day 70 Stats (5/29):
7am: 193.5 secs, or ~3 mins
1pm: 14494.0 secs, or ~4 hours 2 mins

BG 188 (+3) is the last BG called for the day at 9pm.

Notable stoppages: None

Average pace: 4mins/BG, 2mins/BG from 8pm to close.

VQ Drop Mean/Average:
7am: 5.7s -> 24.5s (+18.8s)
1pm: 2hr 3m -> 2hr 15m (+12m)

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

 

[Turtlekrawl]

7AM drop last 2 days:
5 seconds on Sunday
3 minutes on Memorial Day

To what do we attribute these crazy wide swings? I’ll go out on a limb and say MK was not 37x busier on Sunday

 

[gerarar]

7am drop lasted for 5.208 secs.
Tuesday 7am Drop Average: 8m -> 7m (-1m)

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

 

[Rsj88]

Since the 1:00 drop seems to be lasting longer can you cancel your spot and rebook to get a later time (as long as times were available still)? Or would canceling not allow us to book again in the same drop?

 

[DisQuick]

Since the 1:00 drop seems to be lasting longer can you cancel your spot and rebook to get a later time (as long as times were available still)? Or would canceling not allow us to book again in the same drop?

I actually did this on Sunday. I booked at 1:00 and got 105, then at 1:02 I booked again and got 161. Great idea if you want to ride at night.

 

[Rsj88]

I actually did this on Sunday. I booked at 1:00 and got 105, then at 1:02 I booked again and got 161. Great idea if you want to ride at night.

Thank you so much! That’s exactly what we are trying to do!

 

[gerarar]

1pm drop closed at 1:24pm, lasting for 1405.935 secs, or ~23 mins.
Tuesday 1pm Drop Average: 1hr 40m -> 1hr 33m (-7m)

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

 

[Twirlnhurl]

7AM drop last 2 days:
5 seconds on Sunday
3 minutes on Memorial Day

To what do we attribute these crazy wide swings? I’ll go out on a limb and say MK was not 37x busier on Sunday

Imagine that there are 100 boarding groups and 100 people trying to get a group at the distribution time.

Now imagine that 95% of the people trying are successful right when it drops, but 5% of people have trouble with their internet and have to restart their app.

In this case 95 people get a group in 5 seconds and 5 people get a group when the app restarts 3 minutes later. This is like what happened on Monday.

If there are 110 people who want a boarding group, and there are still only 100 groups available, you would get a different result if the app performance rate was the same.

In this case, 104 people would not have app problems. Of that, 100 would get a group in 5 seconds, 4 people with a working app would be out of luck, and 6 people who restart the app would be out of luck as well. This is similar to what happened Sunday.

In this example, a change of 10% in the demand would change the boarding group availability by the observed 37x change in the availability window.

 

[gerarar]

Final Day 71 Stats (5/30):
7am: 5.2 secs
1pm: 1405.5 secs, or ~23 mins

BG 205 (+17) is the last BG called for the day at 10pm.

Notable stoppages:
10:02 - 10:20am

Average pace: 4mins/BG, 2mins/BG from 8pm to close.

VQ Drop Mean/Average:
7am: 8m -> 7m (-1m)
1pm: 1hr 40m -> 1hr 33m (-7m)

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

 

[gerarar]

7am drop lasted for 5.151 secs.
Wednesday 7am Drop Average: 29.0s -> 26.8s (-2.2s)

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

 

[gerarar]

1pm drop lasted for 1954.309 secs, or ~33 mins.
Wednesday 1pm Drop Average: 2hr 7m -> 1hr 59m (-8m)

Up to BG 65 called at 1pm, 2 more than yesterday.

 

[gerarar]

6pm drop lasted for 5.143 secs.
Wednesday 6pm Drop Average: 1hr 1m -> 54m (-7m)

Up to BG 127 called at 6pm, 5 more than yesterday.

 

[gerarar]

Final Day 72 Stats (5/31):
7am: 5.2 secs
1pm: 1954.3 secs, or ~33 mins
6pm: 5.1 secs

BG 200 (-5) is the last BG called during regular park hours at 10pm.

For EEH, resumed at 10:35pm with BG's 207-209, with BG 241 as the last BG called for the day at 11:58pm.

Notable stoppages:
10:36 - 10:54am

Average pace: 4mins/BG, 4mins/BG during EEH

VQ Drop Mean/Average:
7am: 29.0s -> 26.8s (-2.2s)
1pm: 2hr 7m -> 1hr 59m (-8m)
6pm: 1hr 1m -> 54m (-7m)

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

 

[gerarar]

7am drop lasted for 4.825 secs.
Thursday 7am Drop Average: 27.8s -> 25.7s (-2.1s)

BG's 1-6 called at 10:31am as part of the initial wave.

 

[Ayla]

Even though demand for this ride is no where near what they hoped (can I insert 'I told you so' here?), I will say the ride appears to be very consistent and reliable, with very little downtime or issues.