• 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.

FSX SODE Issue Again

Through prayer and perseverance; checking and re-checking; comparing and re-comparing and more praying, it works all flags are good. Thank you for all your help with the airport and you have a lot of credit given in the README. I can't think of any SODE at the moment, so you are lucky I won't be "bugging" anytime in the near future.
 
I have looked at your files.
That the flag is not visible is due to your xml file.

The following lines in red must be removed.

<SimObject Name="USPOW_FLAG">
<Placement Lat="42.775167" Lon="-71.5095" Alt="0#AGL" Hdg="0.0"/>
<Model SimTitle="USPOW_Still">
<VariableDrivenRotation Variable="WindDirection" Axis="HEADING" Animated="No"/>
<ConditionalVisibility Variable="WindSpeed" Value="0-4"/>
</Model>

<SimObject Name="USPOW_FLAG">
<Placement Lat="42.775167" Lon="-71.5095" Alt="0#AGL" Hdg="0.0"/>

<Model SimTitle="AM_USPOW_Flag">
<VariableDrivenRotation Variable="WindDirection" Axis="HEADING" Animated="No"/>
<ConditionalVisibility Variable="WindSpeed" Value="0-99"/>
</Model>

</SimObject>

Furthermore I have sorted your SimObjects (flags).
 

Attachments

I have looked at your files.
That the flag is not visible is due to your xml file.

The following lines in red must be removed.

<SimObject Name="USPOW_FLAG">
<Placement Lat="42.775167" Lon="-71.5095" Alt="0#AGL" Hdg="0.0"/>
<Model SimTitle="USPOW_Still">
<VariableDrivenRotation Variable="WindDirection" Axis="HEADING" Animated="No"/>
<ConditionalVisibility Variable="WindSpeed" Value="0-4"/>
</Model>

<SimObject Name="USPOW_FLAG">
<Placement Lat="42.775167" Lon="-71.5095" Alt="0#AGL" Hdg="0.0"/>

<Model SimTitle="AM_USPOW_Flag">
<VariableDrivenRotation Variable="WindDirection" Axis="HEADING" Animated="No"/>
<ConditionalVisibility Variable="WindSpeed" Value="0-99"/>
</Model>

</SimObject>

Furthermore I have sorted your SimObjects (flags).
Again, thanks. I was able by studying the U.S. Flag you sent last line by line against each line of the USPOW and found my error that was keeping it from being visible and it NOW IS. I will compare this one. I still have to use two sets of textures: one for the still flag from Sketchup and the other from the original USPOW you finished which uses Dietmar style textures. They just won't cooperate for me but I got it to work.
 
I will compare this one. I still have to use two sets of textures: one for the still flag from Sketchup and the other from the original USPOW you finished which uses Dietmar style textures. They just won't cooperate for me but I got it to work.

You check your mdl files with the MCX.

mcx_001.JPG



Each flag should have its own name and GUID.
Furthermore, you check the textures used for each flag.
All used textures should have recognizable names and should be available in the texture folder.

mcx_002.JPG



On the left side, select each texture that you want to change and then on the right side make the change.

mcx_003.JPG



This is how it will look after the change.

mcx_004.JPG


mcx_005.JPG


And now you only use the textures from the one texture folder.
 
I'll go through this all later after programming next week's Christian Radio Programs and report back. AND another thank you for teaching.
 
I was able to get the US/Texas to install at KDTO airport and it looks great. I am just letting it stay up all the time for now no dawn/dusk or seasons. I will work on that a little at a time. In the meantime one of the SOH members who installed KASH has a problem I am bringing here because I don't have a clue. I gave him MY files that work great but....here are his words:

"Still no luck. each of the models give me this in the log

[18:33:25.605] WARN SODE.FOLDERMANAGER : SimObject with SimTitle 'US_Flag_Still': 'UNDEFINED.MDL' does NOT exist!

my SODE has been installed by ORBX Central, maybe that is causing the issue.

Thanks, Dave"

After checking its NOT ORBX. Our files that work fine don't for him.
 
