-
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 1.6.0 Install
- Thread starter PatDeBarr
- Start date
- Messages
- 45
- Country
Ok Jeffrey,
SODE 1.6.0 is installed and work in Prepar3D V4.2 ...
But in this new version, there is an object that no longer appears in the scene, it appeared with V1.5.3!
It is a aircraft whose file '* .mdl' is placed in the relocated folder 'J: \ P3D_Externes \ SimObjects \ Airplanes \' :
Is this folder no longer read in V1.60?
Error in SODE.log : [15:01:23.154] DEBUG SODE.FOLDERMANAGER : 'C:\Users\Patrick\AppData\Roaming\Lockheed Martin\Prepar3d v4\simobjects.cfg' does not exist! Extraction of SimObject Paths not performed...
But 'simobjects.cfg' in located in : 'C:\ProgramData\Lockheed Martin\Prepar3D v4' !!!
Best Regards
Patrick
SODE 1.6.0 is installed and work in Prepar3D V4.2 ...
But in this new version, there is an object that no longer appears in the scene, it appeared with V1.5.3!
It is a aircraft whose file '* .mdl' is placed in the relocated folder 'J: \ P3D_Externes \ SimObjects \ Airplanes \' :
Is this folder no longer read in V1.60?
Error in SODE.log : [15:01:23.154] DEBUG SODE.FOLDERMANAGER : 'C:\Users\Patrick\AppData\Roaming\Lockheed Martin\Prepar3d v4\simobjects.cfg' does not exist! Extraction of SimObject Paths not performed...
But 'simobjects.cfg' in located in : 'C:\ProgramData\Lockheed Martin\Prepar3D v4' !!!
Best Regards
Patrick
Last edited:
- Messages
- 611
- Country
The line above your posted one would be interesting then...
First SODE checks simobjects.cfg at C:\ProgramData\Lockheed Martin\Prepar3d v4, then it checks the AppData\Roaming path. In my case, the last one does not exist, but the first one is read.
What is defined in your simobjects.cfg at the ProgramData location?
EDIT:
I think I know what the problem is. You are placing an aircraft through SODE. While this is technically possible (an aircraft is also a SimObject), most aircraft are defined with an aircraft.cfg file, while "true" SODE SimObjects uses sim.cfg.
This SODE version only scans sim.cfg files and checks the existance of the models listed in those sim.cfgs.
When SODE then checks for existance of your aircraft, it is not found internally and that's why you get that red cross!
So with this SODE version, you won't be able to load any SimObjects (using aircraft.cfg) directly anymore, only SimObjects that are defined through a proper sim.cfg.
If that's the only aircraft you use for static placement, you can create a little SimObject container for that using a sim.cfg, then it should load.
Code:
[18:55:32.910] DEBUG SODE.FOLDERMANAGER : Extracting SimObject Paths from 'C:\ProgramData\Lockheed Martin\Prepar3d v4\simobjects.cfg'
[18:55:32.910] DEBUG SODE.FOLDERMANAGER : 'C:\Users\Jeffrey\AppData\Roaming\Lockheed Martin\Prepar3d v4\simobjects.cfg' does not exist! Extraction of SimObject Paths not performed...First SODE checks simobjects.cfg at C:\ProgramData\Lockheed Martin\Prepar3d v4, then it checks the AppData\Roaming path. In my case, the last one does not exist, but the first one is read.
What is defined in your simobjects.cfg at the ProgramData location?
EDIT:
I think I know what the problem is. You are placing an aircraft through SODE. While this is technically possible (an aircraft is also a SimObject), most aircraft are defined with an aircraft.cfg file, while "true" SODE SimObjects uses sim.cfg.
This SODE version only scans sim.cfg files and checks the existance of the models listed in those sim.cfgs.
When SODE then checks for existance of your aircraft, it is not found internally and that's why you get that red cross!
So with this SODE version, you won't be able to load any SimObjects (using aircraft.cfg) directly anymore, only SimObjects that are defined through a proper sim.cfg.
If that's the only aircraft you use for static placement, you can create a little SimObject container for that using a sim.cfg, then it should load.
Last edited:
- Messages
- 45
- Country
Hello Jeffrey,
I made a folder 'SODE_Aircraft_Stat' in 'C: \ ProgramData \ 12bPilot \ SODE \ SimObjects \' and put the plane to it :
The plane is present in the scene, but since the file 'Aircraft.cfg' is not read, this plane is in a funny position:
I am disappointed that I can no longer place objects from the general library, such as airplanes!
I have a lot of scenes that include objects placed with SODE, and all these scenes are to resume ...
Best Regards.
Patrick
I made a folder 'SODE_Aircraft_Stat' in 'C: \ ProgramData \ 12bPilot \ SODE \ SimObjects \' and put the plane to it :
The plane is present in the scene, but since the file 'Aircraft.cfg' is not read, this plane is in a funny position:
I am disappointed that I can no longer place objects from the general library, such as airplanes!
I have a lot of scenes that include objects placed with SODE, and all these scenes are to resume ...
Best Regards.
Patrick
- Messages
- 611
- Country
Dear Patrick,
I have just uploaded SODE V1.6.1 which allows again injection of aircraft.cfg based SimObjects.
It was an easier fix than I thought
P.S. Just for reference:
Your aircraft added as a sim.cfg based SimObject is below the ground because you need to define static position data (pitch and altitude). The reference point of aircraft is mostly in the middle of the object.
Here an example, you should be able to copy the values from the aircraft.cfg.
I have just uploaded SODE V1.6.1 which allows again injection of aircraft.cfg based SimObjects.
It was an easier fix than I thought
P.S. Just for reference:
Your aircraft added as a sim.cfg based SimObject is below the ground because you need to define static position data (pitch and altitude). The reference point of aircraft is mostly in the middle of the object.
Here an example, you should be able to copy the values from the aircraft.cfg.
Code:
[contact_points]
static_pitch=0.0
static_cg_height=2.2- Messages
- 45
- Country
Hello Jeffrey,
We still have problems with V1.6.1 ...
Some objects are 'absent' while they are actually present in object libraries !
Several simmers have noticed the same problems, see here : http://www.vfrnetwork.com/forums/in...e-p3d-v4/&page=10&tab=comments#comment-171194
For example :
Where are the mistakes?
Bests Regards.
Patrick
We still have problems with V1.6.1 ...
Some objects are 'absent' while they are actually present in object libraries !
Several simmers have noticed the same problems, see here : http://www.vfrnetwork.com/forums/in...e-p3d-v4/&page=10&tab=comments#comment-171194
For example :
Where are the mistakes?
Bests Regards.
Patrick
Attachments
- Messages
- 611
- Country
Hi Patrick
After looking for hours at your (and other‘s) examples, I think I found the reason for this issue.
The comparison of the simtitle as written in the xml to the one defined in the sim.cfg is very strict and must match *exactly* including lower-/uppercase. the comparison is case sensitive.
FS seems to be not that strict and does not care about case sensitiveness...
In your example, Windsock and Pole are different in upper/lowercase. Just fix the simtitle in the xml.
I might change the strictness of the checking in the next version, but for now you need to fix it in your xmls.
After looking for hours at your (and other‘s) examples, I think I found the reason for this issue.
The comparison of the simtitle as written in the xml to the one defined in the sim.cfg is very strict and must match *exactly* including lower-/uppercase. the comparison is case sensitive.
FS seems to be not that strict and does not care about case sensitiveness...
In your example, Windsock and Pole are different in upper/lowercase. Just fix the simtitle in the xml.
I might change the strictness of the checking in the next version, but for now you need to fix it in your xmls.
- Messages
- 45
- Country
Hello Jeffrey,
Thank you for the hours you spend for SODE ... and his little worries!
This version 1.6.1 works perfectly.
I understand the details about the '* .xml' files.
I pay close attention to the files I build and they apply the XML syntax.
I do not have any problem with my files, but this is not always the case with files from other sources !
Best regards.
Patrick
Thank you for the hours you spend for SODE ... and his little worries!
This version 1.6.1 works perfectly.
I understand the details about the '* .xml' files.
I pay close attention to the files I build and they apply the XML syntax.
I do not have any problem with my files, but this is not always the case with files from other sources !
Best regards.
Patrick
jtanabodee
Resource contributor
- Messages
- 3,924
- Country
I use the mdl file name everywhere related to that model such as model.folder, simcfg, XML etc. . Just double click (slowly) on the name of the mdl file and copy the name and paste to where you need it. It eliminates my headache a lot. Shuan recommended this to me and it is a very good recommendation. DO NOT type the name by yourself, just copy the name of mdl file.