Airj247 8 Posted August 3, 2017 Share Posted August 3, 2017 I was flying into Las Vegas at an altitude of 37000, I had no TOD indicator on the map prior to my next wpt, which had a restriction of 23000, once I passed the wpt I finally got a TOD indicator on my screen. Am I messing something up? Link to comment Share on other sites More sharing options...
Clorix 6 Posted August 4, 2017 Share Posted August 4, 2017 Was the restriction at or above FL230, at FL230, or at or below 23000? If it was at or above FL230, then that would be in compliance since you were above at that point. Link to comment Share on other sites More sharing options...
Airj247 8 Posted August 4, 2017 Author Share Posted August 4, 2017 Ok, I think I had to be at FL230 but I don't remember this might also be just me being a noob. Link to comment Share on other sites More sharing options...
Clorix 6 Posted August 4, 2017 Share Posted August 4, 2017 Do you remember what route you used by chance? The only FL230 restriction I can find going into KLAS is on the SITEE1 arrival, GGAPP transition, a restriction of "at or above FL230". Link to comment Share on other sites More sharing options...
Airj247 8 Posted August 7, 2017 Author Share Posted August 7, 2017 I don't remember, but I recently flew into Ottawa, and on the star I had a restriction of 8000B (was at FL230), the TOD was ON the wp with the 8000B restriction. Maybe I setup wrong but I had the TOD before. (I did modify and the restriction wasn't there before, still wouldn't of had enough time to get to 3000 from Fl230.) Link to comment Share on other sites More sharing options...
PineappleWizard 44 Posted August 7, 2017 Share Posted August 7, 2017 I've had this too, where I'm at FL380 and supposed to be below FL270 at the next waypoint and yet TOD is after that waypoint. Link to comment Share on other sites More sharing options...
JRBarrett 675 Posted August 7, 2017 Share Posted August 7, 2017 I think this is being worked on for the next update. Link to comment Share on other sites More sharing options...
blahhh 41 Posted August 10, 2017 Share Posted August 10, 2017 Hi Does something have changed in the 1.0.0.5 update? I still have this issue and I don't know if it's usefull to report details or not, I'm not sure that is a priority. Let me know. cheers Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted August 10, 2017 Aerosoft Share Posted August 10, 2017 Link to comment Share on other sites More sharing options...
Hans Hartmann [OLD] 1419 Posted August 10, 2017 Share Posted August 10, 2017 6 hours ago, blahhh said: Hi Does something have changed in the 1.0.0.5 update? I still have this issue and I don't know if it's usefull to report details or not, I'm not sure that is a priority. Let me know. cheers No, I didn't touch that yet, simply because most VNAV issues are ultimately caused by bugs in the LNAV part. Depending on whether more reports on LNAV come in or not, I'm going to take a thorough look at distance/time/fuel and VNAV over the weekend. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.