I had this issue too and submitted a ticket with screenshots. The LL part is not working for me.
It looks like weāre missing some LL data. David is working on it now. ETA is less than an hour, I think.
Go ahead and open tickets if itās anything other than that. Thanks!
2 Likes
Iām told weāve regenerated the LL data. Please try to re-optimize plans, if youāve got them.
3 Likes
Hmmmm, itās still not working for me. I deleted and redownloaded the app. And it shows that I have G+ but the system is not adding in lightning lane suggestions for me.
When I manually add in an LL for PPF, I get this.
1 Like
Ah, thanks for sending the screencap with that date. Looking at it now. I think we just loaded December and are on to January now.
3 Likes
Makes sense to prioritize the people that are in the parks now. Thank you 
2 Likes
I canāt seem to get LL return time forecasts consistently except as part of an Optimized plan where the system chooses my LLās. I appreciate the system is trying to minimize my total time for the day, but I actually care more about minimizing wait time by maximizing LLās.
What I would like is to give it a list of target LLās to obtain at specific booking times, and get a RT forecast back for each - I could figure out the rest from there. But I canāt get that to work, bc Evaluate wants all those Obtain steps to happen before plan start time. I can play around with plan start time and get something, but itās laborious.
1 Like
Iām playing around with it, not sure if Iām doing something wrong.
I created a plan with the plan times of 10:30am-7:00pm with six G+ eligible attractions, then optimized. It only has me obtaining and using two LLās the whole day. Obtaining one at 9:27 and the other at 3:29. There is no free time at all within the plan, and the last attraction is well past 7:00.
2 Likes
Are you happy with that plan?
It seems to be optimizing around getting through all the rides listed even if it means riding standby, and assumes that plan start time is fixed with no wiggle room.
What are you looking for in a plan?
1 Like
Well no, it runs to nearly 8pm.
I understand it wonāt get all the LLās if not necessary. And it hasnāt gotten any better when I shorten the hours. Hmm, definitely will take time to figure outā¦Iām hoping this isnāt too complicated for most users. 
And youāre right, you should be able to manually add an attraction and get a forecasted return time. TP has that data.
1 Like
Fwiw I have not had a plan work with any parameters Iāve set up since fpp went away. I just think the data is too unpredictable to work with the software anymore.
4 Likes
I agree the data is now very complex. My suggestion to @Len would be, is it possible to provide more flexibility to allow users to optimize the plan themselves? I donāt necessarily need TP to find the ābestā plan, but I sure could use help pulling together all the supporting information in one place, like forecasted RTās, waits, walking times, opening hours, available rides, etc. so that I can make a āgood enoughā plan. Iād be happy if I could put together a list of rides and LL āObtainsā and have TP look up / calculate the forecasted wait / RT times / walking times given the order I put them in and the start time I put in. Then, I can move them around and play āwhat ifā until I find something I like even if itās not the absolute ābestā.
Is that what the Evaluate function is supposed to do?
3 Likes
I mostly use Evaluate these days when I make a TP. I know which attractions I want to do when and roughly when the best time is to do them. Sometimes Iāll do one optimize just to see what it says. But after that Evaluate is all I need.
6 Likes
With Evaluate, how do you get it to forecast a bunch of LL āObtainsā?
2 Likes
I havenāt tried the new features yet, so if anything I would just do a break or snack if thereās a step I need to squeeze in.
You may want to post your question on one of those blogsā¦
We plan to do this with Evaluate. To your point, we first wanted to see how complicated the UI got with what we had. Letās see how this goes and weāll go from there.
5 Likes
Sharing updates and info here from Lenā¦
8 Likes
That part isnāt the issue; the problem is that it uses a predicted standby wait time for an attraction I will be using LL for. Thus It will show 52 min wait when it should be 6 min. I havenāt been able to figure out how to make TP factor in the use of the LL.
3 Likes