Jim Robinson

I was hoping that might be the case! :smile:

Yep, and you could even take it a step further and add specially designated parking spots with ADE and line them all up in a semi-circle or something. I did that back in the FS9 days, I may have a screenshot...

OK I've seen the procedure turn! The flight was KBOI DNJ MQG KCOE, ILS 06 approach, HILIE transition. I'm impressed. It nailed it, pulled off the procedure turn and no problems transitioning to LOC1. Just when you're about to give up it delivers a flight like this! Started in Boise about 16:00 local time, killer dusk arrival at Coeur d' Alene with ASN doin' it's thing! :smile: BTW Ed, is there a chance the PL21 you're showing in the video might be somehow connected to a certain Citation XLS project in the works?

What I don't get from watching your video (thanks BTW) is when you dialed in 1700' for CILEB > BRENT your VSI bug didn't move. When I do that mine goes to -500 FPM automatically and then I just use the VS wheel to nose it over to -1000 or whatever I want. I see you hit the VS button, to this date I've never used the VS mode because I really haven't needed to. So I did that approach and did everything the same as you except I used the VS wheel instead of clicking the VS button, then when I clicked APPR it just kept turning itself back off. I briefly clicked the VS button then went straight for the APPR button again, that time it stuck and finished out the ILS beautifully. It looked like I had all the same announcements at the top of the PFD that I see in your video, APPR FMS AP ALT (your descent to 1700' was prior to you switching to LOC1), so I'm not understanding what altitude mode you had it in where dialing in the lower altitude didn't trigger it to automatically start descending at -500 FPM? I think your success and/or my lack thereof has something to do with clicking that VS button (or some button, as I mentioned earlier in the thread I've also been able to straighten out APPR by clicking the VNAV button). Is that possible? Is that what happened to you at PAKT? You were unable to activate APPR mode?

Can you give me an example of an approach/ILS where this works? I'd like to try it. I suspected things may work differently in FSX so I installed it there and did a few flights but TBH I see the same problems in FSX I see in P3D v3. The only difference I've noticed is that the IGN switches can be operated individually in FSX where left & right are tied together in P3D3. I have a problem every time going from FMS to VOR1 and there seems no set sequence of button clicks to make the transition successful, what works on one approach doesn't work on the next, etc. Thanks.

I didn't even see an announcement for v1.2 but I didn't see a problem with any textures or effects. This autopilot doesn't do the same thing twice from what I've seen. I can't see the point in even downloading v1.2. Last night I loaded an approach with a DME arc (ILS03, KABQ, NODME transition) and was surprised to see the AP actually flew the arc, I made it through the effed up "intercept" phase but unfortunately the flight was ruined when it came time to switch to ILS and I couldn't get the APP button to engage. I've done it 20 times but it wasn't happening this time. No danger of becoming a "child of the magenta" here, nothing like a hit & miss AP to keep you on your toes! I Ctrl+C'd out of the flight muttering a few obscenities on the way out. Later I ended up doing a couple flights in the CS 727, lol.

Note that what shows in the Preset field is what mode you'll be in after you click the button, not the mode you're currently in. It should say VOR1 before you click it, after you click it it'll probably say FMS. You have to use the DATA knob to make it say VOR1 first, then click the Preset button. TBH it was VMC and as Amelia Earhart (sorta) said "Left seemed the most attractive at the time", lol. I hadn't looked at the chart and I had "Left" stuck in my head, I was sitting there waiting for the AP to do something and when it broke right I assumed it was trying to double back on rwy heading so I turned on HDG hold and took over manually. Maybe the AP was trying to initiate the procedure turn correctly to the right [mild skepticism], I didn't hang around to see what happened. I'll have to try that one again and see what it does. EDIT: Nope, no procedure turn.

Of course you're addicted! :smile:

OK here's an example I just did, going into KGEG Spokane, WA from the west, I started at KEAT Pangborn/Wenatchee and did the ZOOMR1 arrival and ILS21 approach. To put that in the FMS you make a flight plan between KEAT and KGEG, then on the DEP/ARV page you select ILS21 followed by the ZOOMR1 arrival and EPH transition. I didn't mess with any waypoint altitudes in the FMS, I just climbed straight to 19,000' for cruise and descended manually to hit the FAF at 5500'. Charts here: ZOOMR1 ILS or LOC/DME RWY 2 If you load that in the FMS it sends you from GANGS to LUCEV which is the IAF and the chart says to hit LUCEV at 5500'. Since the turn between LUCEV and SIGYO is nearly 180° you'd do a procedure turn there (at least the GTN750 does one there). Apparently the FMS doesn't do procedure turns so it tries to double back on itself and swings so far off course it doesn't have time to line back up again before touchdown - anyway I expected this so I took over at LUCEV and did the procedure turn manually. I spun the HDG bug left to 360° (reciprocal HDG minus 30°) and turned on HDG hold crossing LUCEV, flew out for 1 min, and then turned back right to 210°. Oops, according to the chart I should have gone counter-clockwise, but something like this: Here's where I think the problem is, after clicking the HDG button to take over manually, the tooltip over the NAV button still says "FMS NAV (on)". Somehow HDG and NAV are both on at the same time, so just click the NAV button once to turn it off. So then I do this procedure turn at 5500', 200 KIAS and more or less roll out on rwy heading. While I'm turning I set the ILS freq 111.10 and change the nav source with the Preset button on the PFD (make sure it says VOR1 and not VOR2 before you click it, if you need to change it you can scroll it with the DATA knob on the DCP). Crossing LUCEV a second time I descend to FAF altitude 3900' before SIGYO, and hit the APP button. From there the AP captured the GS and flew a beautiful approach right to the inner marker. Maybe try that one and see if you can get it to work. Jim

It seems to me the problem is that when you switch between FMS and VOR1 using the Preset button on the PFD the NAV switch stays stuck on FMS Nav, I think just turning that off and back on again lets it switch from FMS NAV to VLOC NAV and then the APP button becomes available. I've made ILS landings with my FAF altitude value still entered on the ALT knob, APP seems to successfully override that once you manage to tickle everything in all the right spots. Also it appears once you switch the Preset button from FMS to VOR1 you also have to choose the correct CDI needle by clicking the NAV/BRG button on the DCP, then select the VOR1 needle with the Menu/ADV knob. Click the NAV/BRG button again to get back out. You'll notice I use a lot of terms like "it seems", "I think", "it appears", etc. :smile: I'm still trying to get this all figured out myself and the problem is every practice session is an hour flight at least, lol.

I successfully did one off off an FMS arrival/approach last night, I've noticed twice now though when you switch from FMS to VOR1 you can lock onto the localizer but the APR button wont stay on when you try to arm it for the glideslope. It just keeps turning itself off. Last night I clicked VNAV briefly and then after that for some reason I was able to click APR and it stayed on. It did a good job on the ILS once I got the combination right.

You have to capture the altitude you want manually. Get your initial climb sorted out with trim, pop open the AP window (Shift+4 I think) and press the AP button. Set your heading bug and then click the HDG button on the AP. Use the little rocker switch to increase/decrease climb rate. When you're 50' from reaching your planned altitude click the ALT button on the AP and it will level off and hold the altitude. If you want to climb or descend from there use the rocker switch to initiate the climb/descent and keep clicking down or up until you get your desired FPM, capture your altitude again 50' below your desired altitude (which means if you're descending you'll have to go slightly below your desired altitude, if you capture ie: 12,000' at 12,001' on the altimeter the AP will level off at 12,100' instead of 12,000' - you have to click below so wait for 11,999' before you click) To track the GPS plan you use the AP NAV button but you have to click the CDI button on the GNS430 so it says "GPS" as opposed to "VLOC". (this is simply the NAV/GPS switch) If that old ancient autopilot isn't doing it for you, you can replace it with a default AP which will behave normally with an altitude preset and all that.

