There's probably something I'm missing, as I know absolutely nothing about simulator design. However, I know the real 208 perfectly well; I'm a retired AME (Aircraft Maintenance Engineer), so in my mind, it's all very simple. I understand very well that it's not necessarily so when you have to translate all of that into a simulation. I truly appreciate the work already done; the black squares are really very well modeled. My comment was a suggestion for possible improvement, not a criticism, as I myself am incapable of creating such a product. Best regards

"NAV" tracking now working but now unable to zoom GNS 530 in or out.

I am having the exact same issue. I believe I am on V1.3 and mine doesn't work at all.

Yeah, this issue plagues me in most of my GA planes, really wish they'd fix it.

Appologies to Nick as quite frankly any aircraft he makes will be a day one purchase from myself. I have a real hankering for a Swearingen Merlin and I think that would go rather well in your turboprop lineup. Although i think my want of the week will no doubt change again

@rlashier said in Bonanza Pro Installer Issue: I’m hoping someone from the Just Flight team will be able to help me with this. Our advice would be the same as that offered by Nick - contact Just Flight Support and they should be able to help with this issue: See: https://community.justflight.com/topic/2/product-support

@Zacke said in two more questions: sensivity of the mixture/flap bindings: in the manual it's stated one can change the sensivity of the mixture control by using the right friction lock. But is that only for hardware bindings or does even change the sensitivy when I use the mouse? It only changes the sensitivity when using the mouse wheel on the mixture control. Sensitivity of your hardware controls is dependent on your actual physical hardware controls or the binding/sensitivity curves that you've assigned to it. @Zacke said in two more questions: sensivity of the mixture/flap bindings: And I can't bind the flaps to my joystick buttons. I tried the different flap commands (continous etc.) but nothing's happening within the Commander. The ordinary Increase/Decrease Flaps bindings in MSFS should work just fine. Don't use the Continuous ones unless you know what you're doing. If you want the continuous flap control to work, you'll probably need to use third party binding software. There's an example of how to do that with Mobiflight: https://community.justflight.com/topic/11197/axis-control-for-cowl-flaps/26?_=1789410025015

Still the best aircraft for 2024 available!

Hello djd565, please read my new post from today (https://community.justflight.com/topic/11360/some-minor-observations). Do you also see the problem the KLN keeps alerting you to change track after passing a flight plan waypoint? Maybe these problems are connected.

Thank you. That was the issue. For some reason I parsed the sentence as saying this was present in the reciprocating version of the plane. Thank you for the quick response, and thanks for the wonderful product.

[image: e182301a-0547-4ccf-91cb-0c9f5269c68f.png]

@NG7V Don't forget there are two handles for the doors - the lower one opens the door once the upper one is unlocked ... but this doesn't explain why the baggage door doesn't open.

IRL you'd probably look down when you slotted the tablet back into its storage? I find it quite immersive having to look where I'm putting it, rather than just clicking it 'off' and having it 'vanish' ... but I use TrackIR so that makes looking down easy I suppose.

Ah, that could be a good clue, since I’m using the PMS GTN750 in combination with the GNS530. Oddly enough, the latter isn't displaying any data either. If the calculations are based on that, they would naturally be incorrect. Of course, I don't know how it works internally... [image: 56599130-1e97-4072-b2c6-04a8e1b704a4.png]

Hi all, I have this version of POH: "Issued: December, 1983. Revised: September, 1998. Serials: TJ-436, TJ-444 and after". I think it is the latest, but I’d like to ask you to confirm this. Regards.

This kind of artifact is solely the result of the simulator's renderer, and most likely from frame generation. If you're seeing this after a recent update, did you enable DLSS5, perhaps? Unfortunately, there is nothing an aircraft developer can do to combat this kind of artifacting.

Yes, exactly as you explain in your old post—the exact same thing is happening to me.

I wish!! There are a few things that really need some attention.

Thank you