Avro Vulcan B Mk. 2, K.2 & MRR

I have similar issues in VR. I get no tooltips except on the fire test switches.

Going to be a difficult one to run down, but I'm 99% certain it's not flight model related. The reason I say this is that there is nothing in the FM which could give differential aileron in a left / right sense. There IS a table which adjusts the effect up and down, and for a brief moment I wondered if that had become 'altered' in the core game flight model. However, I fired up the Vulcan and see no issue - the extremity of each axis gives me a reading of 1.000 in the controls debug tool.

With the NAV LIGHT switch in the FLASH position, the nav lights and beacon lights will be illuminated. This is the position that is required as part of the takeoff callout conditions. Mark - Just Flight

I've found the volume of navaid audio tones to be very, very low in both MSFS 2020 and 2024, often to the point of being inaudible. I've only managed to just barely hear them a couple times, both times with headphones. I've never attempted in the Vulcan, but maybe if you turn engine and environmental volumes down it'd be easier to hear them, since it's generally a loud aircraft. Just an idea. I don't even try to listen for these tones any more because they're so hard for me to hear in any plane.

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

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.

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

Thank you for the feedback. I have logged this with our artwork team to investigate ahead of the next update to the Vulcan. Mark - Just Flight

Thanks for your reply. That’s understood fully. There are a few aircraft on the market place on Xbox that allow if you press jettison it removes the we[on from the payload which is a little more immersive. So not specifically seeing the weapon drop but as close as we can get etc. would this be possible for the marketplace versions at some point? The aircraft that allow this are the IFE aircraft. Sorry for name dropping another developer but it adds to the immersion that big extra. Cheers Rg

Unfortunately, as you say, I believe this will be a limitation of using Chaseplane with some of our products. The Vulcan, and a few of our other products, rely on the core MSFS camera system to move the user to certain locations in and around the aircraft. As Chaseplane overrides the default camera system, the cameras that we trigger in the code no longer exist, so the camera will not change. It's something we have logged on our internal trackers for further investigation, and to see if there is any form of a workaround we can find for Chaseplane users. In the meantime with the Vulcan, it should be possible to create custom Chaseplane cameras inside the AEO/Navigrator compartment and then trigger those via the Chaseplane interface. Mark - Just Flight

Found this with chat gpt https://aviationarchives.blogspot.com/2017/09/avro-vulcan-b-mk-2-aircrew-manual.html

I've just checked this on my side, and the following control assignments can be used to control the CLIMB/DIVE switch on the throttle quadrant: INCREASE AP PITCH HOLD REFERENCE DECREASE AP PITCH HOLD REFERENCE Note, those will only control the aircraft's pitch when the autopilot is engaged, and no other vertical modes are engaged. Hope that helps. Mark - Just Flight

I'd recommend contacting Just Flight Support about this problem. https://community.justflight.com/topic/2/product-support

Thanks again for your help. I’m not sure then, other than maybe it’s just my eyes deceiving me. I’m on Xbox if this helps anything? Thanks Chris

We're not aware of any brake issues in Vulcan, however, if you're using MSFS 2024 there have been some changes to Parking Brake control assignments in SU3 that could be causing a conflict. See: https://forums.flightsimulator.com/t/parking-brake-cant-toggle-on-off/734585 If brake issues exist in multiple aircraft, that typically points to either a control assignment conflict. Mark - Just Flight