If you type S47 into airnav.com it redirects you to KTMK so you could try that next time an airport doesn't come up.

S47 is now KTMK

The GTN has a switch to select whether the AP nav source is the GTN or the default GPS, you right click the blue SD card to change it and the tooltip tells you which is in use. By default when a GTN-equipped plane loads nav source will be set to use the GTN.

Near as I know Reality XP is dead in the water at FSX-MS. You said ou're using Steam Edition right? ...so I don't think you can use the RXP units anyway. Is that the case Bert? I put the GTN in the PC-12's normal Avidyne location, I have it on a pop-up too though and that's the one I normally use. I didn't want to lose my default GNS's and I hate the Avidyne, it looks like a bad Winamp skin from the late 90's to me, lol.

I can confirm some weirdness. There was a discrepancy between the VC gauge and the 2D gauge, one of them snapped the course needle to next waypoint and the other one didn't, can't remember which. I disabled Bert's gauges and reverted to the carenado defaults for a test and then both needles snapped to the course and as long as I was to the left of course the CDI deflection was OK but when I was to the right of course the needle stayed centered. I tested it once with the GTN completely removed so I know it's not interfering somehow. Bert's mods seem to work fine when the GTN is the nav source so I'm gonna leave it at that, lol. I installed it BTW by replacing Gauge_EFIS50_EHSI.xml and Gauge_EFIS50_EHSIVC.xml in the PC-12\panel\GAUGEPC12EHSI folder with those from Bert's latest fix (dated 7/12/15 and 7/27/15 respectively). I think in your case using the default GPS I'd be tempted to try and graft the HSI out of the default Lear or B738 into the panel or something.

