• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

SODE Error

spotlope

spotlope

FSDevConf team
Messages
346
Country
portugal
A beta tester of mine is reporting SODE crashes in FSX when he changes aircraft in-sim. All the SODE-driven scenery disappears and the SODE menu entry is suddenly gone. The only error I see in his log is this:

ERROR SODE.FSLOOP : SimConnect EXCEPTION! UNRECOGNIZED ID (3)

Any idea what that refers to? I see it in my log files as well so it might be unrelated to the crashes.
 
Hi Bill,

Could you attach the complete log file here, so I can see the entire context? Unfortunately in V1.4.2 I've introduced a little bug that generates exactly that error, but it is absolutely harmless and does not crash SODE. So your reported error originates from something else...

I've seen this shutdown behaviour before when SODE tries to load an invalid/incomplete aircraft.cfg, which could also explain the occurence of the crash when changing aircraft. So my follow-up question here: Does the crash occur only when changing to a specific aircraft or any aircraft?
 
No problem, Jeffrey. The user's log is below.

[22:55:56.261] INFO : SODE Version 1.4.2
[22:55:56.261] INFO : Targetting Platform 'FSX'
[22:55:56.261] DEBUG : Initializing Text Menus...
[22:55:56.261] DEBUG : Initializing Seasonal Object Handler...
[22:55:56.261] DEBUG : Initializing SimObject Lists...
[22:55:56.261] DEBUG : Initializing QuadTree...
[22:55:56.261] DEBUG : Initializing Sound Engine...
[22:55:56.293] INFO SODE.SOUNDENGINE : SoundEngine initialized.
[22:55:56.293] DEBUG : Initializing Sim Bubble...
[22:55:56.293] DEBUG : Initializing AI Monitor...
[22:55:56.293] DEBUG : Initializing IK Solver...
[22:55:56.293] DEBUG : Initializing Jetway Handler...
[22:55:56.293] DEBUG : Initializing VDGS Handler...
[22:55:56.293] DEBUG : Initializing GateNumberBox Handler...
[22:55:56.293] INFO : VDGS Pack is not found/installed!
[22:55:56.293] DEBUG : Start Main Initialization!
[22:55:56.293] DEBUG : Trying to read Settings from SimObjectsDisplayEngine.ini file...
[22:55:56.293] DEBUG SODE.SETTINGS : All Settings successfully read.
[22:55:56.293] DEBUG SODE.SETTINGS : Current Settings (1) -> SoundEngine=1; WatchDog=1; SecMenuHotKey=NONE
[22:55:56.293] DEBUG SODE.SETTINGS : Current Settings (2) -> UserJetwaySound=1; ForceHorizontalJetway=1
[22:55:56.293] DEBUG SODE.SETTINGS : Current Settings (3) -> AIDetection=0; AIJetwaySound=0
[22:55:56.293] DEBUG : Trying to find Custom Configuration files...
[22:55:56.293] DEBUG SODE.XML : Finding SDX CFG Files...
[22:55:56.293] WARN SODE.XML : \cfg\ not found. Code(2) [C:\ProgramData\12bPilot\SODE\cfg\*.sdx]
[22:55:56.293] DEBUG : Trying to build SimObject List out of Custom Config files...
[22:55:56.293] INFO SODE.XML : No SDX Files found! Lists are empty.
[22:55:56.293] DEBUG : Trying to find XML Definition files...
[22:55:56.293] DEBUG SODE.XML : Finding XML Files...
[22:55:56.293] INFO SODE.XML : xml File Found: iBlueYonder_Herons-Nest.xml!
[22:55:56.293] INFO SODE.XML : xml File Found: LOWS.xml!
[22:55:56.293] DEBUG : Trying to build SimObject List out of XML definition files...
[22:55:56.293] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml\iBlueYonder_Herons-Nest.xml'
[22:55:56.293] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml\LOWS.xml'
[22:55:56.293] DEBUG SODE.XML : XML Data successfully read and List created.
[22:55:56.293] DEBUG : List generated! Trying now to insert into QuadTree...
[22:55:56.293] DEBUG : QuadTree populated with SimObject references.
[22:55:56.293] DEBUG : Trying to generate Aircraft Parameter Map from the INI file...
[22:55:56.293] DEBUG SODE.ACFTPARAMS : Door Parameters read for 28 ICAO Aircraft Types.
[22:55:56.293] DEBUG : SDX/XML/INI Handling done! Start FS Processing...
[22:55:56.293] DEBUG SODE.FOLDERMANAGER : Starting SimObjects container scan...
[22:55:56.293] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\
[22:55:56.308] DEBUG SODE.FOLDERMANAGER : Looking for aircraft.cfg files in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\
[22:55:56.807] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Rotorcraft\
[22:55:56.807] DEBUG SODE.FOLDERMANAGER : Looking for aircraft.cfg files in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Rotorcraft\
[22:55:56.857] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\GroundVehicles\
[22:55:56.867] DEBUG SODE.FOLDERMANAGER : Looking for aircraft.cfg files in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\GroundVehicles\
[22:55:56.867] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Boats\
[22:55:56.867] DEBUG SODE.FOLDERMANAGER : Looking for aircraft.cfg files in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Boats\
[22:55:56.877] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Animals\
[22:55:56.877] DEBUG SODE.FOLDERMANAGER : Looking for aircraft.cfg files in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Animals\
[22:55:56.877] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Misc\
[22:55:56.887] DEBUG SODE.FOLDERMANAGER : Looking for aircraft.cfg files in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Misc\
[22:55:56.887] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\UT2 Aircraft\
[22:55:56.887] DEBUG SODE.FOLDERMANAGER : Looking for aircraft.cfg files in C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\UT2 Aircraft\
[22:55:57.187] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in C:\Program Files (x86)\12bPilot\SODE\data\SimObjects\
[22:55:57.187] DEBUG SODE.FOLDERMANAGER : Looking for aircraft.cfg files in C:\Program Files (x86)\12bPilot\SODE\data\SimObjects\
[22:55:57.187] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in C:\ProgramData\12bPilot\SODE\SimObjects\
[22:55:57.187] DEBUG SODE.FOLDERMANAGER : Looking for aircraft.cfg files in C:\ProgramData\12bPilot\SODE\SimObjects\
[22:55:57.187] INFO SODE.FOLDERMANAGER : SODE SimObjects Map Building completed. Size=24
[22:55:57.187] DEBUG : Initializing Internal Sounds...
[22:55:57.187] DEBUG : All Initialization Done!
[22:55:57.187] DEBUG SODE.FSPROCESS : Trying to connect to FS...
[22:55:57.187] DEBUG SODE.FSPROCESS : Connected to FS!
[22:55:57.187] DEBUG SODE.FSPROCESS : Secondary Text-Menu Hotkey not defined in INI file...
[22:55:57.187] DEBUG SODE.FSPROCESS : Setting up Connection Watchdog...
[22:55:57.187] DEBUG SODE.FSPROCESS : Entering FS Dispatch Loop.
[22:56:08.561] INFO SODE.FSLOOP : SODE connected to Simulator...
[22:56:08.561] DEBUG SODE.FSLOOP : SimState query...Running = 0
[22:56:08.561] DEBUG SODE.ACFTEXITS : No Custom Data Found for C:/Program Files (x86)/Microsoft Games/Microsoft Flight Simulator X/SimObjects/Airplanes/Vcol_dhc3p_otter_f/. Using original aircraft.cfg exit data!
[22:56:08.561] INFO SODE.FSLOOP : Successfull Registration of Reserved Key -> s Tab+S
[22:56:08.561] INFO SODE.FSLOOP : Creating Top-Menu structure...
[22:56:08.561] INFO SODE.FSLOOP : Top-Menu created.
[22:56:08.561] ERROR SODE.FSLOOP : SimConnect EXCEPTION! UNRECOGNIZED ID (3)
[22:56:08.581] ERROR SODE.FSLOOP : SimConnect EXCEPTION! UNRECOGNIZED ID (3)
[22:56:09.001] INFO SODE.FSLOOP : SeasonalObjectHandler: Variables initialized!
[22:56:37.451] DEBUG SODE.FSLOOP : Initialize Position after SimStart Event!
[22:56:38.121] INFO SODE.FSLOOP : ### FILTERING OBJECTS WITHIN SIM RADIUS OF 40000m
[22:56:38.121] INFO SODE.FSLOOP : ### Active SimObjects: 1; Active Wind Data Probes: 0
[22:56:38.321] INFO SODE.FSLOOP : + SimObject iBlueYonder_Herons-Nest:iBlueYonder Herons Nest [iBlueYonder_HeronsNest_SU]. ID: 51
[22:56:52.981] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[22:57:53.102] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[22:58:53.162] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[23:00:21.192] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[23:00:21.192] INFO SODE.FSLOOP : - SimObject iBlueYonder_Herons-Nest:iBlueYonder Herons Nest [iBlueYonder_HeronsNest_SU]. ID: 51
[23:00:21.402] INFO SODE.FSLOOP : + SimObject iBlueYonder_Herons-Nest:iBlueYonder Herons Nest [iBlueYonder_HeronsNest_HW]. ID: 171
[23:00:30.032] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[23:01:30.102] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[23:02:30.112] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[23:03:39.942] ERROR SODE.ACFTEXITS : Custom Exit Data reading error -> [FLTSIM.0]!
 
