OnCourse Software

The project is still updated from time to time I think... Enjoy!

I had the same issue today flying into KDFW, logs attached.

I did use some time acceleration, but keeping a close watch on the nav display I did not appear to miss any waypoints as far as I can tell.

This lack of descent issue happens for me on most flights and is the one thing keeping me from being completely happy with PF3, all the rest is great. Hopefully a solution for this can be found.

regis902 wrote:

I had the same issue today flying into KDFW, logs attached.

I did use some time acceleration, but keeping a close watch on the nav display I did not appear to miss any waypoints as far as I can tell.

This lack of descent issue happens for me on most flights and is the one thing keeping me from being completely happy with PF3, all the rest is great. Hopefully a solution for this can be found.

Well you certainly seemed to have an interesting flight. When you were 103 miles from TYPTN (your 12th waypoint of 18) you hit terra firma!

You also requested a lot of altitude changes... from 34,000 to 37,000, from 24,000 to 23,000, from 23,000 to 17,000, from 17,000 to 13,000, from 14,000 to 10,000, from 11,000 to 8000 and from 9,000 to 5,000. All within a time period of 13 minutes and 100+ miles from your destination!

It then looks like P3D either crashed or you closed it down without first disconnecting PF3

Thanks for the response Dave. My thoughts/comments are below:

dmarch wrote:

Well you certainly seemed to have an interesting flight. When you were 103 miles from TYPTN (your 12th waypoint of 18) you hit terra firma!

That would have been my landing at KDFW RW17L, that distance from TYPTN is about right and my landing was the only time I touched down after take off.

dmarch wrote:

You also requested a lot of altitude changes... from 34,000 to 37,000, from 24,000 to 23,000, from 23,000 to 17,000, from 17,000 to 13,000, from 14,000 to 10,000, from 11,000 to 8000 and from 9,000 to 5,000. All within a time period of 13 minutes and 100+ miles from your destination!

Assuming 34,000 to 37,000 is a typo or in reverse, (I didn't request any cruise altitude increases), the other altitude requests were me trying to step my aircraft down as per the STAR I was following (DEBBB2). I only made these requests because PF3 did not issue descent clearances. I did input the STAR altitudes into PF3 using the altitude adjustment option, so PF3 in theory should have known what altitudes I wanted to be at for each waypoint on the STAR.

dmarch wrote:

It then looks like P3D either crashed or you closed it down without first disconnecting PF3

I did forget to disconnect PF3 before shutting P3D down, but that was long after I had landed and taxied to the gate on my own.

Thanks for that... I guess I need to delve into your log again... Interesting.

regis902 wrote:

Thanks for the response Dave. My thoughts/comments are below:

dmarch wrote:

Well you certainly seemed to have an interesting flight. When you were 103 miles from TYPTN (your 12th waypoint of 18) you hit terra firma!

That would have been my landing at KDFW RW17L, that distance from TYPTN is about right and my landing was the only time I touched down after take off.

dmarch wrote:

You also requested a lot of altitude changes... from 34,000 to 37,000, from 24,000 to 23,000, from 23,000 to 17,000, from 17,000 to 13,000, from 14,000 to 10,000, from 11,000 to 8000 and from 9,000 to 5,000. All within a time period of 13 minutes and 100+ miles from your destination!

Assuming 34,000 to 37,000 is a typo or in reverse, (I didn't request any cruise altitude increases), the other altitude requests were me trying to step my aircraft down as per the STAR I was following (DEBBB2). I only made these requests because PF3 did not issue descent clearances. I did input the STAR altitudes into PF3 using the altitude adjustment option, so PF3 in theory should have known what altitudes I wanted to be at for each waypoint on the STAR.

dmarch wrote:

It then looks like P3D either crashed or you closed it down without first disconnecting PF3

I did forget to disconnect PF3 before shutting P3D down, but that was long after I had landed and taxied to the gate on my own.

Ah right, I think I can see why things went amiss... this has already been addressed and will be in the next maintenance release which should be the end of the week.

I too seem to have the lack of descent instructions when approaching the destination, so I am glad to hear an anomaly has been identified!
Great program though, love it.

Good to hear, looking forward to it

I had a flight from EGKK to EGPH last night, I had ATC but was handed off the Essex Radar, who responded to my check in, but then nothing else! I checked the display tool for a list of commands I can use on the current frequency, which was none.

I looked at the say again window of last commands and the last entry was was Essex Radar confirming contact with my call sign.

Sadly I don't have any logs, I restarted my sim after my flight as I purchased MCE yesterday and wanted to test the commands out

Just thought I would mention that there maybe something a little strange occurring.

Regards Rob

Opps, just read above, this might be fixed then in the next update

helix1250 wrote:

I had a flight from EGKK to EGPH last night, I had ATC but was handed off the Essex Radar, who responded to my check in, but then nothing else! I checked the display tool for a list of commands I can use on the current frequency, which was none.

I looked at the say again window of last commands and the last entry was was Essex Radar confirming contact with my call sign.

Sadly I don't have any logs, I restarted my sim after my flight as I purchased MCE yesterday and wanted to test the commands out

Just thought I would mention that there maybe something a little strange occurring.

Regards Rob

Opps, just read above, this might be fixed then in the next update

Repeat your flight exactly and if the same problem occurs report it here with the attached logs. Just to be sure in case any future update dosn't address your precise problem.