Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

6 Neutral

About BTenhaaf

  • Rank
    Flight Student - Airwork

Recent Profile Visitors

2822 profile views
  1. This is what it looks at my P3Dv4.5 - my LIPE Afcad is dated 11.04.2018 (iso 27.03.2018) Rgds Bernhard
  2. Did you check this (once more): In FSX/P3D main/scenery/0502/scenery check if you have those files disabled/removed APX43200.bgl CVX4320.bgl It seems that the scenery 0502 has received some update as there are several files ending ".bgl.p3dini" and the new once have a creations date in midst of 2018 (iso 2017).
  3. Hast Du denn die DO228 bei Carenado registriert (angemeldet) ?
  4. Sorry - is it really January 1, 2019 or should it read January 1, 2020 ?
  5. Here is my file - please rename the original file "AF2_LPPS.bgl" into "" and copy the attached file into the scenery folder of Porto Santo. LPPS_ADEP4_ADE.bgl
  6. I checked my AFCAD file for LPPS (latest version) by using ADE. It states under "Runway": 36/18 but under "Starts" there you find 19/01. This can be easily fixed by yourself using the ADE tool. I did this some days ago. I don't know if it is allowed, to pin the "revised" file hier as it may be the property of Aerosoft.
  7. Hello Kai, I had the same problem including the wrong AS Updater when I updated Bergamo to 1.01.1; it seemd the in the frirst version of the updater, there was a mistake. Please see here: After a second download after that everything was ok - perhaps Simmarket did not get the corrected version of the updater to 1.01.1, which has the same version number then the first (corrupted) one
  8. Version V1011 of Bergamo Professional is the latest version; you mentioned version, but this is for the Bergamo extended version only - not for Professional
  9. Best for me was to uninstall Cologne-Bonn, download the new complete files once more and then install it with adminrights. After that, all was ok.
  10. Some Threads ago there was a hint that the PREPAR3DV4 Organizer from Lorby SI makes this change after you have changed the sequence by using the Organizer
  11. The Addon-Path for Updates is wrong: It should be only : ...\Prepar3d v4\Cologne-Bonn Professional and not ... \Prepar3d v4\Cologne-Bonn professional\SimObjects.
  12. [EDIT MOD] This post was merged from another topic into this one. The next post in this topic is the original first post in this topic. This post should be displayed after that... Hi Pat - had the same problem - and the solution took me some hours. First to see if P3DV4.3 is running, deactivate in your LM-Folders in C:\"(your name) APPDATA\Roaming" and in C:\ProgramData\ follwing items: addon-on.cfg, dll.xml and exe.xml (rename them - don't delete !!) and then start P3D once more. It is now building new items. And then, you can one by one reactivate the old items and see, were the mistake is (only on at a time and restart P3D). My finding was in the add-on.cfg in C:\Programdata\LockheedMartin - it seems that LM will not accept double sceneries compared to the add-on.cfg in APPDATA\Roaming. That's how i got P3D running. For editing *.xml- and *.cfg-data I don't use the normal editor but "Notepad++. Hop that helps a little bit
  13. Normally PANC Prof and PAFA Prof should not be shown in the scenery.cfg as they are installed via the xml-method. You should check the installation in your C:\programdata\lockheed martin\Prepar3Dv4\add-ons.cfg if this file contains PAFA / PANC. You can also unckeck PAFA in your scenery.cfg and see if then all is ok. If PAFA is not in the above folder, you should uninstall and reinstall PAFA.
  14. sorry to say, but PAFA is not covered by FTX SAK - too far north
  • Create New...