I was using it with the GTN 750 in P3D v3, didn't try the default GPS, let me try it and see if I can reproduce the problem.

I bought the PC-12 during the xmas sale and just spent the last couple evenings making these mods work in P3D v3.1. There's a problem with prioritizing in P3D v3 where these gauges in subfolders of the panel folder don't get priority over the carenado-supplied .cab files in the P3D v3\gauges folder, so while you've installed the overhaul mod into P3D as you were instructed to do in FSX, you won't see the effects of the modified gauges because of this priority glitch in v3. The solution is to use the new P3D3 external content management system, you can do that 2 ways, first and probably easiest is to simply add the Prepar3D v3\SimObjects\Airplanes\Carenado PC12\panel folder as an additional gauge directory in the gauges.cfg giving it priority over the main gauges folder. I have not tested it this way for the record, it's just assumed it should work, lol. The gauges.cfg is located in C:\ProgramData\Lockheed Martin\Prepar3D v3 and by default it looks like this (opened in Notepad): [Entry.0] Title=Default Gauges Path=Gauges Required=True Active=True Path=Gauges is relative to the root Prepar3D v3 folder so it means Prepar3D v3\gauges or the main gauges folder as we know it, to add the PC-12 panel folder with priority over the main gauges folder you could edit the gauges.cfg like this: [Entry.0] Title=PC-12 Overhaul mod Path=SimObjects\Airplanes\Carenado PC12\panel Required=True Active=True [Entry.1] Title=Default Gauges Path=Gauges Required=True Active=True The 2nd way - I have an external content folder already set up complete with it's own gauges folder. My gauges.cfg looks like this: [Entry.0] Title=Addon Gauges Path=D:\P3Dv3 Addon Content\Gauges Required=True Active=True [Entry.1] Title=Default Gauges Path=Gauges Required=True Active=True D:\P3Dv3 Addon Content\Gauges holds gauges from several other aircraft that I have set up in the external content folder as well. All I did to make the overhaul mod gauges work was move the mod gauge folders from the PC-12's panel folder into my D:\P3Dv3 Addon Content\Gauges folder. The gauges.cfg was already edited so moving the folders was all that was needed. This has been tested and it works, it does give the modified gauges priority over the carenado-supplied .cab files and it accesses the .cab files for whatever it doesn't find in the mods folders (the mods folders contain only files that were changed, the rest are expected to be found in the .cab files). I hope that helps anyone that's trying to use the PC-12 + Overhaul mod in P3D v3. It's a great collection of modifications BTW, you guys did a great job and thanks :smile: Jim

Is it possible the power lever gets stuck when you exceed ITT at altitude for an extended period? I'm used to ramming the power lever full fwd above 18,000' or so and now I see my ITT is flashing and I'm over the redline which I guess is a result of the v1.8 overhaul mod. Since then I've been careful about not exceeding ITT (which means power lever is not full forward in cruise) and I haven't seen the power freeze-up since. :blush: Also I got a fix from Bert Pieke for the CDI deflection, send him and email and tell him to send you the same thing he just sent me. :smile:

