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

@Martyn Thanks for the tip, I'll give it a go the next time it happens. Really appreciate the quick response.

Thanks for the great suggestion. Whilst we can't promise anything until we get a proper chance to look into this in the new year, it does sound like something we should be able to add.

Many thanks.
Season's Greeting.
S!

@Adam106 said in Low level max speed and power....too low:

Can we assume the drag performance is correct at the rest of the speed range?

The entire flight model is a compromise because MSFS does not deal well with a thick delta wing. This is where the problem with normalisation comes about - the game's core flight model cannot deal with the actual shape of the aircraft. I have grown up with Vulcans, so this for me was one I wanted to get absolutely right and (for example) the fact that the mach tuck starts at 0.94M instead of 0.88M and I can find no way to adjust that without compromising the rest of the flight model is a massive frustration! In terms of the specific of your question, the drag, well the actual figure is accurate but how the 'normalisation' works and affects the overal performance is down to Asobo. Figures and performance in the normal flight envelope seem to be on the mark. Induced drag has had to be massively increased because (again) the game cannot deal with a large triangular shape being pitched up to create drag. It means you can use aerodynamic braking on the landing run, unfortunately it also means you will bleed airspeed slightly too quickly if attempting toss-bombing unless you are very careful. I'm hoping that the promise of returning full flight model control to developers in the next version of the game will give me the chance to correct the various areas which I am not happy with.

Having said that, my research has included conversations with several Vulcan pilots and one at least will be flying this in the near future and whatever feedback comes my way will be worked into it as best I can. Climb performance, mach numbers, endurance and (most importantly) handling across the altitude range should actually be closer than our previous versions (P3D and X-Plane) because we are fairly well tuned-in to where it should be but we'll see what the above feedback gives and work on from there.

You mention manuals . . .
V.JPG image url)

And that's without the books! Just today, I was deep in the servicing manuals because of a slight issue noted with the nosewheel. I set the correct figures based on the actual measurements of the airframe, the game didn't like. So I worked it backwards and have reached a point where the problem is no longer an issue.

@brennan

Thank you

@Martyn Sorry, my bad, I had that panel switched off. I turned it on and everything works fine.

It's the livery_config.ini file in the data folder that you need to add your own livery entry to, but it's the 'title' value in the aircraft.cfg that is being checked. The livery name in the square brackets needs to match the title, minus the 'Just Flight Avro Vulcan' prefix.

For example:

Aircraft.cfg
[FLTSIM.0]
title = "Just Flight Avro Vulcan B2 XH534" ; Variation name

livery_config.ini
[B2 XH534]
hasProbe=1
has201=1
hasTFR=0
hasModernAerials=0
hasFinECM=0
isK2=0
isMRR=0

I can't make use of this as I'm all-in on Spad but I can admire the workmanship... much kudos!

BTW, JayDee has posted a hotfix on Flightsim.to and the PMS50 GTN650 works now without conflicting with the speeds card.

@NinoGZ

We aren't able to replicate the issues where the landing lights aren't extending during the approach. One quirk of the landing lights is that if the landing lights are retracted automatically at 180 knots, the landing light switches need to be moved to the RETRACT position to reset the system, before then moving them back to the LANDING or TAXI position. If the switch isn't moved back to the RETRACT position, then the lights will not extend.

Thank you for reporting the issue regarding the copilot not disappearing with the camera RIGHT SIDE CONSOLE camera. We have logged this on our internal bugs tracker and we will make sure this gets fixed in the next update to the Vulcan.

The HP Cocks clickspots are not working sounds like you may have a controller assignment that it fighting against them. Do you perhaps have any SET ENGINE 1 FUEL VALVE, SET ENGINE 1 FUEL VALVE, etc control assignments assignment to your external hardware? If so, these may be constantly triggering and preventing the throttles from moving from the idle to HP Cocks SHUT position.

Mark - Just Flight

@brennan said in v1.1 question:

same place as the original - login to your JF account, orders, download vulcan 1.1 install
Thank you

Yes, that fixed it. Thanks!

Thank you for reporting this. I have logged this on our internal bug tracker and we will investigate further.

Mark - Just Flight

Ok - that's very clear - thank you!

Loving this a/c, much like the 146 and F28... If only the A300 had a freighter variant...

@Adamski_NZ Would you be able to send a screenshot with the camera in the Navigator's position showing the issue you are experiencing?

On my end, with the GPS selected, the "RADIOS GPS" camera position is centred between the radio panel and the GPS, with both in view. So it would be useful for us to see what this looks like on your system.

Vulcan NAV GPS.jpg

Mark - Just Flight

I agree. The Vulcan is one of the most interesting aircraft in MSFS - maybe THE most interesting. So much thought has gone into it - the dynamic speed placards, for example.

Thank you @brennan. I’m resigned to the fact that when tracking a Beacon 250KIAS is my lot That said the Vulcan is a marvel and they’ve done a grand job

Guys, you're amazing. Thank you!

@Derek I'm not going to drag this on as you have made the companies position clear, and I thank you for that.

I totally get a road down the DCS route would be a huge let alone resources.

Anyway... you've done a superb job and knocked it right out the park in every respect.

Thanks again for your prompt response.