@dreadnought1906 For number 2, the AP light on the glare shield is not supposed to be a click spot, the autopilot button is on the center console.

@martyn
I made a couple of test flights. The first flight went well, no problems did show up. But the sound of the horn was there as soon as “ALT ARM” was selected.

The second flight I tested if the horn also was heard as I selected a higher altitude.

In levelflight I selected a higher altitude and as soon Alt ARM was selected the sound was there. So I deselected Alt ARM, and then the plane went up while “ALT” is stil selected.

@jmarkows didn't process the "From Scratch" version wasn't yet out. I probably did miss the roadmap somewhere. They plan to add things still so. It's really nice.

Many thanks for your answer.

@martyn Awesome news thanks for that confirmation Martyn.

I have the exact same issue with both the Arrow and Turbo Arrow. @Martyn when can we expect an update fixing things for the pipers? It's been 3 months with no support for these products.

@melon

yeah that's what i'm looking for too. The TO/GA press spot. did you figure it out?

I have now carried out the following adjustments to the Performance Spreadsheet:

Adjusted the Bae146 weights to more closely match those of the Just Flight aircraft. Amended the Flex temp calculation, following initial flight testing of the Bae146 versions. Corrected an error in the flex temp calculation of the EASY version of the spreadsheet.

I have just released the new version PERF06 of the spreadsheet:

https://flightsim.to/file/24722/aircraft-runway-performance-spreadsheet

I will be carrying out further performance testing and will amend the calculations again if required.
I am extremely pleased with the way Just Flight are updating the aircraft, and the speed with which they are acting to correct any minor bugs that occur. If only Microsoft could adopt the same policy....

@the-sledge There are many different classes and types of VOR and NDB stations with different power and range limitations, so it's important to determine the type and range of the VOR or NDB you are trying to use.

Based on the information below, Wolverhampton (108.6) is a low power DME, intended only for terminal area navigation. And, the Wolverhampton NDB (356) is also low power and used for terminal area navigation only... The MSFS Map also shows WOL (108.6) with a DME symbol and DME description.

https://ourairports.com/navaids/WOL/Wolverhampton_DME_GB/
https://ourairports.com/navaids/WBA/Wolverhampton_NDB_GB/

This might be a useful reference website for the area you are flying in...
https://ourairports.com/countries/GB/navaids/list.html?start=150&show=&sort=
http://www.pilotfriend.com/flightplanning/flight planning/uk_navaids1.htm

@sbanks75 said in Update 0.1.3 question:

Greetings, I updated yesterday and did a quick IFR flight and saw a couple of strange issues and wondered if anyone else saw them..

I set my final flight level for FL240 but the autopilot stopped short at about 23,600 ft. I’d moved to standard pressure and thought it may be something to do with that, but I think it also happened in the climb, I had to manually adjust to altimeter to a bit over the target alt to get it to work

In my descent, the autopilot sync with VS set went really weird. Hit the sync button, set my descent rate, hit sync again… and the autopilot tried to climb. Alt was set and armed appropriately. Tried it again during approach and it worked fine but I had what would have been a very unpleasant experience for my virtual passengers!

Last one, could not arm glide slope capture on final. Was in nav mode, and the ILS lateral nav captured fine, but had to fly it manually

Anyone seem similar issues. I am definitely not ruling out user error but the plane AP seemed to behave very differently

Thanks. That aside I loved the rest of the updates. The cockpit lighting felt really great and the EFB changes are awesome

First one (maybe others too) should be fixed with the just released 0.1.4 version.

@jmarkows

Prob not 100% what you’re after but I downloaded this from flightsim.to and printed it and it’s been very helpful

https://flightsim.to/file/31731/bae-146-checklist-procedures-quickview

@b3lt3r Hmm, I had similar with my Bravo, but no lights either on the FCU or my Bravo, but I think it may have been activated in the background. When I switched to VS mode and applied speed brakes to slow down the plane just nose dived to maintain air speed and nothing I could do could get it to work as it previously did.

@martyn

thanks for your response. I tried changing cockpit fan and packs, but didn't notice any sound difference at all in flight. I tried moving the engines from full throttle to idle and back and it's definitely the engines making the majority of the roar noise in the cockpit. I don't know if this is how it's supposed to but just reporting my opinion on it. Cheers.

P.D. I tried to record some videos to demonstrate what I mean but my iphone sound quality isn't very good so it's hard to tell the difference in loudness, but it's a lot for me.

Front & back:
https://streamable.com/bnl2in

Engines full & idle:
https://streamable.com/6ir29z

@martyn thanks, found it!

@martyn ah no problem, thank you! 😃

I can't reproduce that issue here so please submit a support ticket so we can investigate further: https://support.justflight.com/support/tickets/new