Airport Enhancement Services

Support for AES

3149 topics in this forum

  1. Pinned topics
    • 784 replies
    • 371991 views
    • 50 replies
    • 6969 views
    • 324 replies
    • 66096 views
    • 92 replies
    • 33761 views
    • 4 replies
    • 1207 views
    • 0 replies
    • 961 views
    • 132 replies
    • 81918 views
    • 13 replies
    • 16266 views
    • 11 replies
    • 6374 views
    • 11 replies
    • 22220 views
    • 0 replies
    • 5112 views
    • 7 replies
    • 26873 views
    • 1 reply
    • 9496 views
    • 7 replies
    • 16193 views
    • 18 replies
    • 17419 views
    • 2 replies
    • 9307 views
  2. Topics
    • 3 replies
    • 206 views
    • 5 replies
    • 116 views
    • 2 replies
    • 353 views
    • 2 replies
    • 161 views
  3. Solved

    • 4 replies
    • 143 views
    • 3 replies
    • 208 views
    • 1 reply
    • 94 views
    • 10 replies
    • 415 views
    • 0 replies
    • 144 views
  • Posts

    • Update - I got it working by installing the SODE as mentioned by Thorsten and then turning the _SODE from .off back to .bgl and vice versa for the other one and I now have GSX working and the jetways are also there.
    • Ok Tom, here are the results of the test.... With base scenery Orbx Global, Vector and openLC FlyTampa CYUL and CYYZ activated PMDG 737 ASN FSDreamteam GSX REX 4 Texture Direct & Soft Clouds (with clouds, runways and taxiways resolution set to 1024) The remaining VAS was 1041148. Then, with Vectors deactivated, it was 1507120. So, Vector used up roughly 466 MB. Then, with Orbx Global and openLC deactivated, it was 1563400. So, Orbx used up roughly 56 MB. Then, with ASN deactivated, it was 1556244. Basically no effect because ASN has more of an effect on frame rate than VAS. Then, with the default Baron instead of the NGX, it was 2064928. So, the NGX used up roughly 509 MB or half of a GB. Finally, with lower display settings, it was 2289912. A slight increase of roughly 225 MB   Ok, now I've done what you suggested yet I still don't understand the point of this test. All it's telling us is that Vector and the NGX are eating up most (~ 1GB) of the VAS memory, which is really nothing new. We already know this. What I'd like to know is how is SIMstarter helping with OOMs if it can't do a thing about this common setup. In other words, what's the point of having SIMstarter if there is nothing it can do to prevent OOMs with a highly common setup as mine? I'm not trying to be argumentative nor condescending. Claims have been made that it helps with frame rate and OOMs, yet I fail to see the proof of that. If by simply installing Vector and the PMDG NGX, which many pilots have, renders SIMstarter ineffective to live up to its claims, then what's the point?
    • I would like to see one titled "Memory Flights."   This is where a contestant would take a sim-reenactment picture of a special aviation moment in their life (I.E First flight, first time at the airport, etc...) The winner would be judged both on their screenshot and their narrative/why the shot was special to them.
    • I did the fix and it's worked but GSX isn't working for some reason. GSX comes up with a green bar message at the top in P3Dv3.3 telling me that it can't find the _SODE file etc.
    • I got the Jetways working now...only thing is they don't line up correctly with doors...they seem too low when connected with aircraft..I tried it on an Airbus A319 and top of door was above jetway....just a thought!