In some aircraft (e.g., A321 V2, A400M) the “send to avionics” function in the EFB Flight planner is missing. Please add to all aircraft (especially airliners) so we can consistently use the same charts. Keep simbrief integration (if it exists), just make it optional.
I agree, I love flying the A321 and A320 but so far every flight about halfway through the copilot starts requesting destination changes as if there’s a conflict between the simbrief intergrated INIBuilds tablet and the in sim flight planner, idk if this is a bug or intentional or a bug with the copilot ATC function either way it’s incredibly immersion breaking.
In some planes it works and others it does not. It’s up to the plane developer to add this. From what I understand the tools to do so were only recently made available. Yet, a developer may decide never to add it. Vote if you disagree!
That would be on MS to sort out. I don’t have a Navigraph subscription and with the new EFB as well as the online planner I am not tempted to change that. Trying to rebuild a route from MSFS planner in an outdated Navigraph AIRAC is a near impossible task, even with copying text routes. Maybe once modding becomes available, a solution can be found…
The EFB is a actually a very big project. It requires mapping the following:
EFB
Avionics
ATC
This has to be done for each aircraft individually by…the aircraft builders. They have done it for sim brief and will need to work with asobo to figure out how to do in a way that makes sense. Remember, this is a huuuuge departure from the 2020 world map.
It will likely take a few weeks months before implemention by aircraft builders and debugging by asobo and working title is finished for all aircraft.
However this should have been ready at launch because many of us amateur pilots used the world map in 2020 and have no experience with sim brief.
The Inibuilds Airbus planes were not designed to “talk” to MSFS 2020 and 2024’s native flight planning. Since a lot of guys prefer using Simbrief since long before 2020, their planes rely on it and are capable of importing its flight plans.
Those Airbus planes -and the new ones for 2024- still don’t talk to Working Title’s MSFS flight plan tools; hence, this request for them to integrate with these tools.
I find their answer somewhat misleading, the documentation is there and why other aircraft like the 737 is already integrated with the new EFB.
Either they don’t want to do it, or MS has to order this update from them. After that, with their future premium pack where they’ll be updating their aircraft, I suspect they’ll be charging us extra to have versions fully integrated with FS 24.
Shame on you inibuild one of the main points for me to buy 2024 was finnaly stop these discrepancies between simbrief and ms flight planning… seems like airbuses are wasted in that term…
There’s so much missing or bugging with this simulation. Its beyond frustration.
And indeed this is one of them.
I don’t mind when a game has a few issues at launch, but the state in which this simulator is in now, leaves me with one big question.
Why did they release it in this premature condition, leaving people utterly frustrated.
Reporting bugs feels like a full time job.
But thanks to people like you (OP) I hope we get the simulator we all had hoped for.
You have my vote.
I understand that inibuilds’ Airbus aircraft are designed to work with Simbrief. However, it’s important to note that Simbrief is a third-party application. The default EFB in MSFS 2024, which includes the ability to send flight plans to the avionics, was a key feature announced before the release of MSFS 2024. This feature should therefore have priority, especially since it was one of the main reasons many of us were excited to purchase the new version.
While some users may prefer Simbrief, the default EFB functionality should not be overlooked or dismissed. It is crucial for the default tools to work as advertised, ensuring a seamless experience for all users.
I completely agree with your points. The integration of the new EFB into the inibuilds tablet is crucial for a seamless experience. It’s surprising to hear that the documentation and APIs are claimed to be non-existent, especially since you’ve found the Electronic Flight Bag API.
Furthermore, the fact that Navigraph has successfully integrated its applications into the game’s basic EFB suggests that technical feasibility might not be the real issue here. It raises the question of whether the integration was simply not prioritized in the specifications provided by Microsoft.
This feature is essential for all Airbus aircraft, and having it integrated would greatly enhance the user experience. I hope both inibuilds and Microsoft can address this and provide a solution soon.