!! Windows 7 no longer supported !!

As Microsoft will stop supporting Windows 7 on Jan 20th we will be unable to test any of our
products on that platform. It may work, or it may not, but no guarantees from our side. 

Jump to content

OPabst

Developer
  • Content Count

    12992
  • Joined

  • Days Won

    73

OPabst last won the day on June 14 2019

OPabst had the most liked content!

Community Reputation

1785 Excellent

About OPabst

  • Rank
    Developer

Contact Methods

  • Website URL
    http://www.aerosoft-shop.com/products/aes/aes.html

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Sorry, but I have no idea, why your System provides C:\ProgramData\.... instead of the D:\Lookheed Martin Path. The config tool just ask the windows API to provide the Key from the Local_Maschine Key. Just checked the code.
  2. The offical registry key for P3D is not that one below HKEY_CURRENT_USER, it's the key below HKEY_LOCAL_MASCHINE: Prepar3D's registry key information is located here: >HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4 In this Keyset you must have a Value "SetupPath" with the Mainfolder of the P3D. The APPPath below the Current_User Regkey normally will also point to the same folder. The Configtools will read the offical Key below Local_Maschine and use this path to find the Prepar3D.EXE. This is needed to be excecute to register the Addons into the P3D Scenery Environment. So, when you check this regkey and correct the path there, all should work fine without reinstall the Sim. For the future it is importent to select the correct Installpath via the Option Funktion in the Setup of P3D while intalling it and not move the Sim to another Place after install. All SDK complient Addon (not only some Aerosoft Sceneries) will fail, when the SetupPath in the registry is not correct.
  3. Based on your screenshots, the P3D Simulator is installed on D:\Lockhead Martin. In the Registry the Setup Path for the Sim points to C:\ProgramData..., so there is something wrong with the P3D installation itself.
  4. Das Programm liest einfach den Installationspfad von P3D aus der Registry deines PC aus, der dann offensichtlich nicht korrekt ist. Kann es sein, dass Du das Verzeichnis von P3D nach der Installation verschoben hast?
  5. ... and the scenery has no running code or background ddl‘s. Since P3D V4 we had no CTD issues with any of the professional sceneries at all. But, as you have many other addons runing with active code, with loads files for each area, like Navdata of aircrafts, config files like Sode, GSX or FS2Crew, there are a lot of others could generate this issue.
  6. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  7. Da dieser Thread beantwortet wurde haben wir ihn geschlossen. Wenn Sie weitere Fragen haben können Sie jederzeit einen Neuen öffnen.
  8. Der Fehler war ganz am Anfang drin, ist aber seit 22. Mai 2018 in Installer gefixt. Lade den nochmal runter, nachdem Du den Browsercache gelöscht hast.
  9. Sprichst Du von der Professional Version? Verschiebe es auch mal ins Deutsche Forum.
  10. stop P3D and wait one minute, then run the SODE-ON batch again.
  11. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  12. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  13. Same as for Tennerife, no FSX or P3D V3 version planned.
  14. There is no FSX or P3D V3 Version planned.
  15. Damit es nicht noch eines Threads bedarf, hab ich es mal verschoben.
×
×
  • Create New...