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

@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. [image: e581ea72-7429-46d1-90d1-28e795e5f3ad.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.

Must have been a coincidence then. I made a 60 NM ring at it clicked exactly at that point repeatedly. Sim it is.

I noticed this on the support page SteveMk1 https://support.justflight.com/support/solutions/articles/17000137868-why-does-the-fuel-tank-centre-of-gravity-indicator-always-show-nose-heavy-

Thanks for the clear process! I also found today that not closing the #3 and #4 alternator switches on the AAP left side panel will prevent the top row extinguishing.... The fact that there are 2 panels both with alternators 1,2,3, and 4 does confuse me, hence the request for the deeper dive video. Although tbh, instructions as clear as the one you just provided for the overall electrical system would also be great

Hi Mark, Thanks for your extensive answer! I now understand the usage of the switch in the real plane and totally agree it makes sense not to simulate this (that would lead to way more questions here probably )

I believe this would have been a bug with the "State Saving" option on the EFB rather than the 3 preset save states. We have made some changes to the state saving on our latest internal build, and I cannot replicate the issue highlighted here where engine 1 tries to start under those conditions, so this will likely have been fixed amongst the other state saving fixes. Please do let us know if you still have this issue after v0.1.1 releases and we can take another look at it. The work-in-progress changelog for v0.1.1 can be found at the following link: https://community.justflight.com/topic/5705/update-change-logs-v1-0-released-edited-4-12-23 Mark - Just Flight

Many Thanks Martyn... Works fine now! (schoolboy error after I got it working....ALT wouldn't hold... I turned it but hadn't pulled it on...DOUGH!)

@wulfgar Glad to hear you got it figured out! For future reference, if the Autopilot is disengaged via non-normal means (usually either by forcing it off with excessive control inputs or by using the instinctive cut-out switches on the back of the control columns) this will cause the 28v supplies to the Autopilot to be cut-off, and therefore the autopilot will need to be reset using that Autopilot RESET switch on the starboard console. Once the RESET switch has been toggled, the Autopilot POWER knob should then hold when pulled up, and the white mechanical indicator should show white after a short period indicating that it is ready to be engaged. Mark - Just Flight