I have a 5:00 FP for FOP and it still shows a 50 minute wait in my touring plan made through touringplan.com. Is this accurate? On another AK plan, it also refuses to put Navi standby first thing in the morning although I have a 9 am FP for FOP...which is even recommended in their Pandora youtube video! I know I can evaluate instead of optimizing, but still...
I'm having the same issues, when I put Na'vi first thing, it has it having a 50 minutes wait. When I optimize, it puts it at 9:30 with a 37 minute wait. I'm just going to plan on going to Na'vi first thing and if the wait is longer than 20 minutes, we'll just do it later or not at all. To see if my plan will work, I put a break first thing and made it for 20 minutes. This seems to work and at least I'll have an idea of how my plans look for the rest of the day. I keep checking TP daily to see if the times change, but so far they haven't. We have FP+ for FOP at 12:30 and TP is showing a 31 minute wait for it. I noticed that you're also planning your first mother/daughter trip. My daughter and I leave in 12 days for our first mother/daughter trip and I can't wait! Hope you have a wonderful trip!
There is a forum on touringplans.com. You might want to post there and ask Len to check it out for you.
If you plan to start the day by being there early enough to catch NRJ at rope drop then you could just start your plan at 9 and insert a “meal” of 5 min at Pongu Pongu or Samulis Canteen to help it find you and just put in the notes that it means you are doing NRJ in he early time when they pre open Pandora. The longer wait times for even at fP for FOP though are not a glitch. TP has adjusted them to be pretty lengthy given data they must have that sometimes even the FP waits are long. Several threads on that on the TP forum.
I had the most trouble with my TP plans for AK this year. Everything else was gone but I had several issues with that plan I couldn't resolve without entering in breaks or meals and it still send to have issues with you using multiple FPs for the same ride.
We have the same issue. I didn't even put FOP into our EMH plan for the AK because it shows a 40 minute wait at 7 pm. We are going to be there early enough that I feel we will be on/off in the first 30 minutes. Then we are going to Navi and will continue our plan as scheduled. We may be a few minutes off, but we can evaluate after our first two steps.
With TP, I don’t use “optimize” until I’m in the parks - just Evaluate when planning. My theory is that the algorithm has issues optimizing a future date without good/accurate/current wait time data. I could be 100% wrong, but when I optimize I got some weird attraction sequences (granted, this was a few years back so maybe they’ve made updates). Still love the tool and recommend it!
