Description of the issue:
I can not connect the in-flight iniBuilds EFB to SimBrief. After entering my SimBrief ID the EFB remains disconnected
every time I use this function
open EFB (iniBuilds)
enter SimBrief Pilot ID in the appropriate settings field
try to download a flight plan
error message, not connected
SimBrief ID entered
error message, not connected
Same issue with the Airbus A400M Atlas.
I can connect other airplanes without any issue, using the QR code. This is not possible with these airplanes
In your Simbrief account settings you will have a Pilot ID (usually a 6 digit number) you also have a simbrief username. If one doesnât work then the other should. Nearly all aircraft use either one ID or the other for connecting to simbrief and pulling in the flight plan.
There are of course odd cases of having too short or indeed too long a user name (as I had at one point) where your username may not be recognised.
Topic moved from Bug Reports, as that category is for reporting issues with the base simulator.
Simbrief is not included in the base simulator.
I am getting so fed-up with this game on PS5. Issues, problems, so many details that just donât work
Does the DEV team ever test this, thoroughly? How complicated can this scenario be, just open an airplane with a build-in non MSFS EFB and check all EFB functions.
On ps5
Not in the base simulator on PS5? It is not an add-on, that does not exist on PS5. On PS5, MSFS 2024 comes as one big package.
IMHO after that it is for Microsoft to sort what bug report goes to whom.
Did you contact Navigraph/Simbrief about the issue?
That is the correct group to report the issue to.
I am not employed by anyone to make any bug report. It is all good will. âNo, you should go leftâ ; âNo, this is not for meâ
So now this should go to SimBrief? Or to the Airplane developer? Why is that my problem?
I reported it, should be more then enough. Good luck with it.
On PS5 we have so many issues, I have a day job reporting everything I encounter. No more. I reported this, do with it what you want.
Anything to do with Simbrief/Navigraph should be reported to Simbrief/Navigraph.
So do it, report it to SimBrief. Why should I do that?
If you want someone to look into the issues.
MSFS does not look after problems with third party products.
Try to enter ur id not with ps5 popup keyboard, but from the plane efbâs keyboard (it should be turned on in inibuilds efb settings)
IMHO you are making a fundamental mistake here. I have no issue with SimBrief. My account functions, I can do what I desire on their website and on Navigraph software.
This issue is about an airplane developed by iniBuilds in MSFS 2024 that does not connect to SimBrief. How can I ever decide that this is a Simbrief problem, an iniBuilds problem or a Microsoft / Asobo problem? I have no access to the code, no idea what causes it.
This should be looked at by the Microsoft Asobo team, and then maybe assigned internally to SimBrief.
If we follow your logic, all airplane issues should be reported to the airplane developer, included orange avionics screens? Even if it happens to be caused by a memory issue on PS5 (apparently)? That way it becomes impossible to report issues for us users, we donât know wat causes it, and frankly, I donât want to know.
I think your handeling of this report is below par. This issue is not about a SimBrief account, it is a connection issue with very specific airplanes.
I issued a bug report to Microsoft Flight Simulator Support, same content as here. Hopefully that ends up with the DEV team.
I did , tnks. Entering anything in VR on this specific EFB is a disaster here and my system is not set up for flatscreen use. I can not even enter Caps or small letters, all caps, and only with the build-in EFB keyboard.
How do you know this is a SimBrief issue, and not an iniBuilds problem? Both airplanes that I encounter this connection issue with are developed by iniBuilds.
So you suggest I should also report it to iniBuilds, just in case? Where does that end? Could you please put this back to the Bug reports?
How on earth can you know this is a problem with a Third-Party? What if it is a problem with the airplanes, which are from the same developer? Is that also a Third-Party?
If that is the logic here, I will never issue another Bug report here on this Forum and just move on. You obviously do not value feedback from users on issues, although other entries suggest user feedback is very welcome and taken serious.
Hi Red, @TheSevenflyer is only a volunteer. He does not work for Asobo or MS. He is only here to guide you as to the correct procedure. It is not his fault how the sim developers design their procedures.
I agree it is very confusing as to whom we should report these issues. Particulalry when a 1st party aircraft uses 3rd party addons.
It always feels like someone is passing the problem elsewhere and it never gets a fix. All we can do is report stuff.
On Navigraph it is quite easy and they are usually much more responsive than MS/Asobo. Their bug reporting system is very similar to the one used here.
I understand, tnx. My issue is with the âThird Partyâ designation. On PS5, we have no community folders or anything like that, it is a closed system. E.g. we can not add SimBrief to the MSFS EFB, just not possible (unfortunately). SimBrief integration is a bit of a disaster anyway on PS5.
My SimBrief connection with one other iniBuilds airplane, the F-27 (that can use a QR code to connect) works ok. I think there is a problem with these airplanes.
I fail to see how this can be a Third Party issue on PS5.
And I just tried the Navigraph forum. They donât even have a category for my issue.
They can not do anything with PS5 or playstation it seems. A search on these words gives no results.
It is not a plugin issue, there is no such thing on PS5.
I have no issue with SimBrief dispatch, that does not exist on PS5.
This frustrates me very much and should not be my problem
@TheSevenflyer please note âŠ
Yes, I have a ps5 too. The airbusâs are a difficulty with navigraph/simbrief. Particularly with career mode.
I would suggest that when MS commissioned the 3rd party dev to make these, ps5 wasnât in the picture.
There is a PS5 feedback form in the official sections of the forum. It might be worth making a comment there about the airbus issue.
You may find it already has been reported.
I fear though, it is 1 of those annoyances were going to live with for a while until MS throws some money at Inibuilds or working title to get done.
The F27 was made much later which is why simbrief is likely there.
