Jump to content

phantomflyer

members
  • Content Count

    87
  • Joined

  • Last visited

About phantomflyer

  • Rank
    Flight Student - Airwork

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi 

    I got the same problem of  Yekaterinburg  airport as it is not seen by AES, could you help me plz with this. I installed my latest version 1.01 

    thanks

    Dr. Hisham Selim MD

  2. I am using AES at LIRF (to be honest, I always used AES and never even tried SODE jetways!) I guess I will HAVE to learn how to use SODE jetways in the future!.
  3. I made another error - I use AES jetways at LIRF. They work
  4. My mistake!! I meant LOWS. Sorry! But the stutters and pauses have stopped at LIRF but I don't know why.
  5. No pauses here LOWS is now using SODE 1.3, but ULLI, UUEE and LIRF using 1.22... I was having some pauses at LIRF, but they have stopped. In my FSX menu bar, under addons, I have 2 SODE entries. It appears to not be any problem for me so far. I AM, however, having crazy AES issues! I started another post for that frustrating situation. No sense muddying the waters here with that one as it's off topic... So, as recommended by Evgeny, I am indeed running both SODE 1.22 and SODE 1.3 but they are in different locations (SODE 1.3 MUST be installed in C:|Program files\(x86)) 1.22 is in the FSX root directory as a folder. Once all the developers update their SODE airports, I will be getting rid of the SODE 1.22 folder for good (I will also need to edit the exe.dll to exclude the 1.22 path). I tend to think that as long as SODE 1.2X with 1/3 MUST be in different locations. It's a good thing that Jeffrey has decided to put 1.3 out of the FSX root directory. This is most likely the reason I can run them both but not exactly "in parallel"... I believe Evgeny told me that ULLI is next for update, followed by DD, Drzweikie, an all the others. Cheers everyone :-) Bill A ***EDIT*** I decided to show my exe.dll so you can see the different paths to SODE...They are the 2 last SODE entries on the list. The 2nd to last entry is the path to SODE 1.3. The bottom entry is the path to SODE 1.22 <?xml version="1.0" encoding="windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>exe.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>Couatl</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>fsdreamteam\couatl\couatl.exe</Path> </Launch.Addon> <Launch.Addon> <Name>as_btstrp_config_manager</Name> <Disabled>False</Disabled> <Path>as_srv\as_btstrp_config_manager.exe</Path> </Launch.Addon> <Launch.Addon> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Name>UT2</Name> <Path>D:\FSX\\Flight One Software\Ultimate Traffic 2\UT2Services.exe</Path> <NewConsole>True</NewConsole> </Launch.Addon> <Launch.Addon> <Name>SODE</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Program Files (x86)\12bPilot\SODE\SimObjectDisplayEngine.exe</Path> <CommandLine>FSX</CommandLine> </Launch.Addon> <Launch.Addon> <Name>SODE</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>D:\FSX\SODE\SimObjectDisplayEngine.exe</Path> </Launch.Addon> </SimBase.Document>
  6. 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!
  7. Now LOWS has no runway lights at night because I didn't allow SODE 1.3 to install - this is the price I have to pay, Of course, if I DO install SODE 1.3, LOWS runway lights will work according to Evgeny who said I MUST install SODE 1.3 for LOWS to work properly, but the "other developers will have to update there scenery to meet SODE 1.3, he closes his email with "it's not a pleasant situation" , Of course, by updating SODE to 1.3 will cost me these airports I have - ULLI, UUDD, UUEE, an LIRF because they will all suffer from missing objects. This is a crazy situation folks. I am truly and utterly lost and baffled by this entire SODE saga. I guess I will only have to fly in and out of LOWS during the day. When you do get time Jeffrey (after your holidays) please, please post a tutorial that I can understand. I'd be extremely grateful and I know many others will too.
  8. I went to programs and features and there is no SODE there. I searched Windows software manager" and came up with what the screenshot shows - nothing
  9. I tried but I simply cannot understand a majority of it. What is "Windows software manager"? Never heard of it. SODE 1.22 is not in "programs and features" so how am I supposed to "uninstall" something that is not there? I am not a programmer and I can't seem to get a clear and easy answer anywhere about this SODE mess. I exited the SODE 1.3 installer that came with LOWS and LOWS seems to be fine - so are all my other SODE airports using 1.22 ULLI, LIRF, UUDD, UUEE, and now LOWS. Sorry to come across like this but I am very troubled by this software terminology - as I said, I am not a programmer and this SODE saga should have never happened in the 1st place. I use AES and love it. It's simple and it works. Anyway - I went to each airport and "tested SODE dll" from the addon manager drop down and at each airport I got "SODE Connection Good" That's the kind of language I can understand. Things like this (copy and paste from the migration manual) might as well be written in Greek because i cannot understand any of it: "1.1.1 Module Folder Step 1: Of course, try to uninstall the old version by using the old installer or the Windows software manager." <<<<<<<<<<<<<<<< As above - what is "windows software manager"? Never heard of it! Step 2: Check your sim platform's root folder if there is a SODE folder present. If this is the case, you can copy-paste the 'cfg', 'sdx' and 'xml' folders to the new data folder location ( C:\ProgramData\12bPilot\SODE). If there is a 'SODE_Samples.xml' in the 'xml' subfolder, you may delete it. <<<<<<<<<<<<<< This all means absolutely zip to me. Important: It is possible that sdx/xml files containing SODE jetways copied from an old version of SODE will not work with version 1.3! In this case, the add-on developer should update the jetway models and the sdx/xml according to the new SDK file and provide a product update. <<<<<<<<<<And this means zip to me. Why does it mean 'zip" to me? Because it uses the word "possibly" . I can't live with "possibly" but I can live with clear, concise, definitely will work if you do it this way. I give up! Sorry :-)
  10. Sorry - I saw "Pilot training groundwork" and assumed. I was a USNavy jet jock long ago...never got to airlines though as meeting my wife in Australia changed my entire life's path post USN days...so I just instruct aerobatics part time (I love scaring newbies)...;-)
  11. I don't want to intrude on your much deserved holidays Jeffrey so I apologize in advance - I will be as succinct as possible. I have your PDF's opened and my head is spinning. Can't I just exit the SODE 1.3 installer (that's part of the new LOWS installer) now and put in the SODE 1.3 later with the stand alone installer you have? If I do exit it now, will LOWS still work with v1.22 where it is? This will be the least demanding scenario for my rapidly ageing brain! Of course - thank you for your assistance and a ditto to the above post! never mind - I exited the 1.3 install and will install it later on when my head is clear. Apparently LOWS will work with 1.22 according to older posts in this thread. Good luck with your ongoing flight training.
  12. Hi Jeffrey, That is a good reply but doesn't answer my most worrisome question - will continuing the install of SODE 1.3 into Program Files(x86) break my SODE 1.22 reliant airports? I have not heard back from Evgeny yet...so how long can I leave this installer on hold? The "simple" question I have is this - if I cancel SODE 1.3 now, will everything (including LOWS) work with my current SODE V1.22? BillA
  13. That's what I have done - I wrote to Evgeny and I am not continuing this SODE 1.3 installation until I get a reply! The SODE v1.22 I have in my FSX root are tied into the same path (D:\FSX\SODE) in both my dll.xml and exe.xml ... It makes very little sense to me to want to install 1.3 into Program Files(x86)!! Not only that, but even if I change the path to match the dll.xml and exe.xml entries, I need to know if v1.3 will break my 1.22 reliant airports. That is the most important factor for me.
  14. This entire "SODE saga" seems to have opened a huge can of worms (for me anyway). At the least, it has me extremely confused (and worried) for a number of reasons. Why not simply use one version of SODE and dispense with all these other ones? I have SODE v1.22 sitting in my FSX/SODE/ folder. This one is for ULLI, LIRF, and some Drzweiki airports. Today, Evgeny updated LOWS and as I finish the install routine, I have stopped right here (see the top screenshot) with the final installation of SODE 1.3 that wants to install into C:\Program Files(x86)\12bPilot\SODE\ <<< why put it here and not in FSX root directory? If i go ahead and install it as it shows here, will it break my SODE 1.22 airports that I mentioned above? I am too afraid to go ahead with this installation until I know for certain it won't break anything else I have. I have taken screenshots of my current SODE folder in the FSX root directory to hopefully clarify what airports SODE 1.22 is supporting. Your replies will be greatly appreciated. Thanks, Bill A
  15. Thank you so much for your reply Otto. It works just fine this way. While on the subject, Evgeny says that the latest SODE version will be included in the full installer an about a week. I believe that is v1.3 ... Best to all!
×
×
  • Create New...