• 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 SODE "simulation bubble" limitation ?

Messages
228
Country
france
Hi,

a friend of mine reported a problem with SODE : when xml files are created for 2 airports (1 xml file per airport) located within the 24km radius, SODE triggered/animated objects are visible at one airport only.

Best regards
 
I placed another Hangar with a separate xml file on a nearby airport (within 24km) and it shows up correctly, also in the in-game menu. What do you mean by visible at one airport only? The object itself or the in-game menu entry?
There is one thing to consider though, if you go from one airport to another, the SimBubble updates every 8km travelled from the initial point. The distance condition itself is checked every ten seconds (very low frequency, because it's not that important and 8km is enough around an airport). So in my case, I started at one airport, with the correct Hangar in the in-game menu. Then slewed fast to the distant airport, but the old hangar is still in the in-game menu, because the bubble is not updated yet (remember those 10 secs?). After waiting, the bubble as well as the in-game menu updates and the new correct hangar is now presented in the menu :-)

You could also provide the xmls (and if you want also the SimObjects) to me and I can check it for your friend.
 
Thanks for your reply Jeffrey

I placed another Hangar with a separate xml file on a nearby airport (within 24km) and it shows up correctly, also in the in-game menu. What do you mean by visible at one airport only?
The object itself or the in-game menu entry?

The object itself, we can't get the in-game menu because the key combination doesn't work with azerty keyboards.


You could also provide the xmls (and if you want also the SimObjects) to me and I can check it for your friend.

I will try to replicate the problem before asking my friend.


Best regards
 
Hello Jeffrey,

I am the Jacques's friend ...
My Sim is P3D2.4

Here is my problem :
> Two plateforms : 'LFST' and 'LFGC' are distant of 11Km.
> I have write one XML file for each plateform, joined to the post,
>>> LFST has 1 Windsock, 1 Papi Rwy05 and 1 Papi Rwy23,
>>> LFGC has 1 Windsock, 1 Landing Direction T and, to test, 1 Animated Hangar 1.

> When only one XML file is active, all is correct for each plateform.

> When 2 XML files are active :
>>> Fisrt case :
eN0wk.jpg

>>> LFST is all OK
>>> LFGC : Hangar 1 = OK, but no Windsock and no 'T' is visible.

>>> Second Case, I have inverted the order of the XML files in the directory :
AVH9u.jpg

> LFGC is all OK
> LFST : Papi05 and Papi23 are OK, but no Windsock is visible.

I deduct :
> One XML file has priority on the other, most probably, the last read by SODE,
> The locking affect only objets with Wind Sensibility !

I have made one library of 36 European animated Fags Wind Direction and Wind Range dependant and I cannot make use of these ...

8pBNa.jpg


A lot of airports are nearby one to the other in Alsace ... and neighbourhood.
LFST – LFGC = 11.4Km
LFST – EDSK = 16.1Km
LFST – EDTL = 23.8Km
LFGA - LFSC = 21.2Km
LFSC – EDTG = 16.7Km
LFSC – LFGB = 20.3Km
LFGB – LFSB = 17.4Km

The best bubble radius seem to be 10Km !
Or, may be, add the bubble radius as a variable in the XML file ...

Thank you for your attention ...

Best regards

Patrick
 

Attachments

Last edited:
Merci Patrick

You found a bug! I was able to reproduce the exact same behaviour as you mentioned. It is because across 2 xml files, two SimObjects have the same name "WindSock". Moreover, there seems to be a bug when multiple EnvironmentalDataProbes are present in the SimBubble.

I will correct those issues soon. I'll keep you posted.

[EDIT]

Bug fixed! Multiple EnvironmentalDataProbes are now correctly handled in the SimBubble. For now it supports 128 of those Probes within the 24km radius bubble, which should be sufficient I think ;)
Also, SODE can now distinguish identical SimObject names across different files. So there is no need to invent a new name for every xml.

These fixes will be included in the next version.
 
Last edited:
Back
Top