Thanks for the comments guys! OK I got the suneffect working, the problem it seems was LensFlareCount="2" in the supplied suneffect.cfg vs LensFlareCount="10" in the default P3D v3.1 suneffect.cfg. Apparently LensFlareCount works differently in v3 vs FSX, I think the lens flare was actually working but the two flares were so jammed up against the sun you just couldn't see them. I let P3D build a new default suneffect.cfg and then I modified it to incorporate the needed changes taken out of the supplied suneffect.cfg. This seems to work, here's a link to what I came up with: p3dv31_navid_suneffectcfg.zip It goes in C:\ProgramData\Lockheed Martin\Prepar3D v3. You might experiment with LensFlareCount="xx", maybe LensFlareCount="8" would look better (open it with Notepad, change, save). I haven't tried 8 yet but 10 seems a little over the top sometimes. You need to have these .bmps: sun.bmp sunglow.bmp sunglow2.bmp ...from the download installed in your Prepar3D v3\texture folder to use this suneffect.cfg. Further, if you revert to the default suneffect.cfg later with those textures still installed the sun will look really huge and weird so backup your original textures or install a REX theme afterwards if you decide not to keep it. (there is no sunglow2.bmp in default P3D v3.1 BTW so you only need to back up sun.bmp and sunglow.bmp) To see the lens flare effect from the VC you still need to do the cameras.cfg modification as instructed in the readme and post #3 above. Easiest way to do that is press Windows Key+R, paste the line below and press OK. That opens the cameras.cfg in Notepad and the line you need to change is in the 2nd [CameraDefinition.xxx] near the top of the file (see readme). Change it, save it, you're done. notepad %appdata%\Lockheed Martin\Prepar3D v3\cameras.cfg You also need to put the 140 sky texture .bmps from the download into the Prepar3D v3\texture folder of course to complete the installation. Note that the suneffect mod is independent of the sky textures so you could also use the suneffect mod with HDE v2 or REX sky textures for example if you wanted to.

Note the package is for FSX and I'm not sure the suneffect.cfg mod works correctly in v3, it appears it breaks lens flare in P3D3 so I disabled it and only used the sky textures. The 5th screenshot shows the supplied suneffect, all the others are taken with a suneffect from REX4. More investigation on that is necessary because I really liked the suneffect, just didn't seem to be getting any lens flare, maybe I just didn't have the time of day right... ----------------------------------------------------------------------------------------------------------------------------- To use this package in P3D3 these amendments to the readme are necessary: 4. Put the "suneffect.cfg" into FSX main folder. 4. Put the "suneffect.cfg" into the C:\ProgramData\Lockheed Martin\Prepar3D v3 folder 5.1 Find your cameras.cfg in \Users\USERNAME\AppData\Roaming\Microsoft\FSX. 5.1 Find your cameras.cfg in \Users\USERNAME\AppData\Roaming\Lockheed Martin\Prepar3D v3 5.3 Go to FSX root directory and find "cameras.cfg". Do the same thing here as in step 5.2. (skip step 5.3 entirely, there is no cameras.cfg in the P3D root directory) ----------------------------------------------------------------------------------------------------------------------------- If you install the included suneffect.cfg and don't like it all you need to do is delete it, when you restart the sim it'll build a new one. Then close the sim and apply a REX4 theme with your own choice of sun effects. If you use these and like them make sure to head over to the fsdeveloper thread and give Navid a "like" :smile:

Navid's Sky texture set 2016 was released yesterday in this fsdeveloper thread: http://www.fsdeveloper.com/forum/threads/navids-sky-texture-set-2016.436022/ Definitely worth a look IMHO, so far I've just flown a couple flights with them in P3D v3 but I'm really liking these!

I have experienced both problems you mention (in P3D3). I think Bert has a fix for the CDI deflection. I have no idea what's up with the power lever, last time it happened I pulled it back to idle and minimized the sim to the desktop, fiddled around with ASN for a second, then when I went full screen again the power dropped to idle. Very irritating when VCALC tells you it's time to descend and you can't because you can't reduce power to avoid overspeeding. May as well be an OOM, the result is the same (ruined flight). :smile:

I'm using it in P3D3 and haven't noticed any problems. I'm not sure if they updated their installer since I downloaded but IIRC I selected to install into P3D2 and then on the next screen it allows you to select a folder so I just directed it to the P3D3 folder instead. Not sure if you'd see the P3D2 option in the installer though if you didn't have P3D2 installed.