Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/25/16 in Posts

  1. OK I guess I'm not as stupid as I thought I was! I am using both SODE 1.3 (I installed it to the default location in Program Files (x86)) and edited my exe.xml to add the path to SODE in my FSX root location (I kept a backup of that SODE 1.22 folder). Now I have full functionality at all SODE reliant airports. This means the runway and taxiway lights work at LOWS! (and all other older SODE airports have gates and lights)... Can't believe I actually did it! Anyway sorry for all the moaning and groaning. That will come when the developers of LIRF, ULLI, UUDD, UUEE, update their airports to use the SODE 1.3. I guess then I can delete the old SODE folder in FSX itself and de-register it by editing the exe.xml so I don't have 2 SODE modules running together unnecessarily. This is a HUGE confidence boost for me! Thanks folks. Anyone wants to know what I did, let me know and I'll be happy to help!
    1 point
  2. ICAO: WADD (v3)NAME: Bali, Ngurah Rai Intl AptTYPE: PaywareFS: FS9/FSXDESIGNER: BDOaviation FS9 : http://secure.simmarket.com/bdoaviation-ngurah-rai-international-airport-wadd-fs2004.phtml FSX: http://secure.simmarket.com/bdoaviation-ngurah-rai-international-airport-wadd-fsx.phtml AES 2.41
    1 point
×
×
  • Create New...