Thanks. So those (harmless) SimConnect exceptions are the ones I've mistakenly introduced in the release version, but you can disregard them (Fixed in next release).

The last line shows something interesting. In this stage, the aircraft.cfg parser is in action, and apparently it has some trouble getting data out of it. Can you ask your tester what aircraft he is loading there? Or does the crash happen with all his aircraft? Just trying to narrow it down...

If it is one particular aircraft, could he provide the aircraft.cfg to me for inspection?

Thanks.
 
Hmm, could not recreate the problem. Loaded that aircraft.cfg into the sim and SODE did not crash...
 
Interesting. I suspect there are other elements at play. I'm working with my tester to try and narrow down what other addons/tweaks he might be running that could affect the outcome.
 
I have more information on the problem of SODE disappearing. In the last day or so, I have started noticing the same thing on my system. Concurrently, I've also started getting messages from EZCA that it couldn't communicate with Simconnect (see attached msg). The problems I'm having are slightly different in FSX and FSX:SE.

In FSX, my scenery displays, but won't change texture with the seasons. However, a SODE-driven animated windmill will change direction and blade speed when I change the wind parameters in the sim. Am I correct in assuming that the wind variables SODE uses come from simconnect, the same as the MOY/TOD vars? I can't quite figure how it gets one and not the other.

