@RealPax Thanks, and yes XD

You bet. I have been using it since the FS2004 or maybe before that. It is wonderful.

Hi Mark, I tried a repair from the installer and it was just the same. I'll try and make time to remove and re-add the Vulcans again over the next couple of days. regards Steve

Any news about this? Having lights visible from a distance in the LOD would really help. Thanks.

I'll add that this issue has been partially resolved. However, this applies to MSFS2024. There's an option to change the binding. However, the right mouse button is assigned in MSFS2020 (hard coden I suppose). Currently, I only fly in MSFS2024, so I changed the zoom assignment to Num0 and it's fine. It turns out that some of the press and pull buttons use the right mouse button, so it's a more involved operation.

Sure, thank you Mark. Amazing plane i love it.

The Vulcan was the second aircraft we developed into an MSFS 2024 native product, and therefore, it was developed around the time when we were still learning how to develop products for the new simulator. For that reason, it doesn't make use of as many MSFS 2024 features as our more recent MSFS 2024 native products. All of the MSFS 2024 elements that we have intentionally included with the product are working as intended, and additional items, such as MSFS 2024 walkaround mode, are items we would like to include in a future update, but due to the development time involved in adding those, we wouldn't be able to commit to a timeframe for when those may be added. Mark - Just Flight

Left over from the Duke manual. I've fixed it. Thanks.

Thanks for the comment. Indeed, I've already done the work for all my other aircraft. There is actually yet another step I could take to make the flares really bright (hyper-realistic, shall we call it) during the day, but this would take much more work, so I wanted to see what my users thought of this change first. I think the results are definitely acceptable now, and anymore would be (probably less realistic) eye-candy.

Hey Nick, same as the guy above me, I'm using the WT GNS 530/430 combo and I'm seeing the KAP140 baro setting having no effect and the main altimeter setting controlling the AP. Currently flying the Cargomaster in MSFS 2024, Caravan v1.1. Edit: removing the ping, as based on the comment re: WT update cycle I suspect you're aware of this. I thought it worked in the Analog Caravan in 2020 though? I was using WT avionics back then, as well.

@Galf Do you have v1.1 of the Caravan? There was an issue in v1.0 that prevented those items from saving, but only for the Cargomaster.

@ksmith Wonderful! Thanks for the feedback. Let me know if there's anything else I can do for you guys!

@Black-Square Sorry about that one - for some reason I thought real taxiways changed the pavement markers too. Here's another one today: CYHZ Runway 32/14 - all of the signs say 23-05. Runway 23-05 is correctly marked. Let me know if you want me to continue to tag you on these - or just post and let you get to them when you can.

Yup, that works for the 650, but not for the 750 which was what was confusing me.

+1, sounds like a really cool improvement idea.

@RPGamerous I mean yeah, I agree, especially that it would technically be the only variant with an actual 3d cockpit differences. As I said, I don't believe it would ever take any priority over the steam gauge variants - but it would be definitely a super cool backlog item reserved for whenever Nick has time in between the major releases

If you actually have the Bonanza Professional (the newest version), there is a dedicated MSFS 2024 installer similar to how the TBM850 has one (and you should use it rather than copying the 2020 version over). If you actually have the Bonanza Overhaul, then no it doesn't work in 2024 without a lot of massaging and maybe not even then.

Ah ok... I tried CTRL C very quickly and could see the tablet trying to change the GPS, but it still ended up back at the default 650/750.

Interesting, it was happening repeatedly to me, and after several startup and shutdown cycles since I had done a few flights without going back to the menu. Notes I should have included in my first post: using the Cargomaster, MSFS 2024 SU4 release, and yes the tablet to manually trigger the failure. I had thought it would be in an area using common code across variants, but I did not actually test that. Is there anything I can do to help troubleshoot it? The first time I triggered the failure was actually the longest it took to happen; I had a few seconds to play with the throttle and see there was no engine response, and right around when I moved the emergency lever was when it died. I had thought I had done something wrong until I noticed both fuel tanks were at zero. Subsequent failures of the FCU produced quicker, but not quite immediate results. Sometimes it would instantly zero, on at least one occasion I saw the tanks empty in a few discrete steps.