Not to beat a dead horse. But any news on adding the ability for you to broadcast the FMS so we can use it on hardware equipment. I personally use spad next. But others use different things. This is the only single payware plane I own that doesn't support this feature. It's important. thanks

I tried many things including reinstalling the sim but the problems with the gps are not solved. 750/650 does not start up and the 530/430 has always the message of no gps. I use the premium version of the gtn750 in many aircrafts without any issues. Only in the caravan this happens.

We are just coming to the end of a full rewrite of the holding pattern logic, and we intend that work to form the basis of the v1.4 update. Included with that will be some improvements to the missed approach logic, but we'll share the exact changes closer to the v1.4 release. Mark - Just Flight

Thank you for the feedback. This is something our IT team has on their list to implement in the future. Mark - Just Flight

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

I'm all for providing choices for people, especially if they draw more people to check out Nick's excellent planes. I won't be using those big screens, but I'm sure they'll appeal to a lot of folks who don't want to fly analog. Having said that, in the forums and discords I'm in for so many flightsim devs, wow, every avionics suite under the sun is being requested of pretty much every dev. I'm glad I don't have to try to please everyone!

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]

I added the IFR and Landing views to cameras.cfg. Now I am able to adjust and save those views. Here are the added CAMERADEFINITION blocks: [CAMERADEFINITION.33] Title="IFR" Guid="{9455F7C9-C826-4FE2-A803-D6AC36D3AAC5}" UITitle="IFR" Description="" Origin="Virtual Cockpit" Track="None" TargetCategory="None" ClipMode="Normal" SnapPbhAdjust="None" PanPbhAdjust="None" XyzAdjust=0 ShowAxis="NO" AllowZoom=1 InitialZoom=0.408867 SmoothZoomTime=5 BoundingBoxRadius=0.1 ShowWeather=0 CycleHidden=0 CycleHideRadius=0 ShowPanel=0 MomentumEffect=0 ShowLensFlare=0 PanPbhReturn=0 SnapPbhReturn=1 InstancedBased=0 NoSortTitle=0 Transition=0 Category="Cockpit" SubCategory="PilotCustom" SubCategoryItem="ClosePilot" InitialXyz= 0.033192, 0.011464, 0.308273 InitialPbh= -8.463341, 0.019782, -0.174713 [CAMERADEFINITION.34] Title ="Landing" Guid ="{E4D82C6F-1A57-4B39-9C0E-8F6B2A731D45}" Description ="" Origin ="Virtual Cockpit" MomentumEffect =1 SnapPbhAdjust ="Swivel" SnapPbhReturn =0 PanPbhAdjust ="Swivel" PanPbhReturn =0 Track ="None" ShowAxis ="YES" AllowZoom =1 InitialZoom =0.25 SmoothZoomTime =2 ZoomPanScalar =1 ShowWeather =1 XyzAdjust =1 ShowLensFlare =0 Category ="Cockpit" SubCategory ="Pilot" SubCategoryItem ="LandingPilot" PitchPanRate =20 HeadingPanRate =60 InitialXyz = 0.006,0.260,-0.060 InitialPbh = -8.000,0.000,0.000 NodesToHide ="" ClipMode ="Normal" BoundingBoxRadius =0.1 UITitle="Landing" TargetCategory="None" CycleHidden=0 CycleHideRadius=0 ShowPanel=0 InstancedBased=0 NoSortTitle=0 Transition=1 PanAcceleratorTime=5 XYZRate=0.25 XYZAcceleratorTime=0