Artox67

Man, download the FP from Simbrief and put him into the desired folder for AS flightplans. Than type EDDF/EGHH and put into R1 on the first INIT side thats it.

The download goes to your standard download folder. just cut/copy and past the file to the right location. Alternatively you can use the SIMBRIEF downloader where you can setup the file locations for each addon.

Hi, after you stored the flightplan from SIMBRIEF at the right location go to first inti side and type in e.g. EDDF/EGHH and put it into the field R1. After this your stored flightplan should pop up. Than follow the advise on the MCDU screen.

The busses, didn't land as expected. The whole procedure like " Remember pitch at 50FT and reduce pitch by 30FT with 2 degrees over 8 seconds" is completely not programmed. The bus has a landing behavior as a normal plane like 738. This should be corrected as soon as possible.

In this case to be up to date you need every month a new cycle. Doesn't matter from Navdata pro or Navigraph. Did you install the cycle via DataManager or manually? )Navigraph or Navdata pro?)

If I glance around all the reports in this threat and also the other threads regarding the issue it seems to be the issue occurred mostly at the A320/321. On my side I never had the issue on flights with 318/319. So it seems to be a additional bug in the 320/321 package like the 321 IAE landing behavior (6 degrees nose up)

After a couple of tests I figured out that the issue with the paper is not to reproduced by any steps taken. I suspect one or more DLL's they are responsible for the print are sometimes not correct loaded or unloaded during the flight. Today I took a flight from LEMH - LIME and all was working fine. After deboarding/reboarding for another flight from LIME - EDDK the printer stops working. (P3D was not restartet. It seems to be the process could not found the PAPER_PRINTSHEET.bpm and the PAPER_WINDOWSHEET.bpm. The 2D of the papersheets are still working after clicking behind the print slot (where the PRINTSHEET should be and clicking at the window site where the WINDOWSHEET should be. Both types are effected from this issue. 318/319 - 320/321 Best regards Artox

It was not really an issue more a cosmetic thing 😉 But yes Mathijs you can close.

Nicht alles im Leben gibt es umsonst 😄

We are currently investigating users reporting some issues with power loss (total blackout), managed speed (IAS drop) and missing paper from printer See above

Please find attached now a picture without glowing lights after replacing the standard fx_2.bmp inside of some effect data from the bus. fx_ASABV4_EXT_NAVGREEN.fx etc.

After a couple of tests I figured out that the issue with the paper is not to reproduced by any steps taken. I suspect one or more DLL's they are responsible for the print are sometimes not correct loaded or unloaded during the flight. Today I took a flight from LEMH - LIME and all was working fine. After deboarding/reboarding for another flight from LIME - EDDK the printer stops working. (P3D was not restartet. It seems to be the process could not found the PAPER_PRINTSHEET.bpm and the PAPER_WINDOWSHEET.bpm. The 2D of the papersheets are still working after clicking behind the print slot (where the PRINTSHEET should be and clicking at the window site where the WINDOWSHEET should be. Both types are effected from this issue. 318/319 - 320/321 Best regards Artox

The API.dll has something to do with the registration of P3D

Hi, try to turn off the photoreal sourrounding in the EDDF config.