FSX IS this possible with a 2d pop-up XML gauge?

Maddz · 21 May 2022

tgibson said:
You do not check that they are equal, just that the plane is closer than a certain distance (i.e. airport center - aircraft location is less than a certain value).

I'm giving you a simple approach that should (?) work, although you should be able to find a formula online to calculate the distance between two lat long values if you wish.

1. Compare lat and long from the aircraft's location to the lat long for the center of EAFS (for example). Subtract lat from lat, long from long.
2. Add the two together.
3. Determine if this value is less than a certain value (determined by experiment). If so, you know what airport you are at and can check that the Fuel Gauge Switch is set appropriately.
3. If EAFS is not the correct airport, repeat this for each airport your code covers.
4. If none are less than the test distance, then you are not at one of the included airports.

Testing for the NAV frequency should work fine, I assume.

Thanks for that Tom, helps to picture mentally ”how to”
Im still pondering what to do, as Im reading the gps guide, there are code sample’s within it that should do what I’m after with some modification. But as you say, that approach is not so simple.

I think I’ll try the first approach with FS variables, see how that goes.

Maddz · 22 May 2022

All Stop, No progress, 1 step backwards

Well, i thought i was getting somewhere but realized the gauge wasn't working correctly when dumping. I'm not sure what's happend from last weekend when it seemed to work OK. regardless what i try it will only dump correctly from EAFS, otherwise it adds to the other 2 tanks, even though the code is subtracting (?) . For 2 days I've been trying to find the issue and still haven't. Just when you think your getting somewhere too.

tgibson · 23 May 2022

Write an Element in your gauge to print out the value of some of the variables, and make sure they are doing what you expect. Something like this:

XML:

<!-- test printing-->
    <Element>
        <Position X="5" Y="5"/>
        <Text X="400" Y="24" Bright="Yes" Length="400" Font="Arial" Color="#FFFFFF" Adjust="Left" VerticalAdjust="Center" Multiline="No" Fixed="No">
            <String> %( (A:PLANE HEADING DEGREES GYRO,degrees) )%!3.2f! %( 180 (A:NAV1 RADIAL, degrees) + )%!3.2f! %( (A:NAV1 OBS, degrees) )%!3.2f! %( (A:NAV1 RADIAL ERROR, degrees) )%!3.2f!  %( (A:HSI CDI needle, number) )%!3.2f! </String>
        </Text>
    </Element> <!-- test printing-->

I place  just after /Element to remark it out when not needed.

Or you could use a variable display gauge already available, if you like. An example is xml_vars from:

Doug Dawson's Web Site

www.douglassdawson.ca

Maddz · 23 May 2022

Hi Tom
That’s a great tip for the read out, I use Linda currently, but can be iffy. I’ll be looking into it though.
I think it’s more a case of the way I’m doing it though as it would “seem” to ignore anything past a certain point in the code. (Works perfect for eafs)
What I mean is, I’m now asking for more to be true before anything happens and my “ifs” don’t look right.

I’m currently asking for FLD state AND tank sub - to be true
So && is used as we are asking for 2 (1 and 2)parameters, is that correct?
But I’m now asking for 3 parameters (3rd being the switch for the fuel gauge)- or plan to when I can get to the pc

