I am not a fan of the updated UI. While it looks nice it is much harder to use than the old version. I am using the desktop site on Win 11/Chrome browser. When adding a new attraction that I want to place at the beginning of a plan, it is a multistep process. I need to add it and then perform multiple drag and drops as the plan does not scroll up when I reach the edge of the visible view. Then after every drag and drop it scrolls to the top of the plan, so I need to scroll down to where I temporarily dropped my new attraction and then move it up as far as I can. This process repeats until I have it where I want it.
I am also noticing on occasion that a plan will have an artificial ābreakā where it wonāt have us enter a queue at the expected time. For example I am making an MK plan for arrival day, with a plan to enter the park at 1:30pm.I have meet Mickey as the first step and it gives me a time of 3:00pm to enter the queue, which throws off the whole plan from that point.
The last thing I noticed is that it occasionally give a warning/error that a LL wonāt get used for an attraction I donāt have a LL set up for.
I am making it work as I start to plan out our trip for next February, but wanted to provide feedback on what i was seeing with the ānew to meā system.
This one is usually because you have more time allocated to the park than attractions to fill the time. It picks seemingly random places to out breaks to best optimize wait times. You should either shorten your hours in the park, or add more attractions, food, or breaks yourself to avoid this kind of thing. (This behavior is exactly the same as it was before the UI update.)
That may be, but in this case there should be enough to fill up the time as I have 3 attractions that cannot be done because they are currently āscheduledā after the park closes.
I will delete and recreate and see if that fixes the issue
Okay. I would manually move Meet Mickey down a few steps and reevaluateā¦perhaps the software thinks the first available time to meet Mickey is at 3. Not sure if that is correct, but they probably just need to go in a fix it then.
That also happened to me and apparently got fixed when I switched from āāminimize waitingāā to āābalanceāā.
I agree with you as someone also making TPs for the first time since the changes that it seems like it worked better before. However, unlike you, I am not very proficient with computers.
Thanks for the response, but I generally leave it set to balanced and average walking speed. I will play with those settings and see if they have any impact.