Jump to content


  • Posts

  • Joined

  • Last visited

About Rhett

Recent Profile Visitors

1121 profile views

Rhett's Achievements


Newbie (1/14)

  • Week One Done
  • One Month Later
  • One Year In Rare

Recent Badges



  1. More good news, I contacted the Lorby's Addon Organiser Developer and the latest version (addonorganizer_1_55_b07.zip) has removed the autocorrect feature. Here is a very helpful comment from the Lorby Addon Organiser (P4AO / P5AO) developer regarding the history: "Hello Rhett, Yes, that is a known issue. The latest version of P4AO doesn’t do that automated action anymore. If somebody or something are screwing up their addon references now, they will have to deal with them manually. The core issue is, that you can’t install the Airbus in certain locations, like the default autodiscovery path. The Airbus installer adds it as a CLI addon, so installing it in autodiscovery locations will create a circular reference (P3D will see it twice). This was a bug back in P3D 4.4, where the sim used the wrong add-on.cfg file, which is why P4AO corrected it. That bug had been acknowledged by Lockheed and they resolved it in V4.5, but the correction logic was still there in P4AO. IMHO the Aerosoft installer should check for a situation like that and warn you. I have participated in a thread on the Aerosoft forum too, and told them about what I found. https://forum.aerosoft.com/index.php?/topic/151513-nd-log-file-could-not-be-generated-error-message-returns/page/2/ Best regards Oliver Binder Lorby-SI" IMHO, its such a pity that the Aerosoft Airbus developers seem not to have been aware of this problem which has caused so much unnecessary frustration and wasted time for so many users / customers of the Airbus Product range (which I otherwise love). Interesting that that there is still no acknowledgement from the developers about this issue and if it is known by the developers, that they never offer it as a potential solution and continually harp on about the users systems and performance being the problem. I have not had the flapping elevator problem on departure and approach ever since I discovered the root cause - which is a massive victory - and it hasn't come back! For those not using Lorby's and also have the flapping elevator problem, I would strongly recommend that you check the above thread and confirm for yourself that the Aerosoft Airbuses are installed in the add-ons.cfg file in the following folder: C:\ProgramData\Lockheed Martin\Prepar3D v4 and not in the add-ons.cfg file in the following folder: C:\Users\User\AppData\Roaming\Lockheed Martin\Prepar3D v4 Regards, Rhett
  2. Hi all, Please note a typo slipped into the above [Package.??] entry for the A330 in P3Dv4. Aerosoft should only have one A (not "AAerosoft") in the TITLE! It should read: [Package.??] PATH=C:\Users\User\Documents\Prepar3D v4 Add-ons\Aerosoft A330 Professional TITLE=Aerosoft A330 Professional ACTIVE=true REQUIRED=false Regards, Rhett
  3. Hi RavenKraan, The preferred P3D method of identifying add-ons and their necessary components is by using an add-on.xml file in the P3D add-on folder normally located here: C:\Users\User\Documents\Prepar3D v4 Add-ons These addd-on.xml files are then read by P3D and added to a file called add-ons.cfg which contains all the add-ons used and, in the case of scenery addons, the relevant scenery layering number. Unfortunately for some reason, there are two add-ons.cfg files used by P3D, one in each of the following folders: C:\ProgramData\Lockheed Martin\Prepar3D v4 and C:\Users\User\AppData\Roaming\Lockheed Martin\Prepar3D v4 I am not sure why this is the case. but the airbus must appear in the former and not the latter. Cheers
  4. Hi all, Well I have good (amazing) news for those users who have suffered from this problem. I discovered it after confirming that the root cause also produced some related problems in P3Dv5 (but P3Dv5 seems to have better warning checks to detect the root cause problem when loading the aircraft into the sim). And as I mentioned before, it has absolutely nothing to do with systems, performance and/or settings!! The problem is created when running Lorby's Addon Organiser at any time after installation of the airbuses and running P3D as it automatically moves all the Aerosoft add-on.xml entries from the following folder: C:\ProgramData\Lockheed Martin\Prepar3D v4 OR C:\ProgramData\Lockheed Martin\Prepar3D v5 (depending on which simulator you are using) to the following folder: C:\Users\User\AppData\Roaming\Lockheed Martin\Prepar3D v4 OR C:\Users\User\AppData\Roaming\Lockheed Martin\Prepar3D v5 (depending on which simulator you are using) Lorby's Addon Organiser shows the following message when it does so (this is the very cause of the problem!): This causes the aerosoft wings flapping problem for some reason I do not understand. The solution for me is either not to run Lorby's Addon Organiser (which however is a great tool and is required if you want to create the required file necessary to run Pete Dowson's MakeRwys.exe tool for RAAS and to manage your addon entry positions and scenery order / layering, etc.), . . . Or you can follow this fairly simple procedure after running Lorby's Addon Organiser to fix the change that Lorby's addon organiser automatically made: 1. Delete the Aerosoft Airbus addon entries using Lorby's Addon Organiser (go to the "Packages" tab and find the Aerosoft Airbus packages and delete them). 2. Add the Aerosoft Airbus package entries manually back into the add-ons.cfg file (where they were placed originally by default after a clean installation of the airbuses and then followed by running P3D) in the following folder: C:\ProgramData\Lockheed Martin\Prepar3D v4 OR C:\ProgramData\Lockheed Martin\Prepar3D v5 (depending on which simulator you are using) 3. Run P3D ! NOTES: In case you need them, here are the add-on.xml entries for P3Dv4 that go into the above mentioned add-ons.cfg file (use only the ones that you have): You may have to double check the exact path and that the User folder name is corrected if necessary. [Package.??] PATH=C:\Users\User\Documents\Prepar3D v4 Add-ons\Aerosoft A318-A319 Professional TITLE=Aerosoft A318-A319 Professional ACTIVE=true REQUIRED=false [Package.??] PATH=C:\Users\User\Documents\Prepar3D v4 Add-ons\Aerosoft A320-A321 Professional TITLE=Aerosoft A320-A321 Professional ACTIVE=true REQUIRED=false [Package.??] PATH=C:\Users\User\Documents\Prepar3D v4 Add-ons\Aerosoft A330 Professional TITLE=AAerosoft A330 Professional ACTIVE=true REQUIRED=false Here are the add-on.xml entries for P3Dv5 that go into the above mentioned add-ons.cfg file: [Package.??] PATH=C:\Users\User\Documents\Prepar3D v5 Add-ons\Aerosoft A318-A319 Pro V5 TITLE=Aerosoft A318-A319 Professional ACTIVE=true REQUIRED=false [Package.??] PATH=C:\Users\User\Documents\Prepar3D v5 Add-ons\Aerosoft A320-A321 Pro V5 TITLE=Aerosoft A320-A321 Professional ACTIVE=true REQUIRED=false [Package.??] PATH=C:\Users\User\Documents\Prepar3D v5 Add-ons\Aerosoft A330 Pro V5 TITLE=Aerosoft A330 Professional ACTIVE=true REQUIRED=false Add the packages to the bottom of the add-ons.cfg file right below the last [Package.??] entry and insert the appropriate Package.?? sequential numbers for each package you are adding back (similar to when adding aircraft liveries manually to the aircraft.cfg file). This explains why the erratic / flapping elevator problem was only temporarily solved after uninstalling the airbuses, restarting the PC, running P3D (which clears the add-on entries), then installing the airbuses again, and running P3D (which places the airbus add-on entries to the add-ons.cfg file in the "correct" folder location). Hope this helps those of you who have had this terrible problem ! All the best and enjoy the airbus. Aerosoft - please can you not close this thread as there may be other clever users out there that could add more efficient or better ways of fixing the problem than my method above (after using Lorby's Addon Organiser). Regards, Rhett
  5. Thanks Pablo for the clarification and feedback - much appreciated. This is exactly what I do and it works only for about 1 flight. The next day the problem returns. I am unfortunately so tired of uninstalling and re-installing after every flight! 😞 So disappointed. I have no idea what triggers it but it definitely not performance related as after re installation, it works at the most FPS heavy of airport sceneries without any problems and then the next time it starts flapping again - no matter which airport I try or which scenery settings I apply. Its a real mystery - but sadly its the end of the road for me for Aerosoft aircraft as it happens for every install version and with both the A318/319 and A330. Exactly the same problem!! I don't have the CRJ or Airbus_Research folders. I have no problem when deleting the EFB folder. I really hope that other users could assist as I have seen quite a few with this problem. Aerosoft have not responded to my post yet. Kind regards,
  6. Dear Developers, After months and months of re-installation after un-installation, I have come to the end of my wits trying to solve this very same problem experienced in the following post (and experienced by other users). I have tried the Aerosoft recommended un-installation and re-installation process more times than I can remember or count. Every time I have disabled the anti virus program (Windows 10 built in), deleted all associated Airbus files as well as the C:\Users\User\Documents\Aerosoft\General folder. Uninstalled PTA, all REX programs, uninstalled and reinstalled the P3D Client and content. Cleared Shaders folder as per the "Airbus Professional Uninstall and Reinstall Procedure (for those having issues)" I found on the Aerosoft Forum. Every time I uninstall all the busses and then reinstall them all again after rebooting several times as instructed. I also delete the p3d config file (Prepar3D.cfg) and allow it to rebuild a new config file. Due to the response given to most users reporting similar problems, I felt that I was wasting my time asking for help and that I needed to find the solution for myself - as there are many thousands of users who apparently don't experience any problems. I have the A318/A319 and A330 busses and the exact same problem happens on every version of the Airbus installed. Please note however, that the experience I have is rather strange. The official uninstall and reinstall process works INITIALLY - but then after one or two flights it comes back again. Once the problem comes back, it stays until I follow the complete "Airbus Professional Uninstall and Reinstall Procedure (for those having issues)" process which is extremely time consuming as it resets everything and deletes all the additional liveries. A very painful and time consuming process I am no longer prepared to put up with. I am using the absolutely latest Hotfix 3 for P3V4.5 and the absolutely latest complete downloadable versions of the airbuses. I have a high end PC as well. I have tried lowering the P3D settings completely and the problem does not go away. So finally I would really appreciate some help on this as I have tried everything on my own and by reading every possible related forum topic I could find. The response from the developer(s) always seems to be that "performance" (FPS) is the cause and that because there are so many happy users out there without problems, the problem is not with the product, but with the user's system. The above post describes my problem exactly and others have seen it as well. However the solution proposed only works temporarily for me. It keeps coming back after a few days .... no matter what I do. I am happy to admit that it must be a problem with us users and I am not blaming a most enjoyable product (when it works) - but given that several users do have the same issue - there is obviously something we have in common. A forum (where others can share their experiences) seems the right place to post my troubles. What I have clearly noticed is that when the elevator flaps up and down, the trim wheel in the VC pedestal moves back and forth rapidly in time with the elevator. No amount of trimming or elevator control can stop the flapping / shacking of the elevator. I have tried re-mapping all control axis, trim controls, tried switching from P3D built in axis controls to FSUIPC axis controls and back - and none of these efforts fix the problem. I have never experienced this on any other aircraft in my entire life. Only the Aerosoft Professional Airbuses. I have almost all the well known high end aircraft addons running perfectly (PMDG, Majestic, TFDi, FS LABS A320, etc.) The problem happens mostly just after take off and just before landing. Now I know that the first thing you are going to talk about is the performance. This is ABSOLUTELY not the issue in my case. My frame rates seldom drop below 30 and I monitor them very closely on the screen and the problem happens every time - even at the most remote default airport in the word in the middle of nowhere where performance is absolutely no problem. I have checked and set the P3D display (options) settings as per the Aerosoft Airbus Professional manuals and it does not change or fix anything. I do use the built in checklist and co-pilot. It is such a pity the post linked above post was closed for further comments as the solution provided by the helpful user did not work for me - at least not permanently. I do have one specific question regarding the solution posted by the user reporting the problem in the post shared above. He made reference to the following: "First, you have to uninstall all the Airbuses, then go to Documents/Aerosoft and delete (or rename) the Airbus, Airbus_research and General Folder". I only found the following folder which I always delete completely with every re-install process "C:\Users\User\Documents\Aerosoft\General". I could not find "Airbus, Airbus_research" ? Where do I find these folders / files ? Many thanks in advance for any assistance. Rhett
  • Create New...