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

Vulcan Tanker 7.jpg Vulcan Tanker 10.jpg
Hi Mark. Thanks for your reply. Please see the attached images so that I can explain the idea. As it stands, Airshow Assistant can only spawn the same aircraft that is being flown. When I fly the Vulcan as a K2, if I extend or retract the hose, the AI Vulcan copies. In the upcoming update, I should be able to fly a Typhoon and set Airshow Assistant as No4 in a diamond formation and a Vulcan K2 as No 1. Then when I instruct Airshow Assistant to formate on me, a Vulcan K2 with hose already extended would appear near me and then move in front of me. I could then extend my probe and start refuelling.
I am sure the idea is sound, it only needs the K2, probably with the extended hose to be available as an option on the load page as opposed to the tablet. I use the Typhoon as an example although other aircraft capable of air to air refuelling such as the Harrier could be used. Thanks in anticipation. Robert

@colb617 We don't have a release date set in stone just yet, but the fuel system in the Vulcan remains something we would like to revisit and improve in the future once a suitable gap opens up in our schedules.

Mark - Just Flight

It would be great to be able to assign this function to a specific key. I was just about to write a question about this topic. I managed to assign buttons on the throttle of my joystick to control the throttle position (speed..) in autothrottle mode via the commands: Increase Autopilot Reference Airspeed
/Shift + Ctrl + Insert and Decrease Autopilot Reference Airspeed
/Shift + Ctrl + Delete. So it would be great to be able to turn the autothrottle function on and off, ideally via one button (on/off positions) Best regards and thanks for the great work

I have had issues with it too. I posted this on the MSFS forum a few weeks ago, no replies from anyone so can't say anything if it's widespread or not or people aren't using state saving.

Has anybody had any luck with state saving? I've tried a couple of times and it really messes up the cockpit for me - switches on that I’ve never used before, others in a position I didn’t leave them in etc. Also, the fuel state wasn’t the same, it had refilled it to max; the autopilot wouldn’t work, with no amount of resetting via the RH panel switch amounting to anything, bomb doors not responding to open/closed switch presses. There are no warning lights showing for these last two items, they’re just not responding.

Ok, makes sense.

Cheers

Yup I was stupid.....lol

In fairness, it looked like the row was the top row, but if only I tried to scroll up!

@Davidaa Thank you for reporting these. I have just had a look and it does look like there may be a few systems there that we could add some additional logic to.

I've logged these on our internal bugs tracker for us to investigate further, and we will aim to get these additions added to the next update for the Vulcan.

Mark - Just Flight

@Ojisan_alpha Thank you for the suggestions. We have logged your feedback on our internal bugs/feature request tracker for us to consider adding for a future update.

We try to keep the callouts in our aircraft as accurate as possible, so the callouts we are currently using are reproduced from the callouts used by real Vulcan aircrews. We don't have any reference material for go-around callouts or over-G callouts, so we would have to take educated guesses at what they would be.

The big difficulty in adding go-around callouts and callouts for specific phases of the flight is finding a set of triggers to differentiate each stage of flight. For example, how does the simulator differentiate between a go-around and a normal climb after normal takeoff? Getting these triggers correct and callouts automated is very difficult as you don't want the incorrect callouts playing at the wrong time.

We will look into this though, but unfortunately, we can't give any guarantee that we will be able to add all of these.

Mark - Just Flight

Thx a lot for your insight.

The more experience I get with XH558 the better the flight model feels. At the moment my only serious problem is the lack of pitch-up rate on top of a wingover at 140 kts - hardly any elevator authority there, and still unable to replicate this:
https://youtu.be/B092qvttZGU?si=pLZ_Mu7FGps8UUMG&t=347

However... nitpicking on high niveau - I increased elevator deflection one degree which suits me better. ;

Well.... the mosquito would be an extremely nice addition. :)
With a lot of luck my name might be in the bomb bay door - as it is on XH558.

Long time ago I spent an hour with Kev at RIAT talking about the Canberra... such a pity that it itn't succeed (yet)... and times don't get better for such a kind of enterprise....

I also had the same problem once - shutting off the autopilot and resetting it on the copilot side panel worked.
I regard this as a detail adding to the realism of one of the first autopilots ever. ;)

