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

A little update and I don't understand the results, the ctrl + G has worked in the vulcan but in FBW A320 for example, it's never worked and I'm fairly sure I tried it in the JF Hawk and it didn't work there either. I'll retest that. I have reloaded the FBW A320-Dev and ctrl+G does not work so it seems to be aircraft specific whether it works or not, is this something down to the publishers? Just Flight replies appreciated on this thought.

Your best bet would probably be to contact Just Flight Support. They can probably provide an answer to this kind of problem. https://community.justflight.com/topic/2/product-support

For the autopilot to capture the localiser, the following steps are required: The autopilot must be engaged (IN indicator white) The correct frequency for the ILS must be tuned into the NAV radios The NAV selector must be rotated to the LOC position (GP if glideslope is to be captured too, and rotate the pitch selector to APPROACH for glideslope guidance). Pull the autopilot TRACK knob up (ILS should be indicated on the artificial feel indicator) Once within intercept range of the localiser and the aircraft in the configuration listed above, the aircraft will automatically capture the localiser. Hope that helps. Mark - Just Flight

Thanks for reporting the camera behaviour. I have logged that on our internal bug tracker and we'll take a look at a that ahead of the next update to the Vulcan. in the mean time, disabling the "COCKPIT PILOTS" option on the EFB will remove the copilot from view. The exhaust effect is not something I can replicate on my end, so I suspect it is a conflict with another product/mod. In order to confirm this, I would recommend renaming your Community folder to something like "Community.old", then creating a new Community folder named "Community" in the same location, and then installing the Vulcan into the new folder. Launch MSFS with only the Vulcan in your new Community folder and then see the effects are appearing as normal. If they are, that confirms there is a conflict with another mod in your ".old" Community folder. Hope that helps. Mark - Just Flight

@Delta558 thanks for checking! Of course not, but knowing pilots making error (which is how I ended up even thinking about this)

In v0.1.3 of the Vulcan, we upgraded the GPS from the Aera GPS to the G3X Touch for better MSFS 2024 compatibility. Therefore, the functionality of the GPS has changed slightly as the G3X Touch is a more advanced GPS. To cover each of your points: If a flight plan is created in the MSFS 2024 EFB, the "Send Route To Avionics" button must be pressed in order to import the route into the GPS. If a flight plan is created manually within the GPS, the flight plan must have a departure airport and a destination airport set in order for the autopilot to couple with the GPS (if a flight plan is created in the GPS with only a departure airport and waypoints, the route will be displayed, but the autopilot coupling will not function with an incomplete flight plan). In order for the autopilot to track the GPS flight plan, the ENGAGE knob must be pulled (with IN indicator showing white), the TRACK knob must be pulled, and REMOTE must be selected on the navigational selector. This is a known side effect of a workaround we have put in place to improve touchscreen display interactions in our aircraft in MSFS 2024. If the workaround is no longer required after future MSFS 2024 Sim Updates, we will update the logic so that control cannot be clicked through touchscreen displays. The GPS can also be moved on top of the glareshield by clicking the upper bezel. As the G3X Touch is a default GPS unit in MSFS 2024 (developed by Working Title), we sadly don't have any control over the scaling of the GPS. To circumvent this, we have added custom cameras for each GPS position which moves the camera closer to the GPS display. These cameras can be toggled either via the MSFS Camera menu, or via a clickspot on the right bezel of the GPS. Mark - Just Flight

Thx a lot! I know the speed bleed-off is supposed to be huge - but only at high AoA's. Check the videos of 558's wingovers (especially Kev's infamous one at the last RIAT display) - 558 was able to keep the vertical climb a lot longer than JF's Vulcan. I'd estimate that about 2.500 ft of vertical climb are missing. One main problem is also the lack of nose-up elevator authority at low speeds - one ought to be able to pitch up quicker (alse deducted from the videos). I's a pity - a year after her last flight I spent a RIAT lunch break with Kev, but neither bothered to ask him about all the details of her flight dynamics nor even dreamed of being able to fly such a magnificently modelled 558 in some kind of photo realistic flight simulator...

This isn't something we were aware of, however, we suspect we may know the reason behind this (relating to how LODs are handled within MSFS 2024). We'll log this on our internal bugs tracker as something to investigate ahead of the next Vulcan update. Thanks for reporting this! Mark - Just Flight

@Derek Seems to be working as expected again after the update

@Martyn much appreciated, I wasn't sure if the fix would apply to FS2024 as well.

The Vulcan was submitted to the MSFS 2020 marketplace last week, so if everything goes according to plan, it should be available either this coming Thursday or the following Monday. We will also submit the Vulcan to the MSFS 2024 marketplace at the earliest opportunity. Unfortunately at this time, we don't know when the MSFS 2024 marketplace will become available. Mark - Just Flight

I resolved this by myself at this time, I reverted to search my entire C: Drive for the aircraft folder, threw that into my FS2024 Community folder manually, there we have it, fully flyable from this point. :D!

I have downloaded the FS2024 Vulcan from the JF store, I have extracted the folder from the zip file, then ran the setup, It installed "Somewhere" but the aircraft is not in my FS2024 aircraft selection screen? Nor is the Vulcan Aircraft folder in my FS2024 "Community" folder. I am redownloading the zip file again (because i deleted my first zip) and am going to run as admin this time lol, maybe this could be the reason?

ok great, thank you! Look forward to the release!