Has anyone else noticed;
COM2 on ‘occasions’ will jump by 10 and the NNN.nn5 can not be set. COM1 seems fine.
Today 16 Dec, flying into KSBA could not set GND. 121.7 COM2 would skip from .65 to .75
KSBA is ORBX. (thumbs up on the product)
Flying the Mooney,
and have been into and out of KSBA since it first appeared in Market place.
First time for this.
I checked mine. KX 165 COMM values as NNN.nnn and skipping on/missing below:
NNN.n20
NNN.n45
NNN.n70
NNN.n95
Tested on LOWS and LOWI.
Default, no Orbx.
Anyone else still having some issues with the barometric pressure settings and transponder?
When manually adjusting the pressure, the altitude indicator moves but the autopilot doesn’t react to the change, and doesn’t level off at the proper altitude. Pressing “B” however gets it to respond properly.
The transponder doesn’t report flight level. It constantly shows FL000.
I would report any and all bugs found to Carenado’s own Zendesk.
Yes, of course. Just want to see, though, if it’s just me with this issue. Maybe there’s an easy fix.
already searched in forum “10 degree” ?.. is it same ? 
My autopilot definitely responds to manually adjusting the altimeter. Not sure if this makes a difference, but I do use the Saitek radio panel to do this. As for the FL on the transponder, I honestly haven’t noticed. I only look at the altimeter for altitude information, but will take a look at it this evening.
Anyone figure out how to do an autopilot coupled ILS?
Hi, I am relatively new so I hope I understood you correctly. I have no issues. I selected directly to airport. I did LOWI to LOWS, then loaded the departure and approach Rwy 15. Entered ILS frequency on Garmin and NAV which was 109.90. Took off nice and easy on GPS NAV mode. On final approach, I pressed APR and controlled the throttle, flaps, and speed brake and landed smoothly. To be honest, it is boring. I don’t like too much automation, lol 
Doesn’t that have to do with the fact there is an 8.23Khz (Mhz? I forget) spacing on the channels (I got “yelled” at for calling them frequencies )
tune ILS into nav1, set course of the runway in the OBS (pure reference for yourself), make sure you’re in VLOC (not GPS), turn NAV on when localizer alive, engage autopilot (if not already done), appr on when glideslope comes alive, and handfly it no later than minimums, as the plane is not autoland equipped
Does it work on the default heading indicator? or just the backup VOR indicator. I am a real world pilot, and I know how to do an ILS but for some reason the needle did not move at all when flying the ILS.
Both work for manual reference, but only the main is coupled on the ILS
So i had 10 hours in this airplane… with not a problem. Today, anytime I switch on AP it pitches up wildly, down wildly. Nothing I can do to fix it. I changed nothing… what happened?
I think I am one lucky sim pilot here. Never had any issues with my Mooney nor experienced CTD since I bought MSFS. Flying now, with GNS530 Mod. GPS, NAV, AP, ILS are all perfectly working with me. Cheers.
yes…
Mine has that issue. FL000 , always
V-Speed coming up preset with a number…?
Mine is preset to negative 700 ft/min now. I have no idea how or why.
So I have to be quick on the mouse to zero that out and put in a positive rate of climb.
Do you have the Logitech panels? I think ±700fpm was a default when enabling VS.
scrolled bit back, but not seen it in thread:
Anyone noticed same ?
Honestly, I have no idea what happened. Flying through a certain area of texas it just seemed buggy, after I moved on about 50 miles everything was fine… I chock it up to weird MSFS behaviour? A few hours later no issues.