Thank you for reporting this. We've logged this on our internal bug tracker and we will investigate it ahead of the next Vulcan update.

Mark - Just Flight

@Smarticus The Thrustmaster TCA Throttle Quadrant uses the same control assignments for its fuel levers as we do in the Vulcan (as well as our other products like the 146 and Hawk). The fuel levers on the quadrant are two-position switches, which hold either position (either fuel on, or fuel off), so whatever position the fuel lever is in on the throttle quadrant, it will continue to force the fuel lever in the simulator to the same position.

If the fuel levers on the TCA throttle quadrant are in the "fuel on" position, this will force the fuel levers in the simulator to also be in the "fuel on" position, which for the Vulcan is when the throttles are in the idle thrust position. Advancing the throttles will then fight against the fuel valve control assignment which is trying to keep the throttles at idle and can lead to the throttles "snapping" back to idle whenever the throttles are not being moved.

As a way to guarantee that these switches do not affect the Vulcan (or any other aircraft with combined throttles and fuel valves), we would recommend creating a new controller preset with the conflicting control assignments removed. To do this:

Go to MSFS Options > Controls Options At the top of the page, click on the tab with the name of your throttle quadrant At the bottom of the page, go to Open Preset Manager > Duplicate. Enter a name for the new controller preset (for example "Vulcan"), With the new controller preset selected, use the "Search By Name" field on the left side of the page to search for and delete the following control assignments:

TOGGLE ENGINE 1 FUEL VALVE
TOGGLE ENGINE 2 FUEL VALVE
SET ENGINE 1 FUEL VALVE
SET ENGINE 2 FUEL VALVE
SET STARTER 1
SET STARTER 2

With those assignments deleted on the new controller preset, you should no longer have any controller conflicts with the throttles in the Vulcan or any other aircraft that uses combined throttles and fuel valves.

I hope that helps.

Mark - Just Flight

@Mark - My sincerest thanks for your answer. I have been troubleshooting this and now I know the situation. Sort of understandable and a patch would be excellent one day. The detail on the system modelling in top notch. Keep up the great work. Thanks!

The fuel system is very close to the top of our list of areas we would like to improve in the Vulcan. We cannot provide any timeframe for these improvements at this time, but we'll share any progress we have on this through our normal social channels as well as the changelogs.

Mark - Just Flight

@BjamminOnXbox I'll let @Delta558 respond to your flight model queries, but there is no limit for how long we intend to support the Vulcan for, so we will continue to update the Vulcan.

With regards to the rear cockpit, unfortunately, we have no plans to model it in its entirety. It would be a huge undertaking for our artists and systems coders for very little added functionality compared to what we already have in the simulator. It was discussed internally at the start of the project, but we decided it would be better for everyone for us to release the Vulcan in 2023 without the rear cockpit modelled at a lower price point and release additional aircraft in 2024, rather than release the Vulcan with the rear cockpit modelled in 2025 at a much higher price point and no additional aircraft in 2024.

Mark - Just Flight

@Mark Sorry for the late reply, the speed was the issue. I'm surprised I didn't think of that before posting, thanks for your help!

MS have a blanket rule on the Marketplace that aircraft cannot feature any weapons. In order for an aircraft to go on sale there, all ordinance has to be removed. The same rule affects other aircraft we have released such as the Hawk, and all all aircraft from other publishers.
I believe the rule is so they can have a universal family friendly rating for anything sold there.

@flightengineer Thank you for the kind words. There is a lot of passion for the Vulcan in our development team, so we hope we have done it justice!

Mark - Just Flight

The autopilot and most of the systems would be powered off if the aircraft switched to just the battery when passing 20,000ft, as the battery only provides minimal electrical supply to the aircraft. So if it was related to that trigger, Ithe effects of a loss of electrical would occur instantly as you pass through 20,000ft, not delayed until the aircraft is cruising a 50,000ft.

It may be the AUTO AEO sensing a false trigger due to a lag spike, or it may be a control assignment that has been unknowingly triggered that has removed the electrical power, but we should be able to narrow it down further once we see what the state of the AEO station is.

Mark - Just Flight

Thank you!