In FSX:SE, the scenery just disappears after a few seconds, along with the SODE menu entry. However, the SODE process is still running in the task manager.

In P3D 3.4, everything is rock solid and runs as expected.

My current theory is that I have a simconnect problem. Would it be possible to add some sort of error checking or logging to SODE so that it informs the user when it loses contact with simconnect? My sode.log doesn't show any error concurrent with the in-sim crashes; it just stops reporting.

screencap_2017-04-05-001.png
 
Last edited:
Now it's time to create a simconnect.log: Create a ini file with the following contents
Code: 
[SimConnect]
level=normal
console=0
file=simconnect.log
and save it to C:\Users\<YourUser>\Documents\Flight Simulator X - Steam Edition Files for FSX-SE and C:\Users\<YourUser>\Documents\Flight Simulator X Files for FSX.
During the next FS run, the SimConnect server will log its messages into a <YourFSRootFolder>\simconnect.log file.

Please post that simconnect.log and the SODE.log for a crash case. This will give me most information without having to set up a TeamViewer session (which would be the next step). Thanks for your cooperation :)
 
Hi Jeffrey,

I'm having trouble nailing down my problem. After I wrote previously, I used the "repair" option in simconnect.msi for both FSX and FSX:SE, and the issue of SODE vanishing seemed to have stopped. However, I just got another crash. I've attached my sode.log and simconnect.log. This was in FSX:SE.

thanks,
Bill
 

Attachments

Thanks for the files. From the simconnect.log, I can see that SODE enters an infinite loop while trying to determine/set the objects final altitude but fails to do so...would you mind sharing your xml placement code?

EDIT: Could it be that your object is placed at sea level and the xml altitude is defined as 0.0#AGL? If yes, I was able to recreate it and can confirm that it is a bug.
 
Last edited:
Yes, that's exactly what's happening. The model in question is an island, and it's placed at 0.0#AGL. Is there another way I should be specifying that, or a workaround?
 
As a workaround, you can set the island to an defined, absolute altitude (Altitude="0.0"). This will work for sure, since you probably place the island at sea level anyway.
 
Thanks, Jeffrey. I'll try that workaround and see how it goes. In general, how do people place objects that are intended to be at ground level? In my non-SODE stuff, I've always used 0.0 AGL for nearly everything.
 
0.0#AGL is fine anywhere else except at sea level (bug in the code, fixed for the next release). In most other airport sceneries, ground level is above sea level and that's why the bug was not noticed...
 
I'm sorry to say that changing the 0.0#AGL to simply 0.0 doesn't seem to have fixed my problems. After making the change, I loaded FSX:SE and tried changing seasons from summer to hard winter. The textures didn't update. With FSX running, I checked the SODE log, and when I switched back to the sim the island was gone, along with the SODE menu entry.

I quit the sim, stopped the running SODE process in task manager, and reloaded the sim to do another flight in FSX:SE in which I tried changing seasons. I started in summer (August), then switched to hard winter (January), then to fall (September). The textures on the island never changed, even after using the reload command from the SODE menu.

I've attached my sode.log and simconnect.log.

Thanks for your help with this!
 

Attachments

Can you send me your iBlueYonder_Herons-Nest.xml and KACK_SODE_test.xml through PM? I don't need the models, just the xmls.
 
You must log in or register to reply here.
Back
Top