Jump to content

Cavulife

Registered Users
  • Posts

    227
  • Joined

Posts posted by Cavulife

  1. Changing the G1000 CDI mode from GPS to LOC1 for example will now disconnect the autopilot NAV mode - on the annunciator bar at the top centre of the screen, GPS will change to ROL.

    After changing CDI mode from GPS to LOC1, you need to click again on the autopilot NAV button, and then the APR button to capture the glideslope.

     

    I don't understand how we can be getting such different results on these things. I just tried David's flight from KHEG to KJAX ILS 26. Loaded the approach on the ground. Flew GPS with the AP to about 1 mile before TIKRY then manually switched the CDI to LOC1. The AP continued flying to intercept the localizer (it didn't disconnect). I pushed APPR about 1 mile before DALTN and it intercepted and tracked all the way down.

     

    I don't get it.

  2. Yes, when i choose KBEH I choose the ILS28. The CDI never changes to green. I get the GP on the display. I choose APR for the autopilot at MALLY. Now i can get it to lose altitude but it just doesn't want to fly the slope correctly. I set up the approach speed around 62 kts. at MALLY before I hit the APR button. i have tried the ILS approach on 5 different airports. None of them work as they should. The plane stays on approach altitude till i select VS and do a descent by losing altitude. i have tried everything i can think of. it is a mystery to me. The XBOX version is screwy.

     

    If the CDI never changes to green then it's not VOR1 so it won't track the GS. If you "Loaded" the Approach after selecting it then it should change to the VOR1 for you. You can manually change it at the bottom of PFD. Each time you press CDI it steps through VOR1, VOR2, GPS...

  3. i want to make sure I understand this. When you got to MALLY the GS worked and the plane descended from 2200' to runway on the glideslope. Correct? i get the GS indication but the plane never descends and no green localizer ever appears. i have to land manually every time.

     

    Yes, the autopilot took the plane down the glide slope correctly on both flights. I can’t figure out anything you could be doing wrong since it’s pretty straight forward.

     

    You are selecting the ILS 28 procedure, not the RNAV correct? Does the CDI show as green after MALLY?

  4. Page 177 of MFS2020 Flight Manual. KBEH, STYLE Departure, Altitude 5000', Waypoint ZUBIV, 3nm from ZUBIV descend to 3000' as directed by ATC, HOLD, WOVKA, 5 nm from MALLY manually descend to 2200', at MALLY CHANGE Autopilot mode to APR (approach) NAV should be set to 108.50 IBEH identifier. Good luck, I have only got the vertical to work once when initiated APR.

     

    I don't know how to enter the Departure so I used the World Map Planner to go IFR from KBEH to KBEH for an ILS 28 Approach. It set up a big arc and went through WOVKA, MALLY. I flew the first part manually and approaching WOVKA I switched the PFD to VOR1 and then engaged NAV mode. The localizer and GS both worked.

     

    Then I tried a GPS Direct flight from KLWA to KBEH via 40C. Used NAV mode after takeoff and selected the ILS 28 Approach from the PFD and loaded it. The autopilot took me via 40C and then on to WOVKA (though it said MALLY) then MALLY. Localized and GS worked.

  5. What does it mean when pilots tell ATC they are/have “golf to land”? Ready to land? I’ve “googled” for a precise definition without any luck?

     

     

    Sent from my iPhone using Tapatalk

     

    When you get the ATIS for your destination it will start with something like “Information Golf 2200 Zulu weather”. These are updated every hour and they go in alphabetical order: Alpha, Bravo, Charlie…

     

    Golf is just one of those. If you call the tower and say you have “Foxtrot”, they would know that you had the previous weather report, not the current one.

  6. The GPS will not take you to the approach. You will probably be assigned your selected runway by the tower, but that may not correspond to the current wind.

     

    You can select an approach on the the GPS when you're in the plane and it will navigate you through the approach points. Just make sure you have an intermittent waypoint in your plan and you select an approach BEFORE reaching that waypoint. If you don't do this you may get routed back to the previous waypoint before continuing to the first approach waypoint.

  7. On some aircraft C172 C208 CJ4 for example, the button light no longer lights up to indicate AP NAV HDG, etc... They function, but no indications that they have been selected. They all USED to work and still do on some aircraft, but now not on those I just listed.

     

    Anyone else seen this??? I saw an old complaint in FSX, but not applicable to MSFS.

     

    Really annoying.... could have been an earlier update, since I might not have flown those above for some weeks....

     

    Anyone???

     

    Are you SURE that all of these used to have lights? I do get the lights on the C208, but I just checked the C172, CJ4, DA40NG and Bonanza and I get no lights and I don't really see a spot for the light like on the C208.

  8. Have I mentioned there's no manual for MSFS, at least not one that actually gives you any info on how to fly the planes? (Rhetorical question.)

     

    Anyway, I am trying to up my skills to the next level, which I do by blundering around with buttons on the panel while I'm on AP. So I was in the King Air, flying a GPS route from KDEN to Jackson Hole (KJAC). Nearing KJAC, I decided to fiddle with the settings in the right-hand screen, and pushed "PRO." This produced the display I attach here. This looked like the screens I've seen in YouTube instructional videos for the CJ4, a hopeful sign. So I clicked on "Load and Activate." My King Air then left the GPS route, but did not follow the path traced by those waypoints. Instead, it went to 315, heading for nothing -- at least not KJAC. I then changed my CDI to VOR1. No effect.

     

    So I deactivated the autopilot and started to fly the approach pattern on the screen. Being a polite sort, I contacted the KJAC tower, but they told me to "Fly left traffic, Runway 21" -- in other words, land to the south, directly opposite the approach on my screen.

     

    Is the AP supposed to follow the approach generated by the panel? If so, how can I get it to do that? And how does the plane generate an approach path without checking with the tower?

     

    Thanks all.

     

    I'm no expert, but I've had problems activating a procedure if the current waypoint is the landing airport. I thought that might be your problem so I recreated your flight. GPS direct from KDEN to KJAC. Flew on autopilot and just after passing KSAA I activated the procedure for VOR 1 Approach to KJAC. The magenta line started where I activated it and it's taking my to the first point on the approach EBACA. It continued to fly the approach correctly to the airport. to KJAC VOR1.JPG

     

    I do notice from your pic that the Autopilot was not on NAV mode. It says ROL, instead of GPS. Did you purposely do that when it started to go haywire, or is that what caused it to go haywire? Your GPS says it's taking you to EBACA, but it won't do it if the AP says ROL.

     

    Hope that helps.

  9. I give up!!!

    The sim is much smarter than I am!!!!!!!!

    Not sure why it won't do what I would like to do, But I can get buy the way it is.

    So thank you for your input.

     

    OK, if you want to give up, but it’s pretty easy to change it to what you want.

     

    Go into Options/Controls and highlight the Keyboard. Under Search by Name type Attitude Hold. It will show your CTRL+T there. Highlight the box and click Clear Current Input then Validate to clear it out.

     

    Now under Search by Name type Altitude Hold. It will probably show nothing assigned so do CTRL+T in that box.

  10. Hi Aptos,

     

    Regarding the rudder ball in the 152, it does move when you bank but only with a pretty big initial bank. You'll see here that it's displaced to the right so you should apply right rudder to get it back in line.

    Ball.JPG

     

    I couldn't find anything under General Options for setting Auto-rudder so it's probably not on, but there are settings under the Controls. Mine are all blank as you'll see here. Maybe you should search for "Rudder" under Controls and make sure you don't have an assignment defaulted there.

    Rudder controls.JPG

  11. I may have found the source of my problem but I can't figure out how to solve it.

     

    I read in a prior post that "digital" input means the control is On or OFf, not analog. My joystick Control options state that ithe X Axis is a digital control; e.g., "or or off." It says to map to a key or button. s This doesn't make sense for ailerons controlled with a joystick. When I map the ailerons to the X Axis, any movement of the joystick turns the ailerons "on" or "off." That's what has been causing the uncontrolled rolls. When I map the ailerons to buttons, they work and there are no uncontrolled rolls. But this renders the joystick useless for ailerons. How do I change this? I have re-mapped the ailerons to the joystick X Axis of course, but it still is operating in an "Off/On" function. The joystick calibration shows it operating normally in the X Axis.

     

    I must be doing something wrong.

     

    You state that it says "X Axis" under controls. I'm using a Thrustmaster T 16000, but mine shows "Joystick L-Axis X" for the Ailerons:

    Joystick Aileron.JPG

     

    If I click on "Aileron Left (Roll Left)" then it says in the description that it's a digital input. I think you've just got the joystick mapped there rather than to the "Aileron Axis" like in my picture above.

  12. Well then you are very fortunate. It doesn't work for me at all. Lots of people on the web saying it doesn't work.

     

    So I tried to load up a different plane, the King Air. Started a flight, uggg . . . . cockpit screens are just black. So I googled it. Yup, you guessed it, another bug being reported by many others.

     

    Seriously. I've tried to fly two planes in FS2020 so far and neither of them have worked.

     

    There is a known bug currently that the planes will sometimes start on the runway with no screens. Just hit Escape and then RESTART and it will work.

     

    As for the 747, I’ve had no problems with the autopilot. Maybe check YouTube for some vids about it to see if you’re doing something wrong?

  13. KSBA Ils to Runway 7 I usually just use nave 1 and fly GPS to the last VOR I pick up the horizontal and the plane turns to final but no vertical and no diamond

     

    I can't tell which plane you're talking about because you mention the 182 glass vs the standard 172, but then you mention the diamond. I tried this ILS 7 with both versions today and the glide slope worked fine. KIZA to KSBA.

     

    In the Glass version I loaded the ILS7 Procedure via HABUT. Flew AP via HDG at first to get over mountains at 3500 then NAV to HABUT. The diamond was alive before HABUT a little above center. At GOYED the Garmin switched itself to show LOC1 selected and AP captured GS right after that.

     

    In the non glass version I entered 110.3 into NAV1, pushed the NAV/GPS button to NAV. USED AP HDG to head toward HABUT at 3500ft. This pic is right before HABUT and I was ready to set AP to NAV.

     

    C172 to KSBA.JPG

     

    Then AP to APR when both LOC & GS were about captured. The AP took me all the way down and I turned it off at about 500ft.

  14. Thought I'd give a "heavy" a try today, in the MSFS flight-training tutorial on how to take off. But I couldn't find the parking brake release in the cockpit, and control + num del key didn't work. How do you get this big guy rolling?

     

    I don’t know about the in-cockpit Brake Release, but you can go into Controls for your keyboard and search for Brake to see what it’s currently set to.

  15. Interesting. Could be a bug. But I'm enrolled in ground school for real-life flight lessons and the message for VOR stations was: First, make absolutely sure you are tuned to the correct station. Second, you need to double check ahead of time to make sure that the VOR is actually up and running. They may be down for repairs, maintenance, etc. So hey, it's frustrating that these may be buggy but that's apparently the way it goes in real life too.

     

    Well unfortunately we don’t have NOTAMs or a FSS in Flight Sim to tell us a VOR is out of service. I doubt that the sim is going to go for that amount of realism. It’s probably just a bug with some of the VORs.

×
×
  • Create New...