@Smeets Just some feedback, on how I fly low alt IFR with the F28: in the USA I use WxPro for flight planning, approaches. Outside USA use skyvector for IFR planning, fixes and then set up the 430 GPS unit, so do not use the EFB, except for "refuelling when using the centre tank ". Issue is getting access to approach plates (outside USA), but Google for these. Using MSFS2020, and F28-4000, which is a remarkable piece of software generated by Just Flight.

Wow! Much love Thank you.

Thanks you're the best!

Was sloved both Fokkers and the ifly 737 have need little bit troubleshooting.. Now all is fixed am Rev Version is out. Install now the New cyle and all is fine.

Fair enough. ok

Thanks for responding Martyn.

Great to see this, especially because I've long hopes that @Black-Square would start putting modern avionics in

Thank you! I just got the Honeycomb Echo Aviation Controller, basically its an X-box style controller but I am surprised how well its laid out specifically for FlightSimming, the elevator and aileron axes are surprisingly precise and tunable. It did take me awhile to figure out how to map reverse thrust, prop feather, and cutoff on the Caravan, but i finally got it, and thanks again for mentioning Axis and Ohs, I had heard about the program numerous times before but was intimidated by the interface, now I realize its a great tool for mapping anything once you get the general hang of it.

The EFB performance app attempts to get the weather data from MSFS for the airport using a few methods. If all of those fail, i.e. the MSFS weather system is unable to supply weather data for that airport, it will instead fallback to the ambient weather relative to the aircraft itself. That would include ambient temperature, which would equate to approximately SAT. Unfortunately we are reliant on MSFS providing usable weather data for that functionality, but we'll have a think about what else could be done for situations like this.

The current plan is for v1.2 to release on Thursday. That is subject to the final testing that is currently underway.

Support for the reverse thrust toggle assignment has already been added for the upcoming v1.2 update.

Apologies _ I should have read the EFB documents More carefully! There's a CFG button to press on the A/C page, Del

Hello, I think I have them but I am in vacations so I don't have them here. But do something (by memory... :-): In MSFS2024 Select Fokker 100 or 70 and place it on the ramp. Go to Settings in MSFS 2024 and turn "Developers" on. After, In Spad.next UPDATE all LVARS (always do this, many desapear after closing everything and are impossible to find) In MSFS2024, in the little menu that the "Developers" open on top, check in "tools" and drop "Behaviour". (i think is in "tools"). Find "Behaviour" anyway. "Behaviour" opens a window, in the little menu of that window, in the middle drop menu (don't remember the name" drop it, and you'll see "interaction". select. Find "Interaction" anyway Now if you hover the buttons you will see the name of the function/LVAR title over the buttons. Explore a little. Hope it helps!

@Black-Square said in Aileron trim precision - possible to mod?: I actually reviewed this today, and both the Baron and Bonanza will have values of 0.25 in the next update. I changed it to .1 Otherwise, when using the mouse, I could nerver get the plane perfectly trimmed out. Anybody here using the Brunner yoke? I am working on a profile already quite a long time, but still not 100% happy.

Whilst we haven't been able to reproduce this issue yet, the v1.2 update, due for release this week, will include a lot of AFCAS and ATS fixes and improvements. Please let us know if you still encounter this issue after installing v1.2.

Your wish has been granted. [image: 77fef1b1-daac-4bce-9e2c-b092e54a979a.png] [image: 547b70dd-b6f6-441f-8e7f-cccbfff234bb.png]

@Black-Square Thank you for the quick reply, and for trying to fix this quickly... Bug happens and it's alright, the frustrating part is that they have the fix already, and don't release it....

@Morten I wish it were so easy, unfortunately. Deciding whether to intercept and intervene in hardware input events is not something you can turn on/off on the fly. I appreciate the thought, though. As is often the case, the method I'm thinking of would actually be more realistic, with a real additional hopper tank that's fed from the main tanks. The only reason I didn't do this in the first place was because I thought it would be confusing for users looking at the native payload interface and wondering what this third fuel tank was for.