No, for me I press FPL to bring up the plan, then click the small FMS knob, then turn the big FMS kob.
Thanks. Are you in Legacy or Lock mode for interactions?
What ever is default for use with xbox controller.
Thanks. It works in LOCK mode, Legacy appears busted. Iâll file a report.
In 2024, is anyone else having issues tuning into a VOR? Mine seems totally broken. Cannot see any Nav Aids.
No. Can you give an example of one?
In Legacy you can still click and hold the left mouse button and then simultaneously click the right mouse button with the cursor on the FMS button. This toggles the highlighting on the FPL screen. I consider this a backwards step as just left clicking worked fine in MSFS2020. One more example of a senseless change to something that did not need changing
My issue is that the aircraft will not receive the VOR signal. I am a RWP and am fluent in navigation but no matter what I do, the aircraft isnât picking up the signal. 10 NM away with a straight LOS to the beacon. cheers!
Which VOR station are you trying to receive?
KLAS Las Vegas. From Boulder
Itâs working fine on my end. Please take a screenshot of the PFD.
1 Like
So for msfs-2024 I noted in some stock aircraft that VNAV wonât arm (VPATH in white) using the VNAV button. I have to arm it using the APR button which of course also arms GP - as in the case of a Visual Approach. Iâm doing this well before estimated ToD based on my external EFB. I wonder if this is accurate.
I have had pretty good experiences throughout Sim update 1 Beta and after SU1 launched. Today started fs2024 to fly a couple trips. Couldnât get a flight plan to load correctly into G1000 MFD. It would list the waypoints and ILS fixes but nothing showed up on the map. Usually there is a magenta line for the route. No altitudes loaded either. On the PFD the GPS course was pointing the opposite direction. Canât get GPS to engage in the autopilot at all. Without altitudes there is no VNAV. Tried numerous time using the EFB and also with navigraph charts and simbrief. Similar results. Has there been an update to the G1000 that I missed? Anyone else having difficulty or ideas for a cause/solution?
What youâre usually seeing is that the FPL is focused on the first leg of the designated approach using Vectors-To-Final.
Working Title says VTF by default is the correct mode, but it leaves the MFD route depiction confusing as you described.
The partial solution is to go into the FPL and delete the approach. You can reassign it, but I recommend picking a different transition other VTF. If itâs a Visual Approach, use Straight. If itâs an Instrument Approach, pick a Transition Navaid point based on your Charts and route of travel.
All things being equal, your route path of intended movement (Magenta Line) should now appear. You may need to adjust zoom range as needed.
Everything was working normally a few days ago. Now it is a mess. Itâs much more than just the magenta course not being on the map, as it used to be. No altitudes in the flight plan, so no vnav or TOD. The GPS doesnât work in the PFD. I do select a transition to the final approach when I build the flight plan. Still no course line on the map. Something significant has changed in the last few days with regard to flight plans and/or the G1000. I am flying the C208, as usual, and it always worked before.
Do you have the full flight plan as well as the steps youâre following to input that flight plan youâre having issues with so we can try and reproduce the issue?
I will post that tomorrow. I did install new Navigraph plugins for the G1000 before I opened the sim this morning. Perhaps something in that process caused a problem. Thank you.
I removed all the latest Navigraph plug ins, rebooted, re-installed the Navigraph plug ins and the G1000 screens are pretty much back to normal. Just a bit of trouble getting VNAV to work properly. I donât know why my post yesterday disappeared.
When entering minimum decision altitude for an approach, it seems the only way to enter the number is with the small FMS knob, 10 feet at a time. My minimum is 7,720 feet (at KTRK). My scroll wheel finger is going to fall off!
Silly question: is there an easier way to enter this number?