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

Problem with LogicExpression and multiple models

I

Ian P

Messages
105
Country
unitedkingdom
Hello folks,

I've hit a bit of a problem trying to create multiple windsocks to go with Runway Control Caravans on an airfield.

The idea is that, as per the real world, the airfield has one or more "primary" windsocks which are fixed in location, plus secondary windsocks attached to a runway control vehicle or caravan which is parked at the downwind end of the active runway. The problem is that, while I can get a windsock to appear with the two conditions necessary (wind direction to define active runway and wind strength to determine the type of sock model called), if I then add additional lines for different windspeeds, the object will no longer appear.

It doesn't break the XML file, because objects called by later lines still work, the smaller windsocks just don't appear at all. I've tried different models and locations and it always works for the first model entry, but not if I add more than one.

The following is the code for what I'm trying to achieve for a single runway... Hunsdon has four of these (02/20 and 07/25) but most airfields will have six (e.g. Halfpenny Green has 04/22, 10/28 and 16/34...) to deal with.

XML: 
<!-- Runway 02 -->
    <!-- Runway Caravan 02 -->
    <SimObject Name="RunwayCaravan02">
        <Placement Lat="51.79928167" Lon="0.062996002" Alt="0#AGL" Hdg="022"/>
        <Model SimTitle="RunwayCaravanBlack">
            <ConditionalVisibility Variable="WindDirection" Value="318-047"/>
        </Model>
    </SimObject>
    <!-- Windsock 02 -->
    <SimObject Name="Windsock6ft02">
        <Placement Lat="51.79928167" Lon="0.062996002" Alt="0#AGL" Hdg="000"/>
        <Model SimTitle="Windsock_6ft_00k">
            <VariableDrivenRotation Variable="WindDirection" Axis="HEADING" Animated="No"/>
            <ConditionalVisibility LogicExpression="(A$B)">
                <Condition ID="A" Variable="Windspeed" Value="0-2"/>
                <Condition ID="B" Variable="WindDirection" Value="318-047"/>
            </ConditionalVisibility>
        </Model>
        <Model SimTitle="Windsock_6ft_03k">
            <VariableDrivenRotation Variable="WindDirection" Axis="HEADING" Animated="No"/>
            <ConditionalVisibility LogicExpression="(A$B)">
                <Condition ID="A" Variable="Windspeed" Value="3-5"/>
                <Condition ID="B" Variable="WindDirection" Value="318-047"/>
            </ConditionalVisibility>
        </Model>
        <Model SimTitle="Windsock_6ft_06k">
            <VariableDrivenRotation Variable="WindDirection" Axis="HEADING" Animated="No"/>
            <ConditionalVisibility LogicExpression="(A$B)">
                <Condition ID="A" Variable="Windspeed" Value="6-8"/>
                <Condition ID="B" Variable="WindDirection" Value="318-047"/>
            </ConditionalVisibility>
        </Model>
        <Model SimTitle="Windsock_6ft_09k">
            <VariableDrivenRotation Variable="WindDirection" Axis="HEADING" Animated="No"/>
            <ConditionalVisibility LogicExpression="(A$B)">
                <Condition ID="A" Variable="Windspeed" Value="9-11"/>
                <Condition ID="B" Variable="WindDirection" Value="318-047"/>
            </ConditionalVisibility>
        </Model>
        <Model SimTitle="Windsock_6ft_12k">
            <VariableDrivenRotation Variable="WindDirection" Axis="HEADING" Animated="No"/>
            <ConditionalVisibility LogicExpression="(A$B)">
                <Condition ID="A" Variable="Windspeed" Value="12-14"/>
                <Condition ID="B" Variable="WindDirection" Value="318-047"/>
            </ConditionalVisibility>
        </Model>
        <Model SimTitle="Windsock_6ft_15k">
            <VariableDrivenRotation Variable="WindDirection" Axis="HEADING" Animated="No"/>
            <ConditionalVisibility LogicExpression="(A$B)">
                <Condition ID="A" Variable="Windspeed" Value="15-35"/>
                <Condition ID="B" Variable="WindDirection" Value="318-047"/>
            </ConditionalVisibility>
        </Model>
    </SimObject>

Any suggestions, please, or should I just call a single model for these locations (i.e. always use the 15kt+ windspeed sock model).

Thanks in advance.

Ian P.

Edit: Attached full XML file for people to be rude about how inefficient it all is! ;)
 

Attachments

Last edited:
I don't have a dual condition for my windsocks but I wonder if this is linked to the conditional vis bug I found - if it is, it should be fixed in the next version.
 
Indeed, I wondered the same thing, reading your thread before posting this.

I was actually going to put this on your thread, then decided that in case it wasn't directly related, I should probably start my own. ;)

Cheers,

Ian P.
 
You must log in or register to reply here.
Back
Top