Jump to content

jordanal

Members
  • Posts

    67
  • Joined

  • Last visited

Posts posted by jordanal

  1. 1 hour ago, Thomas Molitor said:

     

    As I said my priority right now is MSFS. And to be honest as a developer I don't like the P3D versioning concept of breaking stuff with each version. I might reconsider it if there is enough demand.

     

    Regards

     

    Thomas

    That's too bad - I guess my 16 years of flights in my FSFK database will have to end here.  If I can't keep the DB moving forward in P3Dv5, while waiting for everything else to catch up to MSFS, then there's no point in continuing with it at all.  I do hope there's enough response from others, to change your mind.

  2. Thomas, can you please fix FSFK 3.5 to work with P3Dv5?  Up through P3Dv4, only the main runways were missing from the NavData and airport maps and FSFK was still usable.

     

    But now using P3Dv5, almost all NavData is missing and the airport maps are useless and FSFK has become EOL.

     

    Many of us airline guys won't be switching to MSFS for a good long while - until the major developers like PMDG have ported over.

     

    Please, please fix FSFK to work with P3Dv5!

  3. Has the height that determins the type of cargo loader used been changed in AES 2.20? For my PMDG NGX aircraft, I had 1.7 for the front and 2.0 for rear cargo holds and both would use the belt-type loader. Since AES 2.20, the rear (2.0) has been using the skid-type cargo loader, which is super unrealistic for the 737. In comparison, the Level-D 763 cargo holds I have set 2.35 and I would still like to see belt-loaders even with the 763. Now my PMDG 747 has the cargo holds at 3.1 and the skid-loader might be appropriate on the Queen.

    Can you please change the height that determines when the skid-type cargo loader used to 2.5 or greater? Thanks! :big_boss_s:

    BUMP - Oliver, I just wondered if you read my post above. Thanks.

  4. Has the height that determins the type of cargo loader used been changed in AES 2.20? For my PMDG NGX aircraft, I had 1.7 for the front and 2.0 for rear cargo holds and both would use the belt-type loader. Since AES 2.20, the rear (2.0) has been using the skid-type cargo loader, which is super unrealistic for the 737. In comparison, the Level-D 763 cargo holds I have set 2.35 and I would still like to see belt-loaders even with the 763. Now my PMDG 747 has the cargo holds at 3.1 and the skid-loader might be appropriate on the Queen.

    Can you please change the height that determines when the skid-type cargo loader used to 2.5 or greater? Thanks! :big_boss_s:

  5. This is planned for a future Major Version change, at the moment it is controlled by the base level of the cargo door you have configured. If it is lower then 2 Meter, the beltloader is shown, 2 Meter an above the Container Loader is comming.

    Ah, good to know Oliver! Looking forward to it! I had no idea it was even in the current version. I guess I fly too much big-iron.

    :clap_s:

  6. Hi all,

    Loving AES more and more with each use; currently using 2.09a with FSXsp2.

    I'm wondering if it might be possible to have an option of linking (or using) a coveyor-belt type cargo/luggage loader with a given aircraft, instead of the, what appers to me, to be frieght bin hydrolic lifts, pulling up to the cargo doors?

    Perhaps some luggage carts can pull up to the bottom of the luggage coveyor-belts as well? I'm not sure about outside the U.S., but it seems to me that all I ever see in my RW pax travels, are the conveyor belt luggage loaders in use. Maybe some sort of AES option to associate one or the other with a saved AES config for a particular model?

    Regards,

    AL

  7. Hi all,

    According to FSX Airport Scanner Tool, I have two EDDM AFCADs in conflict. The first file is AF2_eddm_2010.bgl, located in the Aerosoft AFD folder - obviously this is the main file for my new Aerosoft Munich scenery. The second file, AFX_MDDE_ALT.BGL, is in my Default Terrain layer/folder (..\fsx\scenery\world\scenery). I find it weird that the ICAO identifier for this second file is backwards.

    Is the second file part of my new Munich scenery as well? Does everyone else have it too? It looks to be dated Oct. 19, 2010.

    Now I know a lot of my 3rd-party sceneries put these "ALT" bgl's in my default layer, and I'm guessing this belongs with my new Munich scenery, but why is the name backwards?

  8. I'm wondering if the continuous De-icing prompts may be a result of the recent update from v2.07 to v2.08. I never used to get this de-icing prompt with v2.07 during this summer, but this past weekend, with numerous Level-D 763 flights out of FSDT's sunny & hot Las Vegas (KLAS), I was prompted for de-icing every time. Perhaps a de-icing prompt issue has cropped-up with 2.08?

  9. I'm wondering the same thing. Using FSXsp2, AES 2.06, and ImagineSim KATL V2, it seems to work, but I get an initial error, something about Jetway~.bgl coud not be found. But yet, the jetways seem to move as expected and the rest of the AES experience seems unaffected. I've posted the question to ImagineSim support as well to find out if there's anything different about the jetway bgl V1 and V2 versions that would throw the AES error. I've registered AES with the new ImagineSim MYNN and KLGA as well but haven't had a chance to test them.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use