investigating Ini request: ERROR DOWNLOADING DATA

[KLEE330]

Hello everyone,I have problem with Ini request function 

Although the EFB can import flight plan  from simbrief Successfully, but in the mcdu , when you click ‘ini request’ it just says’Ini request: ERROR DOWNLOADING DATA ’ . And you have to repeat 2 to 20 times click the ’ini request’ until it imports your flight plan successfully 

And I checked the simbrief aircraft model which is the Ini official profile and I try to change my network and I try to use vpn also tried vpn tun , I also checked my efb simbrief account setting, but all of these didn’t work.

Actually I didn’t change any efb settings since I first configured the EFB settings properly，and in the previous version like 1.0.5 before it all works perfectly, but in the 1.0.6and 1.0.7this situation always happens 

Edited 8 hours ago by KLEE330

[richboy2307]

Hi @KLEE330

That is odd, there have been no changes made to the FMS SB Import functions since launch so its unlikely to have been caused by updates. Try the following:

• Re-input your Simbrief ID (numbers only) but using the on-screen keyboard of the EFB instead (you can enable it in the settings).
• Run the sim as admin. The plan is requested via SimConnect to SimBrief and then downloaded into your "work" folder, which is a temporary folder that could be restricted by Windows UAC. Running the sim as an admin may help if access permissions are causing the problem.
  
  You could also manually monitor the files in the "work" folder to see if they are in-fact being downloaded/updated. Namely the Simbrief.json file and the .fpl file in the flightplans folder found there.
  
  Work Folder Paths

  Quote

  Steam: %APPDATA%\Microsoft Flight Simulator 2024\WASM\MSFS2024\inibuilds-aircraft-a340\work\
  MS Store: %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\inibuilds-aircraft-a340\

• Try running with an empty community folder to rule out any addon conflict. While this is rare, occasionally some addons can affect Simconnect behaviour, which in turn could be causing your issue. You can test this quite easily by temporarily renaming your existing Community folder to _Community, then running the simulator to test. To restore, simply close your sim, delete the new Community folder and rename  _Community back to Community.

Hopefully one of the above resolves your issue. Please let us know how you fair.

Thanks!