ATR is not taking the flight plan if I send to avionics from EFB.
Also if I use the provided tablet to IMPORT OFP and then SET FLIGHT PLAN, I am getting the flight plan without the destination airport approach and cant add it manually either.
Only filling it up manually is working. Hopefully this will get fixed someday.
Sounds like this issue may have been fixed and should be in the next update: ATR Flight Plan Import Broken ?
Per Hans:
Nice to see Matt and Hans working out bugs together!
Is it known which planes are planned to be in the next update batch?
Not yet, we need another dev twitch stream for them to inform us of what the plans are for the future.
it would be great if they would allow us to vote each time about which planes we would like to see updated.
Please, can anyone tell me how to bind throttle 5 and 6 to a lever for the Latecoere. Folks say bind 3 throttles to one lever. I cannot get the settings to recognise me moving the 5th and 6th throttle on a Bravo so I can’t bind it to anything!
Or even all to 1 throttle lever.
Asobo, please, for heavens sake give us more throttle binding capability for up to 8 engines.
I actually find it very alarming that only now - 3 years after the ATR has been out, and a year and a half after MSFS 2024 released - that the developer is only now learning how the SDK defines entering airways, and, that the first party devs didn’t have each other’s direct contact info for solving these issues much earlier in the development… and instead are only communicating almost by accident onthe public forum?
I mean, it’s great to see progress, and interesting, but seriously, Microsoft, put the first party Devs in touch with each other for a more collaborative problem solving workflow. No wonder it takes years.
I would like to think a big slack channel could exist where devs are constantly helping each other, but I think in reality everyone is very busy just focused on their own stuff nearly all the time. I think that’s definitely the case with Working Title. They aren’t a support team. There is the dev forum where I occasionally see 3rd party devs helping each other.
In this case though, I think one of the problems was Hans wasn’t even aware he was doing something incorrectly, so he never thought to ask. I give Zadma a lot of credit here by not giving up on his bug report and actively seeking out more understanding and getting two completely separate parties in contact. That’s rare in my experience.
This is because the WASM Route Planner API is pretty new and the ATR is the first aircraft where I implemented it. And I am in contact with WT and other first party devs all the time. The reason why we discussed this on the forum was because Zad’ma posted it there.
Don’t make assumptions, man. It’s not good for your reputation.
Hans
Wasn’t it released with MSFS 2024 in November 2024?
Um… not sure what my reputation has to do with anything. I posted my reaction in a User to User thread. As a customer who has been waiting a long time for basic fixes, I’m glad the ATR is finally being worked on again - as I stated. Hopefully its reputation will improve.
Maybe we should better not talk about reputation, given the state the AAU4 ATR was released in.