OnCourse Software

CapatinAlex wrote: *

Fri Oct 28, 2022 7:12 pm

dmarch wrote: *

Fri Oct 28, 2022 6:32 pm

I think you already mentioned you have closed runways so that's the only way to be certain which one you'll get, but that has its own risks, because AI traffic can still use runways you might have set as being closed. You therefore run the risk of having AI traffic taking off/landing from the opposite end of your chosen runway... not very realistic.

Why do you need to preselect a runway?

Well, I would prefer it to instantly get my departure runway on first call like you do in real life
By the way, I am currently flying from BIKF to ENBR and I closed all the runways except RW 19. I checked it twice and also hit the save button afterwards but I still got runway 10 for departure! And when I requested runway 19, PF3 claimed this runway would be closed, even though it is the only opened runway by me, marked with B.
I hope you can find the problem, thanks in advance


Kind Regards

dmarch wrote: *

Sat Oct 29, 2022 11:21 am

CapatinAlex wrote: *

Fri Oct 28, 2022 7:12 pm

dmarch wrote: *

Fri Oct 28, 2022 6:32 pm

I think you already mentioned you have closed runways so that's the only way to be certain which one you'll get, but that has its own risks, because AI traffic can still use runways you might have set as being closed. You therefore run the risk of having AI traffic taking off/landing from the opposite end of your chosen runway... not very realistic.

Why do you need to preselect a runway?

Well, I would prefer it to instantly get my departure runway on first call like you do in real life
By the way, I am currently flying from BIKF to ENBR and I closed all the runways except RW 19. I checked it twice and also hit the save button afterwards but I still got runway 10 for departure! And when I requested runway 19, PF3 claimed this runway would be closed, even though it is the only opened runway by me, marked with B.
I hope you can find the problem, thanks in advance


Kind Regards

According to the log file you provided runway 10 was the only runway available.... here's the log file data. The 'Usage Set' entry indicates 0=normal use, 1=landing only, 2=takeoff only and 3=closed

Runway data for BIKF WP:0
Usage set to: 0
Rwy Num: 10
Rwy Ltr: 0
Rwy ILS: 0
Rwy Typ: 0
Rwy Lat: 63.98503
Rwy Lon: -22.65509
Rwy Hdg: 103
Rwy Len: 10023
FAF Lat: 64.02206
FAF Lon: -23.02484
--------------------
Usage set to: 3
Rwy Num: 28
Rwy Ltr: 0
Rwy ILS: 0
Rwy Typ: 0
Rwy Lat: 63.98504
Rwy Lon: -22.59245
Rwy Hdg: 284
Rwy Len: 10023
FAF Lat: 63.94425
FAF Lon: -22.22322
--------------------
Usage set to: 3
Rwy Num: 1
Rwy Ltr: 0
Rwy ILS: 0
Rwy Typ: 0
Rwy Lat: 63.96447
Rwy Lon: -22.6055
Rwy Hdg: 14
Rwy Len: 9996
FAF Lat: 63.80273
FAF Lon: -22.6979
--------------------
Usage set to: 3
Rwy Num: 19
Rwy Ltr: 0
Rwy ILS: 0
Rwy Typ: 0
Rwy Lat: 63.99187
Rwy Lon: -22.60547
Rwy Hdg: 194
Rwy Len: 9996
FAF Lat: 64.15356
FAF Lon: -22.51405
--------------------
End of data for BIKF WP:0

Quote:

There must be something wrong in the software

dmarch wrote: *

Sat Oct 29, 2022 2:59 pm

Ah, just checked you log file again and sure enough, on the SID/STAR page you have FS2020 data selected and it is those runways you are configuring/closing, but you are then running with FSX data because you are using XPlane. That's the reason why PF3 does not recognise you runway configuration.

Quote:

There must be something wrong in the software

There are certainly some things wrong with the software but this in not one of them!