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

@Mark Screen was done in VR.

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.

You're both welcome, though I didn't do much beyond a glance at .cfg files and trying out various dev mode debug tools in the menu. Thanks Nick for the corrections. I'll make them just for the warm fuzzy feeling that fixing incorrect data always gives Besides the 'show sim forces' debug option (earlier image), it's very interesting to see the different CFD visualisations at work. With one engine inop there is clearly a sudden loss in thrust, even a loss in the downward deflection on the adjacent air flow from the lack of prop wash over the inop engine's wing, but no yaw tendency or rudder forces/effects show up whatsoever (whether AP is engaged or not, in case of a hidden yaw damper interfering). A roll tendency occurs into the dead engine as you might expect, just no yaw. That's in itself is interesting because it seems to show that MSFS decouples various aspects of the flight model; the forces and moments acting on the aircraft may not be purely a result of all the aerodynamic forces shown (else something else is blocking it from occurring). I know there are legacy and modern flight models, and various settings that are old or new - it must be a nightmare to keep track of which settings actually influence the aircraft and which are deprecated (and catching the undocumented ones) - so I don't envy any developer's job there (well I kind of do, in a different life). I'm sure this one is 'on the list' to be investigated in due course anyway. Regards, Martyn

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

@Wothan Got you, sorry that I cannot help. I did move away from the MSFS Contol System already in FS2020. For that reason I don't have any experience with the internal control bindings of MS2024. Hopefully someone else with more knowledge can help you.

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.