@SkipperMacz What primary and secondary avionics are you using in the Commander?

Yeah I really hope he offers everything and truly makes this the best king air ever made. I hope we get round gauges, EFIS 85, G1000s, Pro Line 21 and all of the fms/ gps options. That would be a substantial amount of work but I think it would be worth it.

OK seems to be sorted for me now (using Google AI) - Assuming you're all using custom liveries? If so and at your own risk 1 If there's a panel.N851TB folder (obviously name might be different depending on the livery) then check if there are any texture files in there like .dds/.json move them to the texture.N851TB folder then delete the entire panel.N851TB folder. 2 Edit the aircraft.cfg file in your custom livery folder, specifically the entry panel = "" (this may have had a reference to the deleted panel.N851TB folder) 3 Recompile the layout.json file by using MSFSLayoutGenerator.exe No support provided Not thoroughly tested either yet but for me, it's fixed the duplication of control on the GNS530s and the fact the FD wouldn't work without the AP being engaged

Correction. It is the PMS.

@Mark Any news regarding the HOLD and Go Around logic improvement, after v1.3 release?

@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."

You'll have to remap that hardware control using third party software (MobiFlight, AAO, Spad.next, etc.) to send the H:MC60_OBS_INC and _DEC events instead if you want it to turn the knob on the MC60 instrument.

I found out that if you use the heat alone it is hard to control, but if you open the vent as well as heat then you can fine tune the temp, much like when you combine hot and cold water to get the temperature you want.

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.

Thanks for the answer, thought it might be something like this. Roger

No true pilot puts sugar on his porridge.

[image: 0fef8fb6-ab27-4b97-9278-cfdfe0604257.jpg] Believe I've found a workaround to this annoying bug!!! It seems to have to do with the altimter qnh/std button. I've been flying in areas mostly with very low transition altitudes (3,000 ft or so) and have been putting this button into STD. Don't do this. If you spin the altitude window up with it in standard, it will give you the invalid cruise message, and you can't engage profile. The solution I've found is as follows: Just leave the button in QNH and manually set the altimeter If you do switch to STD, but level off at an intermediate altitude before cruise, you must reselect QNH, then on the PROG page of the FMC, change the cruise altitude to the altitude currently selected in the autopilot (i.e. 12,000). I was able to successfully reengage PROF. I could then switch back to STD and it would stay. Curious to hear if this helps anybody else.

I believe noise abatement, mostly, but take that with a sizeable grain of salt because I am a simmer, not a real pilot. Per the TBM POH, you should be able to reduce RPM until the TQ reached 121% (spitballing from memory, it's been a while since I've read the exact numbers) and maintain airspeed, however in the sim I have seen dropoffs of 20kts or greater. I am hoping that Nick will be able to overcome that at some point. EDIT: I knew I had written a post about this, here it is: https://community.justflight.com/topic/7065/the-propeller-lever-does-have-a-use

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]