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

v1.5: just one simobject missing

Messages
1,123
The updated SODE installed a treat, well done.
Funny to load up P3Dv4 to test my jetways, only to find that I don't have any aircraft to test them with:)
Just one issue -- I am missing one windsock -- I have a large and small windsock, which I use in Real NZ Dunedin, but only the larger one appears. No mention of the little one in the log, and no errors...
Only other SODE simobject is a flag, and that works as expected.
I'll do some further testing later, but in the meantime just a heads-up that there might be a problem...
 
Hello Jeffrey,

My config: W10 Pro 64b + P3D4.
I just installed SODE V1.5 after uninstalling the V1.4 ...
The operation is correct, for example: the doors of the hangars, the jetways work but not the objects driven by the force of the wind !
For exaple : <ConditionalVisibility Variable="WindSpeed" Value="4-9"/>
Windsocks, windmills and flags disappeared ... in my 3 simulators: FS-X, P3D3 and P3D4.
An example of '* .xml is attached.

Is there a solution?
 

Attachments

Downloaded your object libraries to test, and everything works as expected: They all show up and react to the wind speed and direction. Tested both in P3D v3 and v4.
What is the SODE.log saying on your end?
 
Hello Jeffrey

I placed the file 'SODE_LFSQ.xml' alone in the folder '\\xml', everything works perfectly ...
I added the file 'SODE_LFGC.xml' in the folder '\\xml', all the objects related to the wind disappeared !!!

The log file is in the attached archive ...

Best regards
 

Attachments

Last edited:
Fixed! It was an issue when multiple data probes are loaded into the simbubble.
The indexing was wrong. I have fixed another indexing issue in the xml parser already for V1.5.0, but the changes did not apply to the data probes unfortunately.

V1.5.1 is up!

Thanks for the report.

@toprob : Do you happen to use multiple data probes for your scenery?
 
Just one more issue, Jeff -- in P3dv4 my windsock elevations are off, at one airfield I have three of the same windsock, all at different elevations for some reason. P3Dv3 is still fine with SODE 1.51.
 
Hi Jeffrey

Can we install V1.5.1 over the previously released V1.5.0 or do we have to uninstall V1.5.0 first ?

Thanks

Philippe
 
in P3dv4 my windsock elevations are off, at one airfield I have three of the same windsock, all at different elevations for some reason. P3Dv3 is still fine with SODE 1.51.

Any chance you can create a small test package for that issue and PM that to me? Thanks.

Can we install V1.5.1 over the previously released V1.5.0 or do we have to uninstall V1.5.0 first ?
Since V1.4.2, you can install any newer SODE version over an older one. No uninstall required. But to be very sure, you can always uninstall the old version manually.
 
Any chance you can create a small test package for that issue and PM that to me? Thanks.

I've been experimenting a bit, if I start a flight at the problem airport, elevations are ok, however if I start elsewhere, and then change the location to the airport, the elevations revert to incorrect, 3 windsocks showing the sock at different elevations, but always the same faulty elevation for each windsock. (Only the socks are simobjects, the poles are normal objects and there's no problem with their elevation.)
I'm give this some more thought for a bit, I'm not sure that sending you the files would help, as I suspect it depends on how P3Dv4 loads either the custom mesh I use, or the custom flatten.
 
ok, so what if you placed the socks at fixed altitudes, given that you are using the AGL function currently...
 
Back
Top