Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by bpcw001

  1. On 10/27/2019 at 2:53 PM, alpha117 said:

    Why disable this function, when you can just press the 'Release', button on the top left of the UI, when you get to the correct part in the dispatch process?


    Because it tries to connect to an Eurocontrol API that is no longer open to the public. This request takes time, fails 100% and comes up with unnecessary error messages.

    A possibility to turn off the validation would be greatly appreciated.

  2. What about Athens X 1.20? Does it use SODE?

    To be honest, this SODE stuff has already given me more annoyances that I would like with an otherwise excellent Rome airport. This pause/unpause stuttering is unbearable .

  3. Wenn EDDT zumacht, wäre es schon toll, dann zeitnah EDDB mit AES-Support zu haben. Ansonsten kann man unsere Hauptstadt ja gar nicht mehr airlinermäíg anfliegen (ja ich weiß dass es Freeware-Sceneries gibt, aber ich hätte gerne AES support :big_boss_s: ).

  4. Hallo,

    habe gerade den Aerosoft Budapest Airport v2.00 für FSX erworben und wollte gerade AES 2.13 damit ausprobieren.

    Habe auch in der AESHelp for FSX den Airport aktiviert, allerdings steht dort v1.50 für Budapest.

    Und tatsächlich: auf der 2.00 Version von Budapest scheint mit AES 2.13 nix zu gehen. Auf keiner Parkposition bekomme ich AES-Services (ausser das Fenster, wo ich ein Gate für Follow-Me auswählen kann), teilweise liegen die Parkpositionen mitten in den Gebäuden!

    Ist das ein Problem mit meiner Installation oder kann AES 2.13 gar nicht mit Budapest 2.00 funktionieren?

    Auf allen anderen Airports die ich habe funktioniert AES tadellos.


  5. Can you please unzip the attached file into the AES\SCENERY Folder and replace the original file.

    Then try if the situation changed and the crash is gone or not.

    Tested your fix a couple of times. I couldn't make FSX crash no matter what I tried, so I'd tentatively say that your new file fixes the issue.

    Of course this is not representative for the whole user base.

    May I ask what changes you made? What was the problem?

  6. Can you please mal a zip of your FSX.CFG and attach it here?

    Will do as soon as I'm home from work.

    Yesterday I did some more testing and found out that the situation dramatically improves if I proceed as follows:

    1. Use an aircraft without intelliscene.cfg (Trike, or default C172 with intelliscene.cfg renamed) and place it at a parking pos on an AES-supported airport

    2. Wait until everything is completely loaded and AES displays the yellow dialog ("aircraft not configured...")

    3. With everything loaded and settled, choose any aircraft with intelliscene.cfg present

    4. Observe everything working

    I tried this a couple of times and could not reproduce any crash. I don't want to speak too soon though. Time will tell.

  7. Good day,

    I'm experiencing exactly the same symptoms beckerm13 has already described in http://forum.aerosoft.com/index.php?/topic/46228-fsx-aes-ctd/, but I'm using AES 2.12.

    I also tried the resolutions proposed in the above mentioned thread, but none of those are any good for my system.

    I've seen two types of errors: usually it's in g3d.dll, but I also get "6025 pure virtual function call" errors.

    The crashes appear sporadically, so as if this was some kind of timing or race-condition problem. It works sometimes, but mostly it doesn't.

    In case AES and the aircraft manage to load fine, then everything just works smoothly and stable as it should.

    I know it's one of those errors that make developers cringe, but if you've got any more input on this and hints what I could try, please let me know.



    Windows 7 64 bit, 12GB RAM, Intel i7 990X, Geforce GTX460 2GB,

    FSX SP2 installed in C:\FS\FSX, AES 2.12, UAC off, FSX running as admin, AES help running as admin

  8. I'm using TrackIR too and do all my flying exclusively in VC mode. It took time to get used to it, but it works very well and once it works the immersion is awesome.

    I could think of only two reasons where I'd want to use 2D panels:

    1. suboptimally designed, hard-to-hit-them-right clickspots in the VC or functionality not modeled in the VC at all (this should not happen, but some addon devs still do it)

    2. using external hardware and home-built cockpits

    VC/TrackIR is the way to go!

  9. Since we're not going to see a decent FBW implementation anytime soon, why not do a quick fix and allow for the spoilers to work even if FBW is turned off?

    I usually turn off the FACs and ELACs but leave the SECs on because otherwise I'll lose the spoilers.

    However, I had to find out that even with only this residual FBW functionality on and AP turned off, the airplane will still handle like a hog when the aircraft comes near to flaring.

    It seems that there was some "nose-up" behavior implemented for those people who are doing autolands and were complaining about hard landings/crashes, and that behavior also messes up the manual flight behavior.

    The Airbus X is a really nice bird, very good looking, with one of the best airliner virtual cockpits for FSX I've come across. Congrats to the aerosoft artwork people!

    However, the systems simulation (FBW, MCDU/FMS) still needs quite some work.

    Eagerly awaiting the "advanced" version of the Airbus X ... Keep the artwork ... work on the systems simulation!

  10. Hi,

    after installing 1.22, I lost the scratchpad of the MCDU. The LSK keys work as expected, but on "typing" on the MCDU nothing appears in the scratchpad.

    The values are not there, because when trying to transfer whatever might be hidden in the scratchpad using an LSK, the corresponding position will just show "0" or blank.

    What could be the reason? It's a fresh install (I downloaded the full 1.22 version and de-installed the previous 1.20 version before installing)

  11. No, I already told that the master caution warning only sounds when the levers are disconnected via the quick disconnect buttons. But I can't say anything about Airbus X, I can only talk about the real one.

    Exactly what I was trying to confirm with the posted video.

    Just retarding the throttles during landing should *not* trigger the master caution, hence it is something for the Aerosoft guys to look into.

  12. Can you put here the links to some of the videos where you saw that please?

    There are many. Just do a search on youtube with "a320 cockpit landing", for example:

    In none of all those videos I've watched has there ever been a master caution alert when pulling the throttles back to idle when "retard" announcement comes.

    Makes me think that the master caution alert in AirbusX when retarding throttles is not quite "real-world".

  • Create New...