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

Seasonal hedge but not sim objects

Messages
4
Country
unitedkingdom
I have a 2 part question I'm hoping someone will be able to help with.

I am trying to create a hedge that uses 4 separate models, one for each season of the year.

Ideally I would like to have this hedge as a scenery object rather than a SimObject, this is because the vector tool allows me to place consistent hedges but only works with scenery objects. Is this at all possible or will it have to be a Simobject?

Secondly what would the correct string be to make an object seasonal. I know that for time based objects we can use something along the lines of the following:

(E:LOCAL TIME, Seconds) 28800 > (E:LOCAL TIME, Seconds) 64800 < and (L:XMLVAR_YokeHidden1) 1 == or if{ 80 } els{ 0 }

Many thanks!
 
It would need to be a SimObject if you want it to change dynamically based on season. One thing to consider here is there can only be so many SimObjects loaded in the 30km draw radius. I think that was around 1000 or so last I heard. Though it has been a while... Have never came close to using that many, so I'm also not sure if there would be any performance implications.

As far as code goes, it would depend on how you want to go about changing the objects per season. Going with a range of months is the most straight-forward option. If you have snowy hedges, you may want to go by month, but then tie in temperature or precipitation. Doing winter/snow objects is by far the most difficult, because there is no way to tie it into the snow-depth slider, so you're just playing with a few different conditions to see that it works under the majority of circumstances. Though, it will never be perfect for the time being. Hopefully something that changes in 24.

For a simple month range you could use this:
Code:
<Behaviors>
    <Include ModelBehaviorFile="Asobo\Common.xml"/>
    <Component ID="Clouded_Sulphur" Node="PathAnm_Clouded_Sulphur">
        <UseTemplate Name="ASOBO_GT_Visibility">
            <!-- Visible from May through September -->
            <VISIBILITY_CODE>
                (E:LOCAL MONTH OF YEAR, number) 5 &gt;= (E:LOCAL MONTH OF YEAR, number) 9 &lt;= and
            </VISIBILITY_CODE>
        </UseTemplate>
    </Component>
</Behaviors>

Or if it also needs to be snowing within the range (Obviously the months are wrong here, but it's just a quick example):
Code:
<Behaviors>
    <Include ModelBehaviorFile="Asobo\Common.xml"/>
    <Component ID="Clouded_Sulphur" Node="PathAnm_Clouded_Sulphur">
        <UseTemplate Name="ASOBO_GT_Visibility">
            <!-- Visible from May through September, and when snowing -->
            <VISIBILITY_CODE>
                (E:LOCAL MONTH OF YEAR, number) 5 &gt;= (E:LOCAL MONTH OF YEAR, number) 9 &lt;= and (A:AMBIENT PRECIP STATE, mask) 8 == and
            </VISIBILITY_CODE>
        </UseTemplate>
    </Component>
</Behaviors>

There is also this code I came up with for my snow berms that combines a few different conditions in an attempt to get them to show under most winter weather presets. Though, it's still not perfect. I have seen snow on the ground in live weather, but it wasn't cold enough to trigger it. And I hesitate to tweak the temps any because then it could show when it's cold enough but no with snow on the ground. Tradeoffs. Always tradeoffs...

Code:
<Behaviors>
    <Include ModelBehaviorFile="Asobo\Common.xml"/>
    <Component ID="Snow_Berm" Node="berm">
        <UseTemplate Name="ASOBO_GT_Visibility">
            <!-- Snow Berms will only show at -12C and below or if it is Snowing and -1C or below. -->
            <VISIBILITY_CODE>
                (A:AMBIENT TEMPERATURE, celsius) 1 neg &lt;= (A:AMBIENT PRECIP STATE, mask) 8 == and (A:AMBIENT TEMPERATURE, celsius) 12 neg &lt;= or
            </VISIBILITY_CODE>
        </UseTemplate>
    </Component>
</Behaviors>

Hopefully this points you in the right direction.
 
Last edited:
Thanks for the very quick response. Looks like I may just need to scrap the idea of seasonal hedges and make one that's generic enough to fit in for any time of the year. It's certainly very helpful for some trees I have planned which can be loaded as a Sim object as there aren't too many of the min the scenery.
 
Back
Top