Jump to content

jdxrb

members
  • Content Count

    33
  • Joined

  • Last visited

About jdxrb

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

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

  1. All appears good so I will ignore. Thanks for your help!....appreciated!
  2. Thanks for the reply. I do have Digital Design LOWS. I assume you mean in C:\ProgramData\12bPilot\SODE to check the simobject folder and the xml entry for LOWS which I did and cant trace any entry for ULLI. Its not an airport I have purchased in the past and then removed either. Are you thinking it would be like the above log for ENGM I showed where it had a cfg file entry for ENTC in error? Strange one.
  3. Many thanks. ENAT and ENGM both fixed now!. Very strange about ULLI as I cant find any files in any folders for ULLI.
  4. I upgraded to the latest SODE 1.6.2 and since then I get the following errors on the log: [14:18:33.086] WARN SODE.FOLDERMANAGER : SimObject with SimTitle 'ENGM_Windsock_9': 'G:\FSX\SimObjects\Misc\SODE_ENGM\model.ENGM_Windsock_9\ENTC_Windsock_9.MDL' does NOT exist! [14:18:33.086] WARN SODE.FOLDERMANAGER : SimObject with SimTitle 'ENGM_Windsock_9': 'G:\FSX\SimObjects\Misc\SODE_ENGM\model.ENGM_Windsock_9\ENTC_Windsock_9.MDL' does NOT exist! [14:18:33.086] WARN SODE.FOLDERMANAGER : SimObject with SimTitle 'ENGM_Windsock_9': 'G:\FSX\SimObjects\Misc\SODE_ENGM\model.ENGM_Windsock_9\ENTC_Windsock_9.MDL' does NOT exist! [14:18:33.086] WARN SODE.FOLDERMANAGER : SimObject with SimTitle 'ENGM_Windsock_9': 'G:\FSX\SimObjects\Misc\SODE_ENGM\model.ENGM_Windsock_9\ENTC_Windsock_9.MDL' does NOT exist! [14:18:33.086] WARN SODE.FOLDERMANAGER : SimObject with SimTitle 'ENAT_Windsock_Heavy': 'UNDEFINED.MDL' does NOT exist! [14:18:33.086] WARN SODE.FOLDERMANAGER : SimObject with SimTitle 'ENAT_Windsock_Heavy': 'UNDEFINED.MDL' does NOT exist! [14:18:33.087] WARN SODE.FOLDERMANAGER : SimObject with SimTitle 'ULLI_RD3D': 'UNDEFINED.MDL' does NOT exist! [14:18:33.087] WARN SODE.FOLDERMANAGER : SimObject with SimTitle 'ULLI_RW_Lights': 'UNDEFINED.MDL' does NOT exist! [14:18:33.087] WARN SODE.FOLDERMANAGER : SimObject with SimTitle 'UWGG_show_HW': 'UNDEFINED.MDL' does NOT exist! [14:18:33.087] WARN SODE.FOLDERMANAGER : SimObject with SimTitle 'ULLI_city': 'UNDEFINED.MDL' does NOT exist! [14:18:33.087] WARN SODE.FOLDERMANAGER : SimObject with SimTitle 'ULLI_city_WI': 'UNDEFINED.MDL' does NOT exist! [14:18:33.087] WARN SODE.FOLDERMANAGER : SimObject with SimTitle 'ULLI_RunLight': 'UNDEFINED.MDL' does NOT exist! [14:18:33.087] WARN SODE.FOLDERMANAGER : SimObject with SimTitle 'ULLI_RunLight2': 'UNDEFINED.MDL' does NOT exist! [14:18:33.087] WARN SODE.FOLDERMANAGER : SimObject with SimTitle 'ULLI_SmuLights': 'UNDEFINED.MDL' does NOT exist! Of concern is the entries for ENGM and ENAT because I can find the mentioned windsock files in the specified folder. Not sure why it mentions ULLI as I don't have that scenery? Any ideas please?
  5. Well after self helping and contacting the SODE developer Jeffrey I have finally resolved the data probe issue. The xxxx SODE DYN folders are not required in FSX simobjects misc as the SODE base probe manages all the SODE scenery so I deleted them. Unfortunately I then received SODE log errors for ENAT, ENSH and TNCB. The 3 sceneries I had issues with being ENAT, ENSH and TNCB can use the base SOD data probe located in C:\Program Files (x86)\12bPilot\SODE\data\SimObjects which all my other sceneries use but the scenery xml files contained in C:\ProgramData\12bPilot\SODE\xml needs to have the address for the data probe changed. In the case of ENAT the original one was: <SimObject Name="ENAT Data Probe"> <Placement Lat="69.977489747107" Lon="23.3478127419949" Alt="30.18372703" Hdg="0.0"/> <Model SimTitle="ENAT_Environmental_Data_Probe"> The correct one is: <SimObject Name="ENAT Data Probe"> <Placement Lat="69.977489747107" Lon="23.3478127419949" Alt="30.18372703" Hdg="0.0"/> <Model SimTitle="12bPilot_SODE_Environmental_Data_Probe"> I noticed that a number of other sceneries including HTKJ and UWGG had the same address error and therefore the same SODE log error so I corrected them all. All my sceneries now show no SODE log errors and have all items showing including for TNCB the windsocks. Hope this helps others who may also not realize their scenery is not fully functioning.
  6. Hi and many thanks for the reply. To satisfy my curiosity ref the data probes working for the 3 airports i loaded each up and followed the SODE error log. For ENSH the data probe showed as loaded up and there were no log errors. For ENAT the data probe showed loaded up with no errors. The only error that shows for ENAT is the lack of the hangar door sound file but i seem to remember seeing another comment on this forum that the sound file was never part of the scenery download. I deduce from this that ENAT and ENSH data probe is working correctly - great! For TNCB i still have issues. The TNCB data probe (which i have under TNCB SODE DYN in FSX sim objects misc} shows as a warning that its not loaded in the SODE log. The PAPI,s show as loaded and they do work but no sign of the windsock which i have missing. I tried a test of moving TNCB SODE DYN to the program files {x86} simobjects where the main enviro probe is located with same error. I then moved it to programdata sim objects with same error response. I then uninstalled TNCB senery and removed all SODE reference to TNCB from program data, program files and FSX simobjects misc. I then reinstalled TNCB version 1.02. The installer told me i had a newer version of SODE 1.4 compared to that which it was installing 1.3 and the installation completed. The only ref to SODE now installed is the TNCB SODE xml file in program data xml folder and 2 folders in FSX simobjects misc which are TNCB SODE and TNCB SODE DYN. I then ran FSX again with the SODE log but still same enviroprobe error which tells me somehow SODE isnt reading the scenery....correct? Can anyone who has FSX TNCB scenery kindly load it up and check the SODE log and tell me if they get the same error and advise whether the above 2 folders are also to be found in the same location on their SIM? Thanks!
  7. I am trying to work out if following my update to SODE version 1.4 i finally have everything in the right place. I am satisfied I have SODE correctly installed in C:\Programdata with the simobject animation module,simobject display engine and the platform manager in C:\Programfiles (x86) etc etc however i note that I still have entries for SODE in my FSX folder under simobjects/misc which are specifically for ENAT, ENSH and TNCB. For each of these 3 airports i have 1 folder with objects listed called e.g. TNCB_SODE and a second called e.g. ENAT_SODE_DYN and that folder contains an environmental data probe. Questions: 1. do I still need the entries in FSX Simobjects for these 3 airports or should they moved to C:\program data\SODE\Simobjects where the rest of the installed airport objects are? 2. Should there still be an environmental data probe for these 3 airports in addition to the data probe which is in C:\program files {x86} etc etc SODE DATA SIMOBJECTS SODE_DYN which i understood now runs all airports? 3. for TNCB i do not have any windsocks - i have the pole they sit on but not the actual sock....is this correct? I do have the PAPI,s working correctly and controlled by TAB S. Regards James
  8. Nick yes you are right there is no TAB S for LOWL. Interestingly when I went back through all my SODE sceneries all were fine except TNCB where TAB S gave the PAPI options (with wrong runway which I have now corrected) but the lights never came on. When I read through the official SODE documentation again it says that I can leave SODE_TNCB in FSX Simobjects misc and a future update will likely remove the file so I copied it back from programdata to FSX simobjects misc and the PAPI,s worked. When I deleted the file again (so that I only had SODE_TNCB in programdata simobjects ) the PAPI,s again didn't work so I have left the file duplicated in FSX simobjects misc. Any ideas why? James
  9. Nick....if you heard a clanking sound yesterday wherever you are in the World that was the sound of "the penny dropping" when I finally realized where I was going wrong. Yes you are right.... I am not a Windows expert but I have managed to find my way round most FSX issues over the years - this one had me stumped. Reason was - I had no awareness of the existence of C:\programdata and therefore whenever I read a comment from you or elsewhere I stupidly assumed it referred to C:\programfiles which is why I had all the SODE files in one location. Now I get it. Have moved everything around and bingo - I get TNCB, UWGG and HTKJ working with 1.31! I purchased LOWL last week which for some reason is still not giving me TAB S options so I need to look into that. Anyway very much appreciate your patience with me....got there in the end! James
  10. Thanks Nick. I had a data folder in there for some reason. Have corrected but still no luck. Please cnf that in ProgramData\12bPilot\SODE you have the following 6 items: cfg - which is empty Simobjects containing HTKJ, SODE_TNCB, UWGG and LOWS xml - which for me has 3 xml files inside which are HTKJ_L, UWGG and TNCB_SODE Simobjectsanimationmodule Simobjectsdisplayengine SODEPlatformmanager Am I missing anything else? James
  11. Nick firstly I much appreciate your time taken to explain. I have done exactly as you describe except that in my set up the C drive simobjects are under 12bpilot\data\simobjects. I have changed both 1.31 and 1.20 to TRUE in dll and exe so that when I fire up FSX I am asked to accept or decline both versions. When I accept 1.31 I get LOWS 100% but for the other 3 I get no runway, taxiway or apron lighting at UWGG and HTKJ and at TNCB I get the lighting but no PAPI,s and with TAB S I get the answer no objects within 12km. When I activate 1.20 I get no lighting on LOWS but all the lighting works for UWGG and HTKJ and at TNCB I can control the PAPI,s. Something not right but no worries....I can live with my set up for now and as you say this product has a great future. Cheers James
  12. Nick I must have something wrong somewhere because HTKG, TNCB and UWGG def aren't working with 1.31. Cnf I am correct in having an xml entry for all 3 airports in the xml file within SODE 1.31? How come LOWS doesn't have an XML entry? Its as if 1.31 doesn't know the other 3 airports are there or they,re not talking to 1.31? Absolutely no expert on this but struggling so for now I will leave the 2 versions installed and select one or the other. Cheers James
  13. Nick thanks for the advice but for me it isn't working. In FSX root Simobjects misc I had HTKJ, SODE_TNCB and UWGG folders which I moved to C drive - SODE - Data - Simobjects - where I already have an entry for LOWS - correct? In FSX root SODE I copied the CFG and XML folders to C drive SODE noting that cfg folder is empty and xml folder has entries for TNCB, HTKJ and UWGG - correct? Right now using 1.31 SODE 1.31 and LOWS works fine but the other 3 don't - no lighting at all at HTKJ, no PAPI control at TNCB and no lighting at UWGG. Is there anything else I have to do please? James
  14. Does Graz use SODE and if so which version?
  15. Well I decided the best option was to go back to pre SODE days so uninstalled SODE 1.21 and 1.30 and also HTKJ, TNCB, UWGG and LOWS. Then I removed all remnants of SODE from DLL.XML and EXE.XML. I then reinstalled UWGG which installed SODE 1.21 followed by HTKJ and TNCB and all 3 worked including the PAPI lights switching on and off at TNCB. I then backed up my DLL and EXE and all the SODE entries in my FSX root. Next was a reinstall of LOWS which ofcourse installed SODE 1.30. I checked the DLL and XML and the entries had changed to point to my C drive rather than D where I have FSX. I loaded up all 4 sceneries and LOWS worked but the other 3 ofcourse didn't. Next step was to copy the DLL and EXE entries for SODE 1.21 and paste them so that now I have 2 entries for SODE in both DLL and EXE with one pointing to C\program files and the other to D\FSX. I changed the manual load entry for all 4 to TRUE. When I loaded up FSX I was ofcourse asked to accept the 4 entries for SODE which I did. When the loadup was complete my addon dropdown had 2 entries for SODE. For all 4 sceneries all the lighting worked but I had no DLL test and for TNCB I couldn't switch the PAPI,s on or off. When I amended the DLL and EXE back to TRUE and loaded up FSX answering yes to SODE 1.30 and no to 1.21 I got full functionality at LOWS and v.v. So now until the other sceneries are updated to 1.30 I will keep 1.21 and 1.30 installed and select one or the other each time I load up FSX dependent on where I am flying....done and thanks to the above post which suggested same!
×
×
  • Create New...