Aerosoft official retail partner for Microsoft Flight Simulator !! 
Click here for more information

Jump to content


  • Popular Topics

  • Latest Posts

    • Figured it out and this is basically a 2 part fix..    Go in to your fsx.cfg and verify that the Honeycomb\AFC_Bridge.dll is actually prefixed correctly with the actual path. I am using this as an example since i am not sure if the qzbqbhq... after afc_bridge is the same for everyone.. should look like E:\SteamLibrary\steamapps\common\FSX\Honeycomb\AFC_Bridge.dll.qzbqhqnbnhcrearlikotazuitlzunololuknqkwi=1   1) Navigate an explorer window to this folder: <FSX:SE root folder>\SDK\Core Utilities Kit\SimConnect SDK\lib (By default the <FSX root folder> is C:\Program Files (x86)\Steam\steamapps\common\FSX) 2) Run the SimConnect.msi installer file inside the folder by double-clicking. 3) Navigate to this folder: <FSX:SE root folder>\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces 4) Inside this folder are three more folders that each contain a SimConnect.msi file - run all three of them. Once you have all four steps completed, you should be all set!
    • Alessandro, I'm very happy to hear you're not suffering from the loss of power issue anymore, but sorry to hear that you are not able to see the Printer paper.    I am not up to speed on the everything in the current P3Dv4.5 version of the Airbus but I've been spending time this afternoon doing several uninstall and reinstall of the A320/A321 in order to specifically look at  your issue.  I've been at it for about an hour and I'll need another hour to complete my assessment and get back to you.   In the meantime, I'm providing you with some additional information regarding the printer issues (below) and if you don't mind I have a few questions for you that will help me run this down for you.  I believe the Fire Test issue has been resolved in the current Beta but I'll double check that.   In the past we've  seen this most often when someone has had an errant uninstall, install or update of the product, especially where computer security was not fully disabled, the installer was not run as Admin,  the updater was not run as Admin, remaining files after an uninstall were not checked for and removed if still present, and/or the user account is not an Admin account or there were folder or file permission.  The installation location can also come into play here.   I realize you have already provided some of the information I've requested below, but if  it's not too much difficulty would you please manually verify this again for me?  We like to do this whenever the simple fixes don't seem to resolve issues.   1.  Are you using P3Dv4.56HF3?   2.  What is the specific location to which P3Dv4.5 was installed to?   3. What is the specific location to which you installed the Airbus?   4.  Are you certain the product was uninstalled a check was then made for for any remaining product folders and files, a reboot was performed before installing the product again?   5. The current download version of the Airbus A320/A321 which installs is version 1.3.1.0.  The AS Updater will then install version 1.3.1.1, but one should reboot before installing that update and the AS Updater should be run as Admin.    6. Would you kindly zip and upload your "Data" folder in your reply in this thread?  It will be located in the Aerosoft A320-A321 folder where you installed the product.     Looking forward to hearing back from you!       Dave      
    • Fire test is fixed and will be released with next update.  And please separate topics for each bug in the correct section.
    • What exactly(!) did you do before you saw this?  
    • I have the exact same issue here as well. The yoke seems to work as expected and you can manually enter key bindings though fsx itself but profiles from yoke input are not actually loading in to fsx.    I believe there is an issue with the AS_HONEYCOMB_FSX-FSXSE_V1050.exe installation file itself.    ie. I am seeing the following in fsx.cfg   E:\SteamLibrary\steamapps\common\FSX\gauges\Cessna.dll.lukqlaaqlotbihnqolqwckribclnetlthnitwrlt=2 E:\SteamLibrary\steamapps\common\FSX\gauges\Cessna182s.dll.nilkiwequztzzcnolezculatabhneneaaooqlqqq=2 E:\SteamLibrary\steamapps\common\FSX\gauges\CessnaWAlpha.dll.ozqieuhnnknbziqrbwwlebiwbhernwlwhoukuuqw=2 E:\SteamLibrary\steamapps\common\FSX\gauges\Bell_206B.dll.zblrhlozqohhnktwauhzuraetaewenttulcwwhek=2 Honeycomb\AFC_Bridge.dll.qzbqhqnbnhcrearlikotazuitlzunololuknqkwi=1   and I do believe it SHOULD be the following.. E:\SteamLibrary\steamapps\common\FSX\Honeycomb\AFC_Bridge.dll.qzbqhqnbnhcrearlikotazuitlzunololuknqkwi=1 If I change the path in fsx to the above I actually get a prompt about allowing it to load. Though I still can't get it to load the keybinding profile.    Anyone still happen to have an older version of the installer?  
  • Forum Statistics

    • Total Topics
      105319
    • Total Posts
      741146
×
×
  • Create New...