Mklemme 9 Posted September 18, 2016 Share Posted September 18, 2016 Hello, I recently updated from v1.26 to v1.28 and noticed that route planning now doesn't seem to be wind optimized anymore. I was planning a flight KSFO-RJAA and chose Minimum Fuel (MFT) under Find Route, Advanced Route Planner. The result gave me a routing very close to the GC with a headwind of 84kts. I then tried Minimum Time and Minimum Distance options just for fun and got exactly the same routing, fuel burn and enroute time as for MFT. The attached screenshot shows the results for these three scenarios. In addition I also computed a flight using one of today's KSFO-RJAA routings from Flightaware. This gave me a much more southerly track avoiding the jetstream with flying time and fuel burn of 45 minutes/20,000lb less than under the PFPX ' optimized' plan (see last listing under results). Wind optimized routing seemed to be working well with v1.26, is there a new setting or option that I need to set to have this back in v1.28? Many thanks Kind regards, Michael. Please login to display this image. Link to comment Share on other sites More sharing options...
ken91410 0 Posted November 23, 2016 Share Posted November 23, 2016 Same here Can i downgrade to v1.26? Link to comment Share on other sites More sharing options...
chkl 34 Posted November 29, 2016 Share Posted November 29, 2016 Here too. I'd like the wind option back. Link to comment Share on other sites More sharing options...
CS-TMT 11 Posted November 29, 2016 Share Posted November 29, 2016 +1 here! Link to comment Share on other sites More sharing options...
charlie360x 0 Posted January 1, 2017 Share Posted January 1, 2017 Any hotfix please? Link to comment Share on other sites More sharing options...
tyda0501 0 Posted January 4, 2017 Share Posted January 4, 2017 On 1/1/2017 at 4:57 PM, charlie360x said: Any hotfix please? +1 Link to comment Share on other sites More sharing options...
vallewipp 4 Posted January 7, 2017 Share Posted January 7, 2017 Did you try to lay the wind chart over your actual FPL? Above the map third symbol from the right! There you see which wind conditions you have. And for your flight from KSFO - RJAA the system is exactly doing what it should. Planning along the PACOTS. Those are changing, like Nats and Ausots every 12 hours according the wind. Greetings Link to comment Share on other sites More sharing options...
FlightSimSoft.com 283 Posted January 8, 2017 Share Posted January 8, 2017 Not sure why it was removed form last update, but the feature will be back with next release again - should already work again with hotfix 1.28.7 Link to comment Share on other sites More sharing options...
ken91410 0 Posted January 8, 2017 Share Posted January 8, 2017 Thx FlightSimSoft team reply but 1.28.7 not helping me Please login to display this image. Link to comment Share on other sites More sharing options...
ericu65 0 Posted January 18, 2017 Share Posted January 18, 2017 Was about to report this. Wind optimized route still not working. Can you check please? Link to comment Share on other sites More sharing options...
Skyrock 4 Posted January 21, 2017 Share Posted January 21, 2017 Even with the latest hotfix (1.28.8) the problem persists. Also the turbulences are not shown on the printed charts anymore. Could bring both features back please? Link to comment Share on other sites More sharing options...
VHOJT 57 Posted January 30, 2017 Share Posted January 30, 2017 Hi guys, Any word on this issue? Cheers, Rudy Link to comment Share on other sites More sharing options...
FlightSimSoft.com 283 Posted January 30, 2017 Share Posted January 30, 2017 Will have a look on that... Link to comment Share on other sites More sharing options...
Mklemme 9 Posted January 31, 2017 Author Share Posted January 31, 2017 Hi Christian, I have done some further testing with long-range flights and provide below a few observations that might help you track down the issue/resolution. 1. Flights involving defined tracks- ie NAT/PACOTS. If there are defined tracks in place between departure and destination, PFPX (using optimize route/minimum fuel track) will usually choose the track which is closest to the GC between departure and destination and not necessarily the most fuel efficient track. See below example for ANA7, KSFO-RJAA. PFPX (using Minimum Fuel Track) chose track F which is close to the GC (in yellow), resulting in an EET of 11:15, a wind component of -68kts and 82.7t fuel burn (left picture). The track actually used by ANA7 that day (as per Flightaware) was much further north (track C-right picture) giving a much lower wind component (-37kts) and shorter trip time/reduced fuel burn notwithstanding the much further ground distance of this routing. However, I've noticed that even with defined tracks, if the tracks have a longer ground distance than the GC (ie by say 3-4%) then PFPX auto routing will ignore the tracks and develop a random track close to the GC. Please login to display this image. Please login to display this image. 2. Flights not involving tracks. For routes without defined tracks (ie polar routings, North Atlantic above the OTS) PFPX always seems to generate a random routing more or less along the GC. See example below for UAL58 KSFO-EDDF. Left picture show PFPX derived track using optimize route, minimum fuel track, which is more or less along the GC. En-route time is 10:31, fuel burn 232klbs and wind component of zero (rare to see that!). Right picture shows the routing actually used by UAL58 this day, much further south picking up some tail wind, resulting in shorter flight time (10:15) and reduced fuel burn (228 klbs). In fact, I have planned this flight numerous times (>10) over the last month and PFPX invariably gives me the exact same routing every time (ie in the left picture below) no matter what the jet stream pattern for that day is. Please login to display this image. Please login to display this image. Hope the above is helpful and you are able to restore wind optimization within PFPX. Kind regards, Michael. Link to comment Share on other sites More sharing options...
vallewipp 4 Posted February 1, 2017 Share Posted February 1, 2017 Hi Michael, outstanding work. i saw the same when planning flight from DXB-HKG and back, that for the flight to HKG it took a GC near route and lucky me i had good tailwinds there, but on the way back, a much further south routing would have been by far better, as there was less HWC. But it planned a route directly in the wind... so fuel burn and flight time was much higher, than a cost, time and fuelburn optimized route. Link to comment Share on other sites More sharing options...
chkl 34 Posted February 16, 2017 Share Posted February 16, 2017 Routes for me are just like others above. Not taking winds into account. Support for this app has almost disappeared and I paid for a new year of weather. Link to comment Share on other sites More sharing options...
Anders737 0 Posted February 19, 2017 Share Posted February 19, 2017 I have the same problem with 1.28 This was the number one reason that I use PFPX, but now it seems to pick the shortest route no mather what the wind is like. I really hope you fix this soon, as a bought a 365 days subscription, and now it seems useless really. Thanks. Link to comment Share on other sites More sharing options...
dashcapt 5 Posted March 19, 2017 Share Posted March 19, 2017 Hi Was this issue every resolved. I still have this problem. Thanks Link to comment Share on other sites More sharing options...
VHOJT 57 Posted March 21, 2017 Share Posted March 21, 2017 Some sort of update on the issue from the developers would be good Cheers, Rudy Link to comment Share on other sites More sharing options...
FlightSimSoft.com 283 Posted April 10, 2017 Share Posted April 10, 2017 There will be soon a new version which includes this feature again... Link to comment Share on other sites More sharing options...
B777ER 8 Posted May 10, 2018 Share Posted May 10, 2018 Was this ever fixed with 128.9i? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.