Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

19 Good

About yakyak

  • Rank
    Flight Student - Solo

Recent Profile Visitors

2858 profile views
  1. Tromso and Svalbard do not use SODE. Nick
  2. Couldn't agree more with you Ray. Jeffrey is very helpful and responsive. Any small problems I've found with SODE so far has been due its implementation in a scenery, rather than from SODE itself. Nick
  3. EETN LIRF HTKJ TNCB LOWL LOWS ULLI UWGG LBWN To name just a few. Other will be able to add to the list I'm sure. Nick
  4. Hi James. Did you copy the .xml file as well. You must copy both the folder from Simobjects and the .xml file from the SODE directory. Anyway, there is a new installer from AS which has SODE v1.3 compatability. Best of luck. Nick
  5. Hi Dom. The correct path for v1.3.1 is Program Files (x86). Since v1.3.0 it has changed to that location from the FSX root directory. There will also be files placed in Program Data. During my installation, SODE automatically selected this location. Best of luck. Nick
  6. Hi James. Really happy that it's now working for you. I'm not at my PC right now but I'm pretty sure that LOWL only uses SODE for environmental effects. You will therefore not have any options using TAB S. Nick
  7. Hi James. I think you have some problems with the folders you are looking at. I'm not sure of your skill level regarding the Windows folder structure but those files you mention, such as the SimObjectAnimationModule.dll, SimObjectDisplayEngine.exe and SODEPlatformManager.exe should not be located in the directory ProgramData\12bPilot\SODE. They should be located in the directory Program Files (x86)\12bPilot\SODE. The data folder you spoke of earlier should also be in that directory. This may very well be the reason for all of your problems. In order for this to work you must be very careful a
  8. Just for the sake of accuracy the following step is partially incorrect in the last file path mentioned. 6 - Copy and paste the folders (and the files inside) HTKJ, SODE_TNCB, and UWGG from Microsoft Games\Microsoft Flight Simulator X\SimObjects\Misc to the folder ProgramData\12bPilot\SimObjects The correct file path should be - ProgramData\12bPilot\SODE\SimObjects Nick
  9. Hi James, I was resisting having to do a step by step but here goes. In order to get those sceneries working in v1.3.1 you need to do the following. First of all make sure that you work on copies of the dll.xml and exe.xml files so you can easily get them back if you make a mistake. 1 - Disable SODE v1.2.x by going to the following directory, Users\YOURNAME\AppData\Roaming\Microsoft\FSX. 2 - Disabling the SODE animation module. In the dll.xml file you must comment <Disabled>True</Disabled> in the entry that refers to v1.2x installation. It is the t
  10. Hi Rob, Yep...that's the one. I have left v1.2x installed as I still use LIRF which has not yet been recompiled to use the animated jetways in v1.31. I simply disable v1.2x via the dll.exe and xml.exe when I'm not using LIRF. Also remember that you should not have both versions running at the same time. Additionally I use TNCB, HTKJ and UWGG with no problems in v1.31 even though they were compiled using v1.2x or earlier. These don't make use of animated jetways. I use FSX and can't comment on how this will work in P3D. Also not sure about GSX as I don't use that either. Nick
  11. Update...It is available on Jeffries site, just checked. Nick
  12. I got the link from the DD site. Not sure if it's up on Jeffries site, I haven't checked. Also not not sue on the Virtuali question. Nick
  13. Hi James. Make sure that the entries in the dll.xml and exe.xml for SODE V1.2x are disabled and that SODE V1.3x is enabled. You will have problems if both versions are enabled at the same time. Nick
  14. Just FYI, I can confirm for you that on my setup HTKJ, TNCB and UWGG All work perfectly under SODE V1.3.1. You just need to move the related files from the old SODE V1.2 X directory to the new SODE V1.3x directory. Nick
  • Create New...