(State) 0 == (tanksub) 1 == (fuelgaugeswtch) 0 == && ???
If{ ~code to dump to airport 1~
if{ (fuelgaugeswitch) 1 == ~code to dump to airport 2~
then
els{ if els, then just the dump code for airport 3 - or - also ask for condition of fuelgaugeswitch 2 followed by dump code.
Or
Just add another
if{ (fuelgaugeswitch) 2 ~dump code for airport 2 }
And no els{ }

Or what about

check 2 parameters and fuel gauge switch (then query the last - fuel gauge switch)
If{ 0 } ~ code to dump to airport 1
If{ 1 } ~ code to dump to airport 2
If{ 2 } ~ code to dump to airport 3

apologies for the format, typing on a phone

tgibson said:
Write an Element in your gauge to print out the value of some of the variables, and make sure they are doing what you expect. Something like this:

XML:

 <Element> <Position X="5" Y="5"/> <Text X="400" Y="24" Bright="Yes" Length="400" Font="Arial" Color="#FFFFFF" Adjust="Left" VerticalAdjust="Center" Multiline="No" Fixed="No"> <String> %( (A:PLANE HEADING DEGREES GYRO,degrees) )%!3.2f! %( 180 (A:NAV1 RADIAL, degrees) + )%!3.2f! %( (A:NAV1 OBS, degrees) )%!3.2f! %( (A:NAV1 RADIAL ERROR, degrees) )%!3.2f! %( (A:HSI CDI needle, number) )%!3.2f! </String> </Text> </Element> 

I place  just after /Element to remark it out when not needed.

Or you could use a variable display gauge already available, if you like. An example is xml_vars from:

Doug Dawson's Web Site

Doug Dawson's Web Site

www.douglassdawson.ca

tgibson · 24 May 2022

I tend to keep things simple and use IF and ELS statements, but others have other preferences. Thus your first option.

When you are testing 3 (or more) conditions, you need a comparison operator (AND or OR) for each comparison. So:

(State) 0 == (tanksub) 1 == (fuelgaugeswtch) 0 == && &&

or

(State) 0 == (tanksub) 1 == && (fuelgaugeswtch) 0 == &&

whichever is easier for you to understand. I tend to use the latter because it's easier for me to read left to right.

Maddz · 27 May 2022

tgibson said:
I tend to keep things simple and use IF and ELS statements, but others have other preferences. Thus your first option.

When you are testing 3 (or more) conditions, you need a comparison operator (AND or OR) for each comparison. So:

(State) 0 == (tanksub) 1 == (fuelgaugeswtch) 0 == && &&

or

(State) 0 == (tanksub) 1 == && (fuelgaugeswtch) 0 == &&

whichever is easier for you to understand. I tend to use the latter because it's easier for me to read left to right.

Thanks Tom
ill be giving it another go tomorrow

Maddz · 28 May 2022

made some progress today.
Got the loading working correctly. I had to make a separate element for each airport instead of just the one containing all three. It was the only way it would work.
Then i was able to make the gauge require tuning a frequency for the selected airport, to show it's current quantity, otherwise if wrong frequency input, gauge reads '0'
click spots added
frequency display + frequency adjust buttons
power switch on off

XML:

XML:

<Gauge Name="Remote_Fuel_Unit" Version="1.0">
<Image Name="background.bmp"/>

<!-- ============================== Radio On/Off Switch ===================== -->
  <Element>
    <Position X="170" Y="188" />
    <Select>
       <Value>(A:Avionics master switch,bool)</Value>
       <Case Value="1">
          <Image Name="radio_switch_on.bmp" />
       </Case>
    </Select>
  </Element>

<!-- ============================== Frequency Readout ======================= -->
  <Element>
     <Position X="49" Y="191" />
     <Failures>
       <GAUGE_COMMUNICATIONS Action="NoDraw" />
     </Failures>
     <Visible>(A:Avionics master switch,bool)</Visible>
     <Text X="85" Y="30" Length="6" Fixed="Yes" Font="Quartz" Adjust="Center" VerticalAdjust="Center" Color="#00FF00" Bright="Yes">
        <String>%((A:Nav active frequency:1,Megahertz))%!6.3f!</String>
     </Text>
  </Element>

<!-- =============================== Test Read-out ============================ -->
<Element>
<Position X="5" Y="50"/>
<Text X="400" Y="24" Bright="Yes" Length="400" Font="Arial" Color="#FFFFFF" Adjust="Left" VerticalAdjust="Center" Multiline="Yes" Fixed="No">
<String> %( (A:FUEL TOTAL QUANTITY,gallon) )%!3.2f! %( (L:FLD_State,enum) )%!3.2f! %( (L:TankSub,number) )%!3.2f! %( (L:Loadsub, enum) )%!3.2f! %( (L:Fuel Gauge Switch, enum) )%!3.2f! %( (L:EAFS,enum) ) %!3.2f! %( (L:UKBA,enum) )%!3.2f! %( (L:LSGS,enum) )%!3.2f!  </String>
</Text>
</Element>

<!-- =================== read dump/load gauge switch position AND selected storage tank switch position, and after ======= -->
<!-- ==LOADING fuel, calculate fuel amount taken from the selected storage tank and subtract, then set minimum to not go below zero or be negative====================== -->

<Element>
<Select>
<Value> (L:FLD_State,enum) 0 == (L:TankSub, number) 1 == &amp;&amp; (L:Fuel Gauge Switch, enum) 0 == &amp;&amp; if{ (A:FUEL TOTAL QUANTITY,gallon) (L:CurrentAmount,enum) - (>L:Loadsub, enum) (L:EAFS, enum) (L:Loadsub, enum) - (>L:EAFS, enum) 0 (>L:TankSub, number) (L:EAFS, enum) 0 &lt; if{ 0 (>L:EAFS, enum) } } </Value>
</Select>
</Element>

<Element>
<Select>
<Value> (L:FLD_State,enum) 0 == (L:TankSub, number) 1 == &amp;&amp; (L:Fuel Gauge Switch, enum) 1 == &amp;&amp; if{ (A:FUEL TOTAL QUANTITY,gallon) (L:CurrentAmount,enum) - (>L:Loadsub, enum) (L:UKBA, enum) (L:Loadsub, enum) - (>L:UKBA, enum) 0 (>L:TankSub, number) (L:UKBA, enum) 0 &lt; if{ 0 (>L:UKBA, enum) } } </Value>
</Select>
</Element>

<Element>
<Select>
<Value> (L:FLD_State,enum) 0 == (L:TankSub, number) 1 == &amp;&amp; (L:Fuel Gauge Switch, enum) 2 == &amp;&amp; if{ (A:FUEL TOTAL QUANTITY,gallon) (L:CurrentAmount,enum) - (>L:Loadsub, enum) (L:LSGS, enum) (L:Loadsub, enum) - (>L:LSGS, enum) 0 (>L:TankSub, number) (L:LSGS, enum) 0 &lt; if{ 0 (>L:LSGS, enum) } } </Value>
</Select>
</Element>

<Element>
<Position X="98" Y="494" />
<Select>
<Value>(L:Fuel Gauge Switch, enum)</Value>
<Case Value="0">
<Image Name="Airport_selector_switch_EAFS_B.bmp">
<Axis X="37" Y="25" />
</Image>
</Case>
<Case Value="1">
<Image Name="Airport_selector_switch_UKBA_B.bmp">
<Axis X="23" Y="35" />
</Image>
</Case>
<Case Value="2">
<Image Name="Airport_selector_switch_LSGS_B.bmp">
<Axis X="37" Y="25" />
</Image>
</Case>
</Select>
</Element>
<!-- ======================= Set max tank capacity ================= -->
<Element>
<Select>
<Value>(L:EAFS, enum) 10000 &gt; if{ 10000 (>L:EAFS, enum) } </Value>
</Select>
</Element>

<Element>
<Select>
<Value>(L:LSGS, enum) 10000 &gt; if{ 10000 (>L:LSGS, enum) } </Value>
</Select>
</Element>

<Element>
<Select>
<Value>(L:UKBA, enum) 10000 &gt; if{ 10000 (>L:UKBA, enum) } </Value>
</Select>
</Element>

<!-- ========================= Fuel Gauge **correct frequecy must be tuned for each airport for gauge to read tank quantity**======================== -->
    <Element>
        <Position X="101" Y="334" />
        <Image Name="needle.bmp" PointsTo="North">
            <Axis X="2" Y="55" />
        </Image>
        <Rotate>
            <Value>(A:Avionics master switch,bool) 1 == (L:Fuel Gauge Switch, enum) 0 == (A:Nav active frequency:1,Megahertz) 108.000 == &amp;&amp; &amp;&amp;
      if{ (L:EAFS, enum) } (A:Avionics master switch,bool) 1 == (L:Fuel Gauge Switch, enum) 1 == (A:Nav active frequency:1,Megahertz) 113.000 == &amp;&amp; &amp;&amp;
      if{ (L:UKBA, enum) } (A:Avionics master switch,bool) 1 == (L:Fuel Gauge Switch, enum) 2 == (A:Nav active frequency:1,Megahertz) 117.000 == &amp;&amp; &amp;&amp;
          if{ (L:LSGS, enum) }
      </Value>
            <Failures>
                <SYSTEM_ELECTRICAL_PANELS Action="0" />
                <GAUGE_FUEL_INDICATORS Action="Freeze" />
            </Failures>
            <Nonlinearity>
            <Item Value="0" X="77" Y="372"/>
            <Item Value="1000" X="61" Y="355"/>
            <Item Value="2000" X="54" Y="333"/>
            <Item Value="3000" X="60" Y="310"/>
            <Item Value="4000" X="78" Y="294"/>
            <Item Value="5000" X="100" Y="287"/>
        <Item Value="6000" X="123" Y="293"/>
            <Item Value="7000" X="140" Y="309"/>
            <Item Value="8000" X="146" Y="332"/>
            <Item Value="9000" X="141" Y="356"/>
            <Item Value="10000" X="125" Y="373"/>
            </Nonlinearity>
            <Delay DegreesPerSecond="20" />
        </Rotate>
    </Element>
    <Mouse>
    <Help ID="HELPID_RADIO_COMM1" />
    <Tooltip ID="TOOLTIPTEXT_COMM1_FREQ" />
    <Area Left="90" Top="150" Width="20" Height="20">
        <Cursor Type="DownArrow" Repeat="Yes" />
        <Click Repeat="Yes" MouseWheelFlip="Yes">
          (A:Avionics master switch,bool) 1 ==
          if{ 0 (&gt;K:NAV1_RADIO_WHOLE_DEC) }
        </Click>
      </Area>
      <Area Left="90" Top="133" Width="20" Height="20">
        <Cursor Type="UpArrow" Repeat="Yes" />
        <Click Repeat="Yes" MouseWheelFlip="Yes">
          (A:Avionics master switch,bool) 1 ==
          if{ 0 (&gt;K:NAV1_RADIO_WHOLE_INC) }
        </Click>
      </Area>
      <Area Left="116" Top="150" Width="20" Height="20">
        <Cursor Type="DownArrow" Repeat="Yes" />
        <Click Repeat="Yes" MouseWheelFlip="Yes">
          (A:Avionics master switch,bool) 1 ==
          if{ 0 (&gt;K:NAV1_RADIO_FRACT_DEC) }
        </Click>
      </Area>
      <Area Left="117" Top="130" Width="20" Height="20">
        <Cursor Type="UpArrow" Repeat="Yes" />
        <Click Repeat="Yes" MouseWheelFlip="Yes">
          (A:Avionics master switch,bool) 1 ==
          if{ 0 (&gt;K:NAV1_RADIO_FRACT_INC) }
        </Click>
    </Area>
<!-- Radio Master -->
    <Area Left="171" Top="188" Width="12" Height="20">
      <Cursor Type="Hand" />
      <Click Event="TOGGLE_AVIONICS_MASTER" />
    </Area>
<Area Left="44" Top="480" Width="40" Height="50">
            <Cursor Type="DownArrow" />
            <Click>(L:Fuel Gauge Switch, enum) -- d 0 &lt; if{ 2 } (&gt;L:Fuel Gauge Switch, enum)</Click>
        </Area>
        <Area Left="130" Top="480" Width="40" Height="50">
            <Cursor Type="UpArrow" />
            <Click>(L:Fuel Gauge Switch, enum) ++ d 2 &gt; if{ 0 } (&gt;L:Fuel Gauge Switch, enum)</Click>
        </Area>
    </Mouse>
</Gauge>

pic: (for testing only)

Maddz · 29 May 2022

Ok, so i wanted to change the frequency to something other than ending in '.000' but if i want 108.20, it wont work, as 108.00 will.
this works:

XML:

(A:Avionics master switch,bool) 1 == (L:Fuel Gauge Switch, enum) 0 == (A:Nav active frequency:1,Megahertz) 108.000 == &amp;&amp; &amp;&amp;

this doesn't

XML:

(A:Avionics master switch,bool) 1 == (L:Fuel Gauge Switch, enum) 0 == (A:Nav active frequency:1,Megahertz) 108.20 == &amp;&amp; &amp;&amp;

or .200 - .020 - .0200
what am i missing?

tgibson · 29 May 2022

I don't know, it should work. Be sure you are tuned to the correct frequency.

108.02 will never work, since it is not a valid frequency. 108.025 is though. But for compatibility with all FS radios I stick to 2 decimals.

Maddz · 3 Jun 2022

Hi Tom
i was sure I was tuned to the right frequency, as displayed on the radio. Also that frequency is a vor at the airfield witch was giving me signal on the cross bars and a dme reading.
maybe a rounding issue? …hard to find any info about this sort of thing

While messing about I took ‘==‘ out after the 108.20 and it then reacts to it but in another switch position so although something happens it’s wrong. This was an attempt at not allowing loading unless at a certain distance from the vor IE 1dme.

tgibson · 3 Jun 2022

Display the value of the (A:Nav active frequency:1,Megahertz) variable and see what it reports.

DragonflightDesign · 3 Jun 2022

@tgibson Tom: I've no idea if this is possible in XML, but in P3D for the radios I run a check against 'COM IS 8333HZ MODE' and adjust the following frequency read/write code to suit.

Maddz · 5 Jun 2022

tgibson said:
Display the value of the (A:Nav active frequency:1,Megahertz) variable and see what it reports.

It displays whats tuned...so 108.20 is 108.20, even adding more digits to the display to see if there was a bigger / smaller number doesn't change, it just displays 108.2000 (( <String>%( (A:Nav active frequency:1,Megahertz) )%!3.4f! ))

I've put way, way to many hours into this 1 simple thing...not feeling 'fun' anymore, may need another approach :/ starting to feel like a ''file - save - flight - reset'' marathon!

Time to go for a flight...

EduHir · 5 Jun 2022

Im using MHz.

(A:NAV ACTIVE FREQUENCY:1,MHz) (L:NavM_POST_ILS_Frq,MHz) ==

You could also test

108.200 (>L:NavM_POST_ILS_Frq,MHz)

And then do the comparison

Maddz · 8 Jun 2022

EduHir said:
Im using MHz.

(A:NAV ACTIVE FREQUENCY:1,MHz) (L:NavM_POST_ILS_Frq,MHz) ==

You could also test

108.200 (>L:NavM_POST_ILS_Frq,MHz)

And then do the comparison

Hi Eduhir
Thanks for the reply, but I don’t follow, I’m confused with this
108.200 (>L:NavM_POST_ILS_Frq,MHz)
What would I compare with?

Btw I think I tried mhz, but will double check… I even used “pounds” just to see if it would do some kind of conversion

but no.

EduHir · 8 Jun 2022

Played around
this worked .... P3Dv5 !!!!

XML:

110.900  (&gt;L:NavM_POST_ILS_Frq,MHz)
(A:NAV ACTIVE FREQUENCY:1,Hz) (L:NavM_POST_ILS_Frq,Hz) ==

or in my testfile

%(110.900  (&gt;L:NavM_POST_ILS_Frq,MHz) (A:NAV ACTIVE FREQUENCY:1,Hz) (L:NavM_POST_ILS_Frq,Hz) == )%!5.2f!\n

gives  ... 1

for (>L:NavM_POST_ILS_Frq,MHz) use your own variablename.
Its part of a xml file.

++++++++++++++++++
your code should be

XML:

108.20 (&gt;L:Used_Frq,MHz)

or
108200000 (&gt;L:Used_Frq,Hz)


(A:Avionics master switch,bool) 1 ==
(L:Fuel Gauge Switch, enum) 0 ==
&amp;&amp;
(A:Nav active frequency:1,Hz) (L:Used_Frq,Hz) ==
&amp;&amp;

Maddz · 11 Jun 2022

EduHir said:
Played around
this worked .... P3Dv5 !!!!

XML:

110.900 (>L:NavM_POST_ILS_Frq,MHz) (A:NAV ACTIVE FREQUENCY:1,Hz) (L:NavM_POST_ILS_Frq,Hz) == or in my testfile %(110.900 (>L:NavM_POST_ILS_Frq,MHz) (A:NAV ACTIVE FREQUENCY:1,Hz) (L:NavM_POST_ILS_Frq,Hz) == )%!5.2f!\n gives ... 1

for (>L:NavM_POST_ILS_Frq,MHz) use your own variablename.
Its part of a xml file.

++++++++++++++++++
your code should be

XML:

108.20 (>L:Used_Frq,MHz) or 108200000 (>L:Used_Frq,Hz) (A:Avionics master switch,bool) 1 == (L:Fuel Gauge Switch, enum) 0 == && (A:Nav active frequency:1,Hz) (L:Used_Frq,Hz) == &&

Thank you!
Working!
You wouldn't believe the amount of time I've wasted with this.
It was very simple, all i done was change Mhz to Khz....and it works. ( for clarity, i'm using FSX:A)

Your reply, and this topic bought it together for me:
https://www.fsdeveloper.com/forum/threads/xml-math-oddity.75567/

It now looks like this:

XML:

(A:Avionics master switch,bool) 1 ==
 (L:Fuel Gauge Switch, enum) 1 ==
(A:Nav active frequency:1,Khz) 108200 ==
&amp;&amp; &amp;&amp;

Maddz · 12 Jun 2022

Posting for a dairy of progress, and all interested

Maddz said:
have some code that recognizes / detects when a switch, with 3 positions, (1 down, 0 middle, 2 up) has gone from 2 to 0 and when it does, it puts (A:TOTAL FUEL QUANTITY) into (>L:EAFS) - COMPLETED AND 2 OTHER TANKS (LSGS - UKBA) ADDED

I wouldn’t know where to start with this one but maybe have to dial a frequency in order for the quantity to show on the gauge? is that even possible? YES - COMPLETE.

bearing / distance of airport from current position. Maybe a compass face with a needle pointing to bearing. Old type drum DME readout maybe - TO DO

Added a feature that allow the gauge to be used to fill or dump fuel at other airports with no storage tank. If the airport does not have a storage tank, when filling or dumping, it will just add / subtract from aircraft tanks.
If at an airport with a storage tank, it will add / subtract from that tank, provided 4 condition are true and works like so:
1) The correct frequency to show tank quantity at the desired airport is tuned. ( I chose the frequencies of VOR's that are on, or very close to the airfield.)
2) The fuel gauge switch is in the correct position.
3) A signal is be received.
4) Has a DME of less than 2 nMiles

Conditions 3 and 4 work together to determine if at an airport. The less than 2 nmiles condition could also return '0' if out of range and would allow dumping, so i added condition 3 to stop that.

XML:

(L:Nav1_DME, number) 2 &lt;= (A:NAV HAS NAV:1, bool) -1 == (L:FLD_State,enum) -2 == (L:Fuel Gauge Switch, enum) 0 == &amp;&amp; &amp;&amp; &amp;&amp; if{ (L:EAFS, enum) (A:FUEL TOTAL QUANTITY,gallon) + (>L:EAFS, enum) }

A current problem i've noticed: or maybe not a problem when not testing - more testing required lol -
If 'EAFS' is the selected airport, and i slew away 3 miles, it won't subtract from the tank witch is correct as the code above asks for 2 miles or less. BUT: if i fill the tanks with any amount, it will remember the amount taken, and when i slew back within range, it will then subtract (could be considered anti-cheat?

)

