Hi, I can confirm the same here, after the public patch Nov 29th (not the beta), Simbrief import is still not fixed. Before last update I had the “endless pending”, and now I’ve the brief flashing “pending” then nothing in the fms. All my other aircraft import simbrief ok, and a raw call works fine for me too in my browser. Thanks in advance for having a look on this problem 
Same here. Simbreif import is still broken.
Odd that it works for some and not others. I am not having issues. I am using the “official” Inibuilds profile and have both the plane and Simbrief set to lbs.
Are folks with trouble using the same profile? Are the weight units the same in the plane and Simbrief?
Yes, the same, plus with the official profile. It’s likely a WASM network or file permission issue to do with the module install/setup, but as there is a workaround (don’t use the MCU import, just use simbrief file downloader direct etc) then so far the devs aren’t super curious about it. They get some people saying ‘it works for me’ and then move on to more pressing bugs I imagine.
Yeah, that’s why I was asking. Once a bunch of folks say it is ok, the developers assume an environment issue and move on UNLESS folks do the legwork to help them isolate the issue.
Mark
Lots of legwork to read about here. I think pretty much every combination has been tried. The A310 was free, so no complaints. Sujet : SimBrief + A310 show me "Pending" - Systems - iniBuilds Forum
Just to chime in: Same problem for me. When pressing the RSK next to “Simbrief”, *pending is flashing briefly , but no FP is imported. Tried with my custom profile, as well as the ‘official’ profile - all units set to kgs. Also, the direct fetch link for the Simbrief FP works fine… 
This item has been tagged with feedback-logged, meaning our team will investigate and attempt to reproduce the issue. If more information is needed, we will let you know.
Thanks for the info above!
I did nothing special but today it suddenly worked!
For the first time I’m now able to load my Simbrief plan from the FMC.
Our team has not been able to get a repro yet on this item.
Can you give your exact steps please, just in case we’re doing something wrong.
Do you just go from a cold & dark aircraft, turn on the batteries and external power and then on the MCU just hit MENU / ACARS / REQUEST SIMBRIEF or other steps?
Yes, exactly, battery on, ext power on, ADIRS x 3 (instant) then MCU MENU ACARS and REQUEST SIMBRIEF .
Now it works ok.
1 Like
Thanks, yep do that exactly and no plan loaded. It’s something either local system related to what’s installed or some sort of network issue. Other people have used my simbrief alias and loaded the plan ok as well. I’ve nuked the A310-300 install fresh (including setting directory) but no luck so far. Also tried with an empty Community folder and not add-ons (so Safe Mode). It’s an odd one for sure.
Do you use GSX Pro?
1 Like
Yes, I use GSX Pro.
2 Likes
I don’t know if you have thought of this, is something in your system blocking the A310’s access to your Simbrief account?
Others have tried your alias, what happens if you use one of theirs?
2 Likes
If I use theirs it does the same, flashes pending and does not load the plan. This is after confirming it works on their A310. It does not seem to be an issue with the actual id or plan.
My simbrief id and plan also works with the iniConfig tool, in that it makes an export plan fine.
1 Like
I have the same issues and also had the endless pending issue before the update
2 Likes
Hi all, just to keep everyone updated, we are actively looking into this. No resolution at this time, but we are working on it
7 Likes
I have question: The A310 take Nav Data from the world map? Cause since update 10, third party airports like LSZH from FSDT, the SID and STAR doesnt work anymore for some aircraft like Vison Jet, Honda Jet, CJ4 WT… I tried the A310 and it does work with the STARS in LSZH so that why I ask maybe A310 use another independent NAV Data Base like the 737 from PMDG. (I mention I dont have Navigraph)
1 Like
Still not fixed after AAU1. Inibuilds says that it seems to be an Asobo WASM problem and they (Asobo) are working on it(?) to solve it with SU12