jimmy64

Presently I have FTX Global, the free airport pack and two add-on airports, FSDT LAX and LatinVFR SAN, in the Southern CA area. I've just bought and I'm downloading So CAL now. Do I need to uninstall anything first before installing the region? I also have UTX2 installed.

Very cool!

Hey all. I've installed two Flight1 GTN 750's in the Duke. One has a male "TAWS system test okay" voice, the other a female. In the past I was able to find the menu to change between the two very easily, and now I can't find it anywhere. Was the option removed in an update?

Thanks everyone, it's working perfectly with the 1504 navdata.

Okay I didn't have the latest installed. Had it, but installed the older one when I moved to 3.1. Hopefully that'll do it. Will try after work. Thanks Ryan, I will if it doesn't work.

TERM then LPV affirmative 1405 (latest for the GTN Trainer afaik) The OBS changes to SUSP during the procedure turn (FITPA to FITPA), then back to OBS once crossing FITPA the second time.

Same results in the Turbine Duke, test is okay, no vertical guidance on approach. The trainer has the exact same data as the unit in the planes. When selecting an approach to fly, I see for example, RNAV 01L LPV, however, under CHARTS, it's RNAV 01L. LPV is not added to the chart. I don't know if it makes a difference because when looking at the Skyvector charts for KTPA, LPV is not on the chart there either. I now think that it's an error with the unit after update after update without a full reinstall. Thanks Scott, I'm sure that I'll get to the bottom of it. Good to know that LPV does work in the 182 for someone.

Thanks for responding Bert. The HSI does show the glideslope indicators on the test page. Still no indicators during the approach. Loaded and activated the 01L LPV approach via PIE with NAV engaged at 2600. Lateral guidance is perfect, aircraft does the procedure turn at FITPA, turns and lines up to cross FITPA for the approach. LPV is indicated in green, CDI on GPS, NAV in the autopilot. Once again the glideslope indicators fail to appear and the plane follows lateral guidance only. Since they appear on the test page, my guess is there is a problem with data. When loading an approach, the LPV is present along with all the others, but, when looking for it under CHARTS, it is not there.

I'm having trouble getting LPV verticle guidance. Verticle guides never show up on the HSI. Using GPS mode and an active LPV approach. The aircraft follows lateral guidance under autopilot but just flies right over the airport. Tried NAV and APR mode both with the same result. I must be doing something fundamentally wrong or LPV doesn't work in 3.2. Hopefully someone who successfully has flown an LPV can give me a scenario and a couple pointers so I see how the GTN works with the A2A autopilot.

+1 for those whose FPS tanked in heavy clouds post B5919 in 3.2. Deleting the shaders folder seems to have helped somewhat. I'm back to 30 fixed in heavy clouds.

31 pages! Simply not enough time in my day, synopsys please, anyone...

34 seconds for default scenario: Sandy-E @ 4.6, 50 Gb SSD caching (1 TB WD Black for primary storage) and memory running at 1667.

Good to hear, may have to give this one a try.

Anyone know if it will work with and interact with MT6?

RIC

Delta virtual (Deltava.org) allows "old school pireps." You can do that or use ACARS. Their codeshare partnership with Alaska Airlines allows you to fly that Q400 all over the west coast. Further, fly on PilotEdge. I'm sure you'll have no need to "prove" anything to anyone after successfully flying a route on the network.

Thanks Scott, got it up and running. Great little tool!

I've tried connecting this app to P3D but so far no luck. It does say FSX all over the place but I thought I'd try to get the exe installed on the computer to recognize P3D, it did right away. It displays connected and shows the coordinates for my aircraft. The app on the phone, however, does not connect to the computer. There are very few settings, but the last under Options is to "enable FSX Sim GPS". At any rate it doesn't connect to the computer and the option turns itself off. Any one get this to work?

I experienced better performance from both upgrades, 2.4-2.5 and then 2.5-3.1. No CTD with PMDG 777. This is finally the version I fly, not toy with to get better performance. If it ended right here I'd be set for years.

Buttons.

I think that it is hardcoded and not a configuration. I am manually trimming the aircraft when suddenly the trim wheel speeds up on it's own, unless I can immediately grab it and go the other direction. My workaround for now is to pull my view back so that I can see the wheel and the attitude indicator at the same time. This way if it starts to take off on me I can immediately see it and respond. Still, I would like to just manually trim my aircraft while looking out the window if I like, right now that is impossible. I've reassigned trim to a button on the joystick. It works fine. Still would rather have a rotating wheel but the metal wheel on the X-55 is a no go.

I use the silver rotating wheel on the Saitek X55 but it happens with the keyboard too.

I looked for Auto Trim in the cfg but I did not see that entry. Maybe a registered version of FSUIPC would help.

Maybe this should be in another area, controllers perhaps. It is, however, not a controller issue. The same thing happens with the 1 or 7 key. It is a program function that speeds up the trim wheel after it has been moved enough. It will trim, all the way up, or all the way down,without any further input. This function is very annoying and deadly in a real scenario. Surely someone knows what I'm talking about.

Looking for an answer to this too.