Commander 114

@Voxen exactly how it works. the cabin heat knob is a valve that controls the flow, not the temp, and the outside air controlled by the cabin air knob is routed through the same vent as the cabin heat.

If you use those H-events then it'll work in all circumstances: NAV/GPS and RNAV modes.

@Black-Square ... it doesn't make sense (to me lol) that the Heading mode should be dependent on the avionics installed. But who ever suggested that Asobo's internals made sense. Next flight (tomorrow probably) I'll test it without the fancy GPS's and see what happens.

@jmarkows I know you implemented the VS properly with 200 fpm increments but I kinda love that you can make it increment by 100 fpm and the dial animates to a spot between the digits. "No... I really want to descend at 500 fpm, thank you."

There are NAV and GPS labels on tne button, but when you have the RNAV511 selected, pressing the button toggles between RNAV and NAV and I have annuciators for both. It does mention that the RNAV doesn't work if you have a GPS unit installed as it can't have all three at the same time.

There isn't a single simvar for that since the current course heading could be either: L:var_Rnav511_OBS_R or L:var_Rnav511_OBS_L if the RNAV computer is driving navigation and depends on which waypoint button is pressed A:GPS OBS VALUE or A:GPS WP DESIRED TRACK if GPS is driving navigation and depends on if the GPS is in OBS mode or not A:NAV OBS:1 if you're just doing ordinary VOR navigation without the RNAV or GPS I might be missing something if you have the GTN 750 installed... I only use the 530. I ended up writing a custom .lua script to derive the MC60 OBS value and basically followed the same logic that the panel instrument uses. I suppose it'd be more convenient if there were a separate "read-only" LVAR for the MC60 OBS value.

No true pilot puts sugar on his porridge.

I recently learnt Blender with my old brain and produced a livery for the Commander. If I can do it well probably most can lol [image: a41d0a78-76b8-41a5-854b-4d20d1d8ec14.jpg]

@Darth-Patzer said in Instr.lights switch landing gear leds off: It's simply very dangerous. Precisely! Which is why you should ensure that both doors are closed correctly which means they aren't in the 'locked' position BEFORE closing the door.

I would say it is an MSFS thing, happens most of the time ... but not all of the time lol

@Andreyzh said in GNS-430 not displaying DTK or DiS to waypoint in Commander 114: And that doesn't make any sense as this is supposed to be contained within the unit and shouldn't require aircraft integration Nor is there anything I have done in any of my other aircraft to affect this, so I think that's a question for Working Title, if anyone.

Same issue for me. In the past, I tried changing camera config files (the XYZ coordinates), but it's really not easy. If anyone knows how to easily adjust the view without constantly restarting MSFS to test if it is ok, that would be helpful. Maybe Nick could change the default camera position for VR as a fix if we suggest good values?

@Esoteric SimTrim indeed improved the trimming a lot. Thanks!

I made my first 'proper' flight in MSFS 2024 today, continuing my Duke adventures with Air Hauler 2. I'm planning to switch from 2020 at last as 2024 seems to run well enough for me now. Although I use a little utility called AircraftState to help save as many variables as possible in any aircraft, I was interested to see what happened with the Duke's own state.cfg file after reading of the issues here. I loaded into the sim at about 16:00. When I landed and was ready to quit at about 17:20, I went into the directory where the state.cfg file is saved. It still had a timestamp of 16:00 on it. I tried toggling an option or two in the tablet in case changing a parameter could trigger it to update and save. Nothing happened. So, I ended the flight. As soon as I was back at the world map, the state.cfg updated with new fuel values and Hobbs hours etc. So it can/does work in some cases. I'll be keeping an eye on it for sure as I get used to 2024's foibles.

@Black-Square Gyro initializes itself most of the time and you say there is nothing to fix ? I end my flight on a parking, just shut down the plane (wait a bit) and go back to the main menu. Then I start another flight somewhere else and I see the gyro moving by itself. For you everything is ok ?