Post by Tom/CalClassic on Feb 16, 2019 17:09:16 GMT -5
I had one more test to make with the FS9 version, and that was to check that it still worked in FSX. Now that I fixed my sound I ran that test this morning and I made a successful AP linked GCA voiced approach to KSAC runway 2 with no problems. So the gauges have now been tested in both FS9 and FSX (but certainly not exhaustively).
I edited three XML files that were included in your flightsim.com Generic GCA upload - if there have been any changes since then they are not in my gauges. For example, I have not made any of the changes suggested by D5turbi in this SOH thread (I don't know of any other SOH threads):
Is there any chance of a FS9 version? I note that Tom seems to have it working. APC gets me to the intercept point but then it orbits as Phil found.
Personally, I'm really only likely to use the GCA element which would be a very welcome addon. As I don't even use existing FS9 ILS where none existed at the time, the "synthetic" version has no appeal!
PS - Happy to just edit the xml's if you point me in the right direction. And to beta test if still needed.
Last Edit: Feb 21, 2019 12:38:49 GMT -5 by Defender
Thanks Tom and looking forward to seeing how it works for FS9.
First issue is where to put it. Windows 0-9 are occupied in the Connies and the views menu is awkward to use so an icon or click point might be useful. Am I correct to assume that the control gauges zzDAT37 and apsmall will still function when the window is closed?
Post by Tom/CalClassic on Feb 22, 2019 15:42:21 GMT -5
Yes, eventually an icon might be useful. For now the first release will be the FSX version ported to FS2004 without any changes.
Yes, the AP and the entire GCA sequence will run fine with that subpanel closed, as long as you have brought it up at the start of the approach, assigned the proper airport and runway, and started the approach sequence by clicking the APC on the apsmall gauge. Then it can be closed and forgotten about.
It is easy to create as many icons for pop-up windows as you want using David "Opa" Marshall's Creating Icons & Popup Windows - an Illustrated Tutorial - Corrected Version - on Avsim and probably Flightsim. Make the bitmap file black - that is transparent - and then place it over a gauge in your vc (i.e. with the same coordinates) - rpm and manifold pressure gauges are pretty useful. The following entries in my L1049 H panel call up the sextant, engine status panel, driftmeter, astrocompass and Synthetic ILS (perhaps soon to be replaced by GCA). The small cab files in my Gauges folder are called sextant, statusg, etc. Hope this helps.
I have now installed the GCA and the final entry currently reads: gauge58=gca!gca, 360,20,150,150
In the Super Connie it is opened by clicking on the right hand manifold pressure gauge. The only difference between this and the Synthetic ILS is that this gauge is visible when the panel opens whether Visible in the panel entry is set to 0 or 1. I suspect this has something to do with the presence of the new sound gauge, but it is hardly a problem. David Marshall gave very clear instructions on how to make these little gauges and with practice it can be done in about 5 minutes. A first attempt will take longer because of the need to read what he says and to be careful with the editing of the small xml file he supplies. I can, however, supply my gca.cab to anyone who would like it and messages me with an e-mail address.
Last Edit: Feb 23, 2019 4:29:29 GMT -5 by connieguy
Tailspin gives a detailed account of the development of GCA in the download which includes the GCA gauge, but forum members may possibly also be interested in an article which appeared in Flight for 11th July, 1946, pp. 47-9. This has a number of interesting photographs and confirms that the talk-down began when the aircraft was about seven miles from the runway at a height of about 1500 feet.
Hi! Resurrecting this thread because I have implemented some improvements (I hope) for a V2.1.
New in V2.1:
- quick sound setup test - menu items grayed out when not ready - activation of autopilot at user's discretion [Ken's point] - 'semi-automatic mode' now available for both Pattern Control and Precision Approach - better setup options for straight-in Precision Approach - improved sequencing of glidepath and centerline callouts [could be a major improvement, following a suggestion by a RL calibrator pilot] - synchronized heading callouts in autopilot and manual modes [could get a mixed reception because it allows seemingly negligible 1-degree corrections] - "slightly above/below glidepath" added to callouts - left/right orientation bug added to centerline offset number [small thing, but a huge help when piloting manually] - revised manual [many changes]
Feel free to test. Looking forward to comments/suggestions.
Hello Manfred. Thank you very much for the new version of your gauge. I much appreciate the fact that the autopilot is now not turned on automatically immediately one contacts APC. I give below the trail of a test flight I did taking off on Runway 02 of LFPO and doing a circuit which ended up with a landing on the same runway.
I flew north until I was about 25 miles away from the airport and then turned south. At a distance of about 25 miles I selected Runway 02 on the gauge, set the intercept distance at 10 miles and then contacted Alice. Once she was in contact I closed the gauge and flew manually simply with her verbal instructions. She eventually put me on a heading of 202. the reciprocal of the runway, and then turned me to 112 and 032. As you can see I did not perform this turn quickly enough and ended up well to the right of the glide path. At this point I was handed over to PAR which did not correct the extent of my error. However, I note that the manual says that PAR cannot handle complex approach patterns and that therefore the pilot must be on a viable straight-in line, which I was not. Apart from turning more tightly is there anything more I could have done, such as setting a bigger intercept distance? I realise that if I had left the gauge open I could have seen how far I was off track and corrected the error in that way.
Last Edit: Oct 17, 2019 4:51:25 GMT -5 by connieguy
Ken, two things that we might look at, 1) Alice should have left you more or less at the end of the ILS arrow of 02, so something is certainly wrong at that point, and 2) it seems that PAR guides you to the runway, which it shouldn't either, it's aim being getting as close as poss to the centerline extension. As at that point it is a straight-in approach, not even a dogleg, it should have handled that easily, too. I'll try to replicate the flight two ways, once in auto learn mode, and once without it.
Edit, Did the more or less identical downwind LH circuit approach in auto learn mode, setting a 10-mile intercept. Nothing really remarkable, as you can see in the pic below. PAR handover established, I am about to reach the intercept at the required height of 3500 in a moment i.e. 0.3 miles), and will be told to "begin descent" in a few seconds. Already, with 10 miles to go, I am well aligned with the runway. Note, doing this in P3D 4.5, so the field parameters may be slightly different in other versions. Anyway, won't do the manual version because it can't possibly be any different, except for pilot clumsiness, which I am in no hurry to display here...
Probable cause of the discrepancy between your flight and mine very likely is the setting of a faulty intercept distance: I believe you may have inadvertently set 0.1 miles instead of 10 (hint: double check the distance indicated in AILA, easy to set 0.1 by mistake instead, another clue is the advised intercept height). At any rate that would fully explain the "odd" final course sets in your picture. (For some reason my p3d won't draw the flight path taken so I posted the above pic instead.)