OnCourse Software

Sabretooth78 wrote: *

Fri Dec 08, 2023 11:45 pm

Possible I'm just being ignorant of other features, but I usually modify these manually as the computed descent always seems to be too late.

Sabretooth78 wrote: *

Fri Dec 08, 2023 11:45 pm

Installed the latest beta (3.21.50) and now getting this "can't descent below current TOD" error:

Possible I'm just being ignorant of other features, but I usually modify these manually as the computed descent always seems to be too late.

The flight plan presets never seem to change this behavior so I've just gotten used to changing them manually; it often needs to be done anyway to meet STAR constraints - this example of CAMRN4 into KJFK being a good example. Needless to say, being unable to push the TOD back is an issue.

Screenshot 2023-12-08 183745.png

SkyCamel wrote: *

Sat Dec 09, 2023 7:38 am

Sabretooth78 wrote: *

Fri Dec 08, 2023 11:45 pm

Possible I'm just being ignorant of other features, but I usually modify these manually as the computed descent always seems to be too late.

To my big frustration I always have the exact problem. I don't think I should be modifying the calculated flight plan every time I load it into PF3.
What I can't wrap my head around is that when loading the flightplan you indicate the climb rate but also the descent rate for the aircraft you're using.
Also the speed. I putt my descent rate extra low to 1000 fpm for my fbw a32nx to make sure I get an "early descent, yet I always get a late descent.
PF3 knows my position, the distance to the airport I will be landing, my descent rate and the speed so it must be possible to calculate the TOD?

I know, this thread is about Beta releases and that's exactly the reason why I respond on this here. I can't undo myself of the impression (mind you, I certainly can be wrong!) that in earlier versions I didn't have that problem, or certainly not that frequently.
Cheers,
Luc

SkyCamel wrote: *

Sat Dec 09, 2023 7:38 am

Sabretooth78 wrote: *

Fri Dec 08, 2023 11:45 pm

Possible I'm just being ignorant of other features, but I usually modify these manually as the computed descent always seems to be too late.

To my big frustration I always have the exact problem. I don't think I should be modifying the calculated flight plan every time I load it into PF3.
What I can't wrap my head around is that when loading the flightplan you indicate the climb rate but also the descent rate for the aircraft you're using.
Also the speed. I putt my descent rate extra low to 1000 fpm for my fbw a32nx to make sure I get an "early descent, yet I always get a late descent.
PF3 knows my position, the distance to the airport I will be landing, my descent rate and the speed so it must be possible to calculate the TOD?

I know, this thread is about Beta releases and that's exactly the reason why I respond on this here. I can't undo myself of the impression (mind you, I certainly can be wrong!) that in earlier versions I didn't have that problem, or certainly not that frequently.
Cheers,
Luc

Sabretooth78 wrote: *

Fri Dec 08, 2023 11:45 pm

Installed the latest beta (3.21.50) and now getting this "can't descent below current TOD" error:

Possible I'm just being ignorant of other features, but I usually modify these manually as the computed descent always seems to be too late.

The flight plan presets never seem to change this behavior so I've just gotten used to changing them manually; it often needs to be done anyway to meet STAR constraints - this example of CAMRN4 into KJFK being a good example. Needless to say, being unable to push the TOD back is an issue.

Screenshot 2023-12-08 183745.png

SkyCamel wrote: *

Sat Dec 09, 2023 7:38 am

Sabretooth78 wrote: *

Fri Dec 08, 2023 11:45 pm

Possible I'm just being ignorant of other features, but I usually modify these manually as the computed descent always seems to be too late.

To my big frustration I always have the exact problem. I don't think I should be modifying the calculated flight plan every time I load it into PF3.
What I can't wrap my head around is that when loading the flightplan you indicate the climb rate but also the descent rate for the aircraft you're using.
Also the speed. I putt my descent rate extra low to 1000 fpm for my fbw a32nx to make sure I get an "early descent, yet I always get a late descent.
PF3 knows my position, the distance to the airport I will be landing, my descent rate and the speed so it must be possible to calculate the TOD?

I know, this thread is about Beta releases and that's exactly the reason why I respond on this here. I can't undo myself of the impression (mind you, I certainly can be wrong!) that in earlier versions I didn't have that problem, or certainly not that frequently.
Cheers,
Luc