- and also, tuning another VOR at another airport would allow loading from the tank selected on the switch whilst not being at that airport as ''(L:Nav1_DME, number) 2 <= (A:NAV HAS NAV:1, bool) -1 =='' would be true. To solve that I added the condition for the radio frequency to be set also:

The code :

XML:

 (L:Nav1_DME, number) 2 &lt;= (A:NAV HAS NAV:1, bool) -1 == (L:FLD_State,enum) 0 == (L:TankSub, number) 1 == (L:Fuel Gauge Switch, enum) 1 == (A:Nav active frequency:1,Khz) 108200 == &amp;&amp; &amp;&amp; &amp;&amp; &amp;&amp; if{ (A:FUEL TOTAL QUANTITY,gallon) (L:CurrentAmount,enum) - (>L:Loadsub, enum) (L:UKBA, enum) (L:Loadsub, enum) - (>L:UKBA, enum) 0 (>L:TankSub, number) (L:UKBA, enum) 0 &lt; if{ 0 (>L:UKBA, enum) } }

Slowly coming together. Still unable to find a suitable image for the unit in the aircraft, looked at many but nothing jumping out so far.

tgibson · 12 Jun 2022

The simple way to avoid your problem is not to allow any filling of the tanks unless within range of the airport.

Maddz · 12 Jun 2022

tgibson said:
The simple way to avoid your problem is not to allow any filling of the tanks unless within range of the airport.

Hi Tom
Yes, that's what I've done. But when testing doing things you normally wouldn't, like slewing, If the panel is setup to fill from EAFS, but 3 miles away, it wont take fuel from the storage tank (correct - out of range, it does not fill from tanks)
but if i slew back into range, it automatically subtracts the amount i added when i was out of range. it gets remembered.
Under normal circumstances i don't think this would be a problem, but need to test more.