OnCourse Software

If my understanding of the way PF3 works is correct all VORs/NDBs in the flight plan should have HOLD check boxes available. I am finding that very few VORs/NDBs actually are being enabled to be set up for a HOLD

e.g LFPG MTD KOPOR ----- DET EGSS

I would expect MTD & DET to be available as HOLDS but they are not

Thanks in advance

musky wrote:

If my understanding of the way PF3 works is correct all VORs/NDBs in the flight plan should have HOLD check boxes available. I am finding that very few VORs/NDBs actually are being enabled to be set up for a HOLD

e.g LFPG MTD KOPOR ----- DET EGSS

I would expect MTD & DET to be available as HOLDS but they are not

Thanks in advance

Even with "% holds" turned off in options1 you should still get the clickable squares for MTD and DET. It works fine in my PF3.
Try deleting the flightplan and the waypoint adjustments altogether. Recreate them and then rerun PF3 and see if it works. Does it happen with any other fpl?

vololiberista wrote:

musky wrote:

If my understanding of the way PF3 works is correct all VORs/NDBs in the flight plan should have HOLD check boxes available. I am finding that very few VORs/NDBs actually are being enabled to be set up for a HOLD

e.g LFPG MTD KOPOR ----- DET EGSS

I would expect MTD & DET to be available as HOLDS but they are not

Thanks in advance

Even with "% holds" turned off in options1 you should still get the clickable squares for MTD and DET. It works fine in my PF3.
Try deleting the flightplan and the waypoint adjustments altogether. Recreate them and then rerun PF3 and see if it works. Does it happen with any other fpl? If so there might be something wrong with your PF3 installation.

The problem occurs with pretty much all my fps, occasionally I get click box on 1 of the VOR/NDB but most of the time it is as you see it.

I should add I am using Aerosoft FlightSimm Commander 9 to create FPs.

I am wondering if perhaps something is leftover from the DEMO version is causing some issues although I did remove it. Maybe a complete removal and reinstall is required.

I have another peculiar issue concerning oceanic airspace that I am going to post in another topic that I have not seen mentioned in any other post in the forum

Please attach a zipped flight plan.

I use FS Commander as well. One of the quirks of the programme is that if a waypoint VOR coincides with an intersection, FS Commander considers the waypoints to be intersections, not VORs. If you look at the pln file you will see they are designated as I rather than V.

Quote:

waypoint.0=, KCLE, , KCLE, A, N41* 24.53', W081* 51.09', +000791.00,
waypoint.1=KK, APE, , APE, I, N40* 09.06', W082* 35.29', +000000.00,
waypoint.2=KK, HVQ, , HVQ, I, N38* 20.98', W081* 46.19', +000000.00,
waypoint.3=KK, HMV, , HMV, I, N36* 26.22', W082* 07.77', +000000.00,
waypoint.4=KK, GIBSS, , GIBSS, I, N35* 59.71', W081* 50.31', +000000.00,
waypoint.5=KK, SPWAY, , SPWAY, I, N35* 49.10', W081* 43.39', +000000.00,
waypoint.6=KK, SHINE, , SHINE, I, N35* 36.52', W081* 35.22', +000000.00,
waypoint.7=, KCLT, , KCLT, A, N35* 12.84', W080* 56.58', +000745.00,

In the above pln, APE, HVQ, and HMV are VORs but the "I" after the waypoint designator means FS Commander has used the intersection, not the VOR. PF3 will therefore not allow a hold there.

Two ways around this. You can force FS Commander to use the VOR rather than the intersection (tedious), or you can manually change the "I" to "V" in the pln file and re-save it. Once the "V" is present, PF3 will allow a hold at the VOR. Sorry for the trouble but it's an issue with the flight planner.

Dan77, this is what I remembered, too, but I did not want to blame FSC9 before seeing the flight plan
I used FSC9 in the past, but switched to PFPX.

SOLVED! Thank you to all who responded to my issue.

The problem was as suggested in the previous posts FSC9 and the plan containing the Intersection rather than the VOR even though it displays the VOR frequency. On changing waypoint type from "Intersection" to "VOR" for MTD and DET and PF3 displayed the hold check boxes.

One other intriguing question I have is that if you change the waypoint type of an actual Intersection waypoint in the flight plan to VOR the hold check box is displayed next to the intersection. Would this be a workaround way of getting PF3 to hold aircraft at intersections as well as VOR/NDB.

If no one knows the answer to this I will try tomorrow and report back

Thanks again

musky wrote:

One other intriguing question I have is that if you change the waypoint type of an actual Intersection waypoint in the flight plan to VOR the hold check box is displayed next to the intersection. Would this be a workaround way of getting PF3 to hold aircraft at intersections as well as VOR/NDB.

Yes, I do believe this works as an unofficial workaround. There has been some discussion about expanding PF3's hold feature to allow holds at intersections and fixes, and this may be implemented in a future release.

ThomasAH wrote:

I used FSC9 in the past, but switched to PFPX.

Hope to get PFPX but I'm still saving my pennies! Is it ever on sale?