Bryn 4 Posted December 8 I've been trying to find a route from LIRF to KCLT, but I get an out of error message before it finds a route. Ticking "Ignore Route Restrictions" solves that, but then isn't that one of the reasons for using the advanced route finder in the first place? Share this post Link to post Share on other sites
alpha117 44 Posted December 8 Hi Bryan Seems OK here Share this post Link to post Share on other sites
srcooke 254 Posted December 8 Replicated here Bryn. Share this post Link to post Share on other sites
phil747fan 44 Posted December 8 ok for me too. and used only find route. advanced one worked fine too. Share this post Link to post Share on other sites
Skyrock 3 Posted December 8 I have the same problem for routes like EDDF-RJBB. Not enough memory after it has calculated for a while. Please fix that. Share this post Link to post Share on other sites
phil747fan 44 Posted December 8 hello Skyrock, could you explain your process up to the time you reach out of memory? which aircraft did you use for it? Share this post Link to post Share on other sites
Skyrock 3 Posted December 8 What I did was the following: open up PFPX, head into the "Flight" Tab, enter the Dep & Dest. airport (EDDF & RJBB), entered the Registration of my Aircraft (I used the 747-400 first, but then also the 777-200LR), thereafter hit "Random Payload" and then at the top, clicked "Edit" to head into the route window. From there, I went into the Advanced Tab, selected FL330 and 390 as Min & Max altitudes and let it calculate. I ran for a short while and then the error showed up.Funny thing is, I can't reproduce it anymore for some reason. Now it hasn't happened until now, but I'll give it a try tomorrow again. Share this post Link to post Share on other sites
phil747fan 44 Posted December 8 happened to me while trying to generate a route between llbg to klax... Share this post Link to post Share on other sites
phil747fan 44 Posted December 8 tried with 2 and 2.01 Share this post Link to post Share on other sites
phil747fan 44 Posted December 9 and it worked after i stopped and re started fpx 2.01 ... Share this post Link to post Share on other sites
