Exactly what I was saying. I think (or thought) 29.92 was the sweet spot for the G1000, but I flew your flight out of Detroit Metro this morning in ■■■■■■ weather (cold, 19 kt headwind), barometer at 29.98. Set heading to 210 degrees, ref alt to 3000. It climbed to reference altitude (within 5 or 10 feet) with a little oscillation ( variable wind and speed?). Set AP and NAV, Descended to 1200 at -400 FPM, held that altitude for awhile (+/- 5 ft). Ascended to 3900 ft. to match Toledo (KTOL?) approach ILS R7Y pattern. Promptly iced up, lost control and crashed. Too cold, too humid, too high, pilot too distracted. However, back to the 29.92 sweet spot, the ALT mode seemed to work, including a baro change to 20.90, approaching Toledo. I can try a Seattle flight to confirm, but it seems something else is at play. Do you have anything in the Community Folder? I don’t.
Ok, how was the KSEA test?
Sorry, haven’t got there yet, washing dishes… LOL!
I’m gonna do Clear skies, 29.92 regardless of actual ATIS, to 3000 ft., heading 163 degrees. Then I’ll repeat at Live Weather, ATIS baro, same alt, same heading. I’ll note runway elevation on both attempts and we’ll see where the G1000 Alt Hold mode takes us.
Tim
Ok,
Use my last KSEA information post and insert your findings (numbers).
KSEA ATIS freq is 118.0
Edit: What is your home town area airport?
Nearest Airport is KDEN, Denver International. I fly out of KBKF (Buckley AFB) for convenience. Flew out of KSEA a bit ago, CTDs are getting ridiculous. Still cn’t get an update out of 1.14.6.0 and starting to lose patience, no Profile, no help from the community, $3000 down the tubes??!! Anyway, prior to a spare of CTDs, at parking spot in Seattle, actual real-time info from outside sources was 30.12 and winds at 8 knots from 335 degrees. Tuning ATIS, they report 30.12 and winds at 8 knots, 321 degrees. In agreement. Barometer setting shows 390 feet, AMSL.?? Anyway, adjusting baro setting to show 432 feet is someting other than +30.12. Take off from 16L with alt ref set at 3000 feet, fpm set to 300 fpm. The aircraft ascends to 3000 feet, +/- 5 feet and holds. Engage AP for a flight to an airport on the coast, (Bancroft??) approach altitude 2100 feet. Set VS to descend to that altitude, which it does (+/- 5 feet), flies the flight plan, procedural approach to runway 24 is activated, does about 3 ‘Crazy Ivan turns’ at which point I take control and hand fly to a landing. My frustration with this ‘Dumpster Fire’ has just about reached a breaking point.
Is MSFS your first Sim?
You mentioned in your KSEA test:
“Anyway, adjusting baro setting to show 432 feet is someting other than +30.12. .”
No , you cannot not do that.
And you never mentioned what baro setting you ended up dialing in.
What is up with all the adjustments to a basic test?
And, I never mentioned doing that.
All other aircraft will be using the correct ATIS Baro setting.
You are making up a situation which will wrongly allow you to stop at the altitude you want.
All other aircraft in the area will be a a different altitude.
You mentioned “Exactly what I was saying. I think (or thought) 29.92 was the sweet spot for the G1000”
There is no such thing.
Edit:
No screenshot to share of your test result?
I’ve been flying MSFS sims since the mid 80s.
Adjusted Baro setting just to see what it was with actual airport elevation, then set to ATIS.
Set to ATIS reported 30.12.
There are NO adjustments to a basic test. I set altitude, left and ascended to the altitude you wanted, watched as the aircraft reached and settled to that altitude, with baro at ATIS 30.12…
I think we’re DONE here, you ingrateful P***K. I’ll give you a screenshot! Who do you think you are???
Good luck!
Another test just now 4-16-21 (about 1200Z)
Cessna Citation Longitude
KSEA
MSFS Live weather
Real world and MSFS ATC reporting Baro 30.17
KSEA Runway 16 L / field elevation elevation 432 feet (FAA airport chart)
Cessna Citation Longitude PFD altitude Runway 16 L with Baro set to 29.92 175 feet
Cessna Citation Longitude PFD altitude Runway 16 L with baro set to 30.17 445 feet
The difference is 270 feet
Cessna Citation Longitude Armed altitude set to 6000 feet for the test
Cessna Citation Longitude stopped climbing at 6260 feet (screenshot)
The error difference is 260 feet
So far this altitude problem has shown up in my tests with the :
Baron
Beech 36
Cessna Citation Longitude
A previous screenshot in this topic showed the autopilot steering mode as:
LVL
In my newly installed MSFS version 1.15.7.0 the steering mode is:
ROL
when the autopilot is turned On.
The questions are:
Was LVL used in the original (older) version(s) of MSFS Garmin 1000 autopilot possibly from e.g. Sept 2020 ?
Is ROL correct for the current MSFS version of the G1000 ?
Screenshol of the LVL roll mode:
Follow up information.
On 4-16-21 I installed MSFS Update 1.15.8.0
It has the same problem.
Aircraft does not stop at the selected (armed) altitude.
These are the MSFS version that have this problem:
MSFS 1.14.6.0
MSFS 1.15.7.0
MSFS 1.15.8.0
As an additional outside test I used Prepar3D v4.5HF3, Mooney Bravo and the Active Sky weather program at KSEA on 4-17-21.
This test was just to confirm I am only seeing the problem on my setup with NSFS, Live weather and various aircraft.
The ATIS Baro setting was 30.20 for KSEA departure (runway elevation / altimeter gauge showing 420 feet).
I armed 3000 feet as the target climb to altitude.
All ok, the Mooney Bravo climbed to 3000 feet and stayed there.
Done your test and can confirm I experienced the same issue.
I believe it’s caused by manually adjusting the Baro instead of using the B key.
Verify this happened on my machine–been this way since Store purchase.
Very annoying.
Later: Input latest Working Title G-1000 and retested–yep still fails to follow armed level.
Retest.
Update.
With a second suggestion on AVSIM forum to try the Keyboard “B” key to set the MSFS current Live Weather Baro instead of using the Baro Knob in the VC to dial it in.
That worked on my setup on default MSFS aircraft with the G1000.
Note:
In my testing other MSFS aircraft using other Garmin products do not require the use of the B keyboard key.
Short video showing the problem on my setup.
It’s the autopilot flat out ignoring the barometer setting and basing it’s altitude off of 29.92. It happens in longitude as well as several other planes.
just had sim 5 update and set it to 29.92 by pushing B and keep getting climb to altitude then get descend