-
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.
FSXA module shuts down
- Thread starter jjbld
- Start date
- Messages
- 228
- Country
It occurs at about 5 min with FSX. SODE.log attached.
- Messages
- 228
- Country
I'm experiencing this with FSX and I do not hit "reset all"
- Messages
- 611
- Country
Thanks all for your help, I really appreciate it!
The SODE.log doesn't have any obvious errors, so we have to check the client-server communication of SimConnect and all its clients. To do this you have to create an empty folder (for example "SimConnectLogs") in your FSX root folder. It will hold the output of the communication.
Then you need to create a config file "SimConnect.ini" and place it in your personal "Documents/Flight Simulator X Files" folder. I have attached my ini file for convenience.
All this steps will force FSX to log all the SimConnect communication into a file simconnect.log within the SimConnectLogs folder. Also, a console window which shows the communication live during execution will open up besides the main FSX window. This all has nothing to do with SODE by the way, it is a debug feature of FSX itself for SimConnect problems.
So, when everything is set up, fire up FSX and play with SODE until it crashes. Then quit FSX and post the simconnect.log file here. Then I will be able to track down the potential problem.
Thanks again!
The SODE.log doesn't have any obvious errors, so we have to check the client-server communication of SimConnect and all its clients. To do this you have to create an empty folder (for example "SimConnectLogs") in your FSX root folder. It will hold the output of the communication.
Then you need to create a config file "SimConnect.ini" and place it in your personal "Documents/Flight Simulator X Files" folder. I have attached my ini file for convenience.
All this steps will force FSX to log all the SimConnect communication into a file simconnect.log within the SimConnectLogs folder. Also, a console window which shows the communication live during execution will open up besides the main FSX window. This all has nothing to do with SODE by the way, it is a debug feature of FSX itself for SimConnect problems.
So, when everything is set up, fire up FSX and play with SODE until it crashes. Then quit FSX and post the simconnect.log file here. Then I will be able to track down the potential problem.
Thanks again!
- Messages
- 45
- Country
Hello Jeffrey,.
My OS is Windows7 64b, and my Simulator is Prepar3D 2.5.
The latest version of SODE (1.2.0) remains active as little time, less than 5 minutes!
At startup, everything is present :
And all run ...
Less than 5 minutes after, all SODE objects have disappeared, but the module is still in memory :
I left and then restarts P3D, same bug... leaving P3D I have 2 modules in memory :
The file 'SODE.log' does not end of communication with FS... the file is attached.
Plus :
> V1.1.0 (No console) worked perfectly!
> The scenery on which I test SODE (LFSQ) is available here: https://sites.google.com/site/patdebarrsimus/home/scenery
> All the scenery of this page have SODE objects.
> My SODE libraries are here: https://sites.google.com/site/patdebarrsimus/home/sode
> I have no present gateway in my scenery.
Good Luck.
Patrick
My OS is Windows7 64b, and my Simulator is Prepar3D 2.5.
The latest version of SODE (1.2.0) remains active as little time, less than 5 minutes!
At startup, everything is present :
And all run ...
Less than 5 minutes after, all SODE objects have disappeared, but the module is still in memory :
I left and then restarts P3D, same bug... leaving P3D I have 2 modules in memory :
The file 'SODE.log' does not end of communication with FS... the file is attached.
Plus :
> V1.1.0 (No console) worked perfectly!
> The scenery on which I test SODE (LFSQ) is available here: https://sites.google.com/site/patdebarrsimus/home/scenery
> All the scenery of this page have SODE objects.
> My SODE libraries are here: https://sites.google.com/site/patdebarrsimus/home/sode
> I have no present gateway in my scenery.
Good Luck.
Patrick
- Messages
- 611
- Country
Merci Patrick
The log looks fine. I had to rewrite most of the code for version 1.2 due to another problem and may have introduced a new one...gotta love software engineering...
But I'm confident I can fix this, because v1.1 was stable.
Could you log the SimConnect communication as described in my post above module shuts down? That would be a great help.
Also, if you ever see multiple module instances in the task manager, then it's a bad sign and the results are unpredictable. You have to close the sim, kill all those module processes and start the sim again.
The log looks fine. I had to rewrite most of the code for version 1.2 due to another problem and may have introduced a new one...gotta love software engineering...
But I'm confident I can fix this, because v1.1 was stable.
Could you log the SimConnect communication as described in my post above module shuts down? That would be a great help.
Also, if you ever see multiple module instances in the task manager, then it's a bad sign and the results are unpredictable. You have to close the sim, kill all those module processes and start the sim again.
- Messages
- 45
- Country
Hello Jeffrey,
I have logged the SimConnect communication as described ...
The module hold long before shut down !!!
The Log File is 855101 lines long ... 73073 Ko and 5213 Ko in Zip format
Too large for upload in this post !
I take it here : https://onedrive.live.com/redir?res...1&authkey=!AJraQvScXlxg6VQ&ithint=folder,divx
Patrick
I have logged the SimConnect communication as described ...
The module hold long before shut down !!!
The Log File is 855101 lines long ... 73073 Ko and 5213 Ko in Zip format
Too large for upload in this post !
I take it here : https://onedrive.live.com/redir?res...1&authkey=!AJraQvScXlxg6VQ&ithint=folder,divx
Patrick
- Messages
- 611
- Country
Thanks guys for your time!
Both logs show that at some point in time, the client-server communication is halted due to "I/O Error! (2, 80004004)" and that error is coming from SODE! Also several exceptions are generated by a newly added component.
I could fix the exceptions from the new component, and I could made SODE a bit more "silent" on requesting and sending data to SimConnect. I hope the I/O error doesn't occur anymore due to the quick fixes. Of course I will explore a bit more about the root cause of that I/O error.
Find a fixed exe file in the attachment.
Both logs show that at some point in time, the client-server communication is halted due to "I/O Error! (2, 80004004)" and that error is coming from SODE! Also several exceptions are generated by a newly added component.
I could fix the exceptions from the new component, and I could made SODE a bit more "silent" on requesting and sending data to SimConnect. I hope the I/O error doesn't occur anymore due to the quick fixes. Of course I will explore a bit more about the root cause of that I/O error.
Find a fixed exe file in the attachment.
- Messages
- 228
- Country
Thanks for your quick replies Jeffrey, SODE menu and objects doesn't disappear with these new versions in FSX.
Unfortunately a new bug occurs : when you select go to airport in the FSX menu, the application crashes (even if you select an airport with no SODE triggered objects).
Best regards
Unfortunately a new bug occurs : when you select go to airport in the FSX menu, the application crashes (even if you select an airport with no SODE triggered objects).
Best regards
- Messages
- 45
- Country
Hello Jeffrey,
New episode of SODE_120 saga.
I think I found an error in the file 'Installer_SODE_v1.2.0_P3D.msi'
Reads the file 'Sode_120_02.txt' ... lines 70-80 !
For information : config files for P3D25 are here :
C:\Users\xxxx\AppData\Roaming\Lockheed Martin\Prepar3D v2
To day, I did serval tests, results are in ''Sode_120_03.txt' ...
Friendly
New episode of SODE_120 saga.
I think I found an error in the file 'Installer_SODE_v1.2.0_P3D.msi'
Reads the file 'Sode_120_02.txt' ... lines 70-80 !
For information : config files for P3D25 are here :
C:\Users\xxxx\AppData\Roaming\Lockheed Martin\Prepar3D v2
To day, I did serval tests, results are in ''Sode_120_03.txt' ...
Friendly
Last edited:
- Messages
- 611
- Country
Thanks for your in-depth testing!
Unfortunately, I can't reproduce the behaviour you are experiencing. I have installed your sceneries and all SODE objects show up fine and no disconnects so far. This is tested in FSX on Win7 64bit.
The fact that absolutely no objects are loaded in your scenario and that the module then just disconnects from itself is very strange and I have not seen it before. And without being able to reproduce it's impossible for me to get to the root of this...Of course I will try to see for errors in the code.
Unfortunately, I can't reproduce the behaviour you are experiencing. I have installed your sceneries and all SODE objects show up fine and no disconnects so far. This is tested in FSX on Win7 64bit.
The fact that absolutely no objects are loaded in your scenario and that the module then just disconnects from itself is very strange and I have not seen it before. And without being able to reproduce it's impossible for me to get to the root of this...Of course I will try to see for errors in the code.