Hi. Thanks for the suggestions. No, there’s no roll equivalent of that pitch assignment pair. In the 146 the pitch command you refer to does successfully control the AP pitch control (although not visually). I don’t think that developer feature you mention is available to Xbox users. But will take a look to be sure. Many thanks.

Thanks for your continued attention to this issue. Looking forward very much to it being fixed.

Agree. And the reason why my hanger includes every plane available on Xbox. You certainly do have a lot of consumer confidence with JF.

@ButterSausage Your best bet would be to contact Just Flight Support and they can advise on any problems you are having with the aeroplane.

@RealPax Thanks, and yes XD

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

@YoYo As per Mark's comment above, if you get in touch with Just Flight support they'll be able to look into this properly.

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.

@V1RotateAP Thanks for the screenshots. That's exactly what I was looking for. Here is what I have been able to determine from my testing: The standby alternator is energized, and contributing power to the aircraft. The two annunciator lights are behaving correctly, as all conditions appear to be met. Indications on the tablet are confused, because my variable L:var_AlternatorOnline is not true. We can see this with the red line through the ammeter (reading zero), which both rely on this variable. There are two avenues we could pursue from here: Why is L:var_AlternatorOnline not being set correctly, despite all conditions appearing to be met. Why is the alternator energized to begin with. I'm inclined to investigate the first point, since, technically, L:var_AlternatorOnline should have no impact other than the visuals displayed on the tablet, while the electrical system is causing the annunciators to illuminate, and causing unexpected electrical behavior. Again, here is where I would suspect a hardware issue (even though I emulated this in my testing, and it caused L:var_AlternatorOnline to be set correctly. To further test this, I would recommend temporarily binding a key combo to Toggle Alternator 2 in the simulator's controls menu. Then, try toggling the alternator manually and see what happens. Either, it will... Toggle back on by itself. Remain toggled off. If #1, then it's more likely a code-side problem. If #2, then it's more likely a user-side problem. I really appreciate the help, and the testing above would provide exactly the kind of information I need next. Thank you so much!

@F737MAX Good tip, thanks. I'll add it to my small collection of useful Firefox extensions!

@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

I hope you guys don't think I've been ignoring you. Unfortunately, I wish I had better advice to offer. The code in the Caravan that might have anything remotely capable of producing a CTD is identical to my other aircraft, and the Caravan has even less in the way of avionics than most of my other aircraft. I know several of you are seeing symptoms that appear limited to the Caravan, but I have also seen similarly limited behavior with my other aircraft in the past that resolved themselves in various different ways. Luckily, I haven't had any consistent and persistent CTD reports (other than v1.0 Starship) with my aircraft over the years, largely in part to their architecture, which avoids WASM, where CTD's are most likely to happen. I would encourage you to keep looking for outside applications or system-level issues that might be causing this, but in the meantime, I will be watching this thread closed to see if there is anything I can learn, or anything I can suggest for testing. Sorry that you're dealing with this right now. I just wish I had more to offer.

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