I read about the problems with SOH with SODE.
I also use SODE 1.7.1 from the SODE website and without problems.

Maybe there are on the problem PC by any reasons, duplicate entries of SimObjects or MDL files.

Just for information...
The SODE program installs itself in the following folder:
C:\Program Files (x86)\12bPilot\SODE

But there is no XML and SimObjects folder!
It does not help to create these folders there!

However, the SODEPlatformManager.exe must be executed once here.
Afterwards SODE must be registered and logged in the simulator via the SODEPlatformManager.
So that the simulator can use SODE.

Only copying the SODE program files will not be successful, you have to install SODE.
And after that don't forget the SODEPlatformManager.

The XML and SimObjects must be in the following folder:
C:\ProgramData\12bPilot\SODE
Here are also already the two folders XML and SimObjekts!
Only here SODE can access the files.
 
Provided that SODE is installed correctly and registered in the simulator, there could also be a conflict of the SODE flags with the original flags of Dietmar Loleit on the problem PC,
if these are used in other sceneries.

Therefore I changed the texture names, MDL names and the GUI.
So there should be no conflict with the original flags of Dietmar.
I changed the sim.cfg so that the xml normally doesn't need to be changed, because I didn't change the title entry.

If you use other flags, you have to adapt them or send me the textures, then I can adapt them.

Here are the flags I changed.
 

Attachments

When you showed my how to adapt the textures to animated and still I was able to change them. You also told me and I changed the GUI with MDCx in the ones that I changed but none of them are in KASH they are all in my own airports that have not been shared with anyone else. so there is no conflict there. I don't know if Sieggie has Dietmar Loleit's flag(s). I will ask.
 
It looked to me like not only Siggie has the problems with the SODE flags.

It is enough if Dietmar's flags were used in some other AddOn (which you use) and you yourself have no knowledge that the flags were used.

Therefore I have changed the names of the textures and the GUID.
As in my last attachment there should be no more conflicts.
 
It looked to me like not only Siggie has the problems with the SODE flags.

It is enough if Dietmar's flags were used in some other AddOn (which you use) and you yourself have no knowledge that the flags were used.

Therefore I have changed the names of the textures and the GUID.
As in my last attachment there should be no more conflicts.
Thank You
 
Could you give me exact instructions please how to use this as an update. Are all of the respective separate simobjects in the SODE folder in 12bpilot to be deleted and this one simobject replace all of them in that folder? Will the xml for each different location find these? If I do an update for KASH I have to have README for the users that is totally clear for them (and me) to use.
 
Now it becomes a little bit difficult for me, because I don't know your file structure in SODE.

It would be advantageous to send me all your xml and SimObjeks files, which you use for the flags, no matter which airport.
So that I can have a look at the structure.

Then we can see what we can do for the update.

Personally I would use for example only one SimObjects folder for all used flags.
 
For SODE to work properly this would still be important.
I quote from the SODE website:
"SODE requires to have the FSX-SP2/X-PACK SimConnect version installed. For FSX-SE and Prepar3D users that never had FSX installed, that version can be installed manually and is also required for several other 3rd party SimConnect add-ons."
 
Finished flying a nice flight in the US Midwest, where I lived for 60 years. I am attaching a folder for you to pack up an update for KASH for me to share with everyone so SODE problems maybe will get eliminated. If you do not mind I am keeping the flags I have no problems with at all and are not shared with anyone else the way they are. In the words of my venerable Uncle Gus, a wise sage, "if it ain't broke don't fix it". They are all working perfectly at the airports I installed them following all your advice about the xml for them. I hope Siggie followed your advice about SODE Platform Manager.
 

Attachments

I have finished the flags.

Could you send me the corresponding xml files?
These are surely also three pieces?

Then I can also combine them into one xml file.

And then pack everything together in one package.
 
Here is the SODE update of the flags in KASH.
Please test it again on your computer.
Readme is included, but you can also rewrite it.
For all the work you put into this, "danke shon" is just not enough (I have very limited Deutsch LOL) I will test it out tomorrow and let you know. I am sure its great!

Richard
 
Back
Top