Board index FlightGear Development AI Traffic

AI Aircraft beacon  Topic is solved

Intelligent, computer controlled vehicles that drive/fly over the planet!

Re: AI Aircraft beacon

Postby wlbragg » Fri Sep 01, 2017 5:29 pm

Ian, I think you want,
Code: Select all
<not>
  <property>transponder-id</property>
  <value type="string">null</value>
</not>
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q
User avatar
wlbragg
 
Posts: 7588
Joined: Sun Aug 26, 2012 12:31 am
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/RTX 2070

Re: AI Aircraft beacon

Postby wkitty42 » Fri Sep 01, 2017 7:19 pm

BecOzIcan wrote in Fri Sep 01, 2017 11:08 am:Using the AI/models/aircraft/Valid=true parameter as suggested does not work, all shown aircraft carry a value of [true] on startup and I can't find a single one one with a value of [False] on my tarmac, maybe it works only for arriving aircrafts once parked

yes, the valid property is set to false at the end of the flight when that aircraft[] record is not being used any longer... the AI system seems to recycle the records... in some period of time, that record will be assigned another callsign and other values and the valid property will then be set to true so the AI system will manipulate the craft... the craft may or may not be removed when the valid property is set to false... i've seen them sit on the runway (no ground net) for a while and then suddenly disappear but the valid property has been false for a while... i'm guessing garbage collection finally caught up...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 9148
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: AI Aircraft beacon

Postby wkitty42 » Fri Sep 01, 2017 7:22 pm

BecOzIcan wrote in Fri Sep 01, 2017 11:08 am:BUT GOOD NEWS

I just discovered and confirmed that the AI/models/aircraft/transponder-id value for my two test models is empty on start up BUT switches to a 4 digits value (different for each aircraft) just before they start push back (once assigned a flight I guess) which is exactly what you suggest

yes, that would probably work and also give the randomness i was speaking of... i think i was thinking to use the random number as a sort of starting timer... after X seconds passed, then start the blinking but i think you already explained that that should be automatically handled when the craft start moving so the randomness idea may not be needed at all...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 9148
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: AI Aircraft beacon

Postby wkitty42 » Fri Sep 01, 2017 7:27 pm

BecOzIcan wrote in Fri Sep 01, 2017 1:57 pm:I my be on the wrong path here, when I link the light switch to speed (as reminded above by Gooney) I am not using the path of a specific aircraft .... still that velocity is stored under each aircraft properties subtree, will look into it further see I can use the transponder ID directly

yeah, i thought you were using their velocity property in the aircraft[] record...

HINT: that velocity property is the one that i manually tickle when an AI craft is stuck and blocking all the others... i'll change it to 15 until the craft is on the runway and lined up and then i'll hit it with 150 a few times because they always try to stop... once they get up in the air and have done the usual "fly runway heading until" part of the flight path, they will then break to turn out of the runway heading path... at that time, they will take over their flying without me having to kick them in a backside any more :mrgreen:
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 9148
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: AI Aircraft beacon

Postby gooneybird » Fri Sep 01, 2017 7:44 pm

I've been testing an updated file that Ian sent me for the last hour or so and things are working nicely apart from the lights not turning off when the aircraft returns and parks up but that could be due to the traffic file I'm using. we will know more when Ian awakes from his slumbers.

The relevant changes are:

Code: Select all
  <!-- Show Beacons when Aircraft is moving -->
  <animation>
    <type>select</type>
    <object-name>BeaconGrouped</object-name>
    <nopreview />
    <condition>
      <and>
        <property>/sim/model/A359/lighting/beacon/state</property>
        <greater-than>
          <property>transponder-id</property>
          <value type="string"> </value>
        </greater-than>
      </and>
    </condition>
  </animation>
  <!-- Show Strobes when Aircraft on runway or airborne -->
  <animation>
    <type>select</type>
    <object-name>StrobeGrouped</object-name>
    <nopreview />
    <condition>
      <and>
        <property>/sim/model/A359/lighting/strobes/state</property>
        <greater-than>
          <property>velocities/true-airspeed-kt</property>
          <value>40</value>
        </greater-than>
      </and>
    </condition>
  </animation>
  <!-- Show Static Lights when aircraft is moving -->
  <animation>
    <type>select</type>
    <object-name>StaticGrouped</object-name>
    <nopreview />
    <condition>
      <greater-than>
        <property>transponder-id</property>
        <value> </value>
      </greater-than>
    </condition>
  </animation>
My Github repository (mostly AI stuff) https://github.com/gooneybird47
User avatar
gooneybird
 
Posts: 3046
Joined: Sat May 31, 2008 2:57 pm

Re: AI Aircraft beacon

Postby BecOzIcan » Sat Sep 02, 2017 6:37 am

Thank you so much guys, I thing we're doing pretty good at taking advantage of the time differences between our 3 continents. Your help is much appreciated and I think we are very close to a satisfactory state with AI Lightning

wlbragg wrote in Fri Sep 01, 2017 5:29 pm:Ian, I think you want,
Code: Select all
<not>
  <property>transponder-id</property>
  <value type="string">null</value>
</not>


I was hoping so as it looked clean and logical but unfortunately did not work

Still, as I didn't want to keep the [space] character I had in the test file I sent to Gooneybird last night (because that space disappears from the code when you beautify it and you loose your condition) . I tested further and found an alternative which I believe takes advantage of the statement made on the wiki page for conditions : " Comparison of string-typed properties involves lexicographic ordering, as specified by the C++ operators < and >". After updating my code the below works fine to both test the emptiness of the transponder-id field and resists code beautification

Code: Select all
<animation>
    <type>select</type>
    <object-name>StaticGrouped</object-name>
    <nopreview />
    <condition>
      <greater-than>
          <property>transponder-id</property>
          <value type="string">0</value>
        </greater-than>
    </condition>
  </animation>



wkitty42 wrote in Fri Sep 01, 2017 7:19 pm:yes, the valid property is set to false at the end of the flight when that aircraft[] record is not being used any longer... the AI system seems to recycle the records....


It sounds like the way to go. I am going to add this condition to my code. @Gooneybird I will most likely need your help again. I am not quite sure about the syntax on strings testing and I barely have any "arriving" aircraft with my current test data (so we can see what happens at the end of flight, once the final parking position reached

wkitty42 wrote in Fri Sep 01, 2017 7:27 pm: that velocity property is the one that i manually tickle when an AI craft is stuck and blocking all the others... i'll change it to 15 until the craft is on the runway


Both Gooneybird and I have spent a lot of time trying to understand that "Blocked at entrance of runway" behaviour and have developed some strategies. Send me your groundnet and I ll see what I can do. Manually pushing an aircraft is frustrating. Finding the right aircraft in the debug properties AI list is even worse.

Next steps for me will be :
- Confirm Lights Off condition (possibly through [Valid] variable
- Making lights look good in Rembrandt. This is totally compatible with the ALS research wlbragg is doing as I understand regular lights (mine) do not show up if ALS is on, Rembrandt or not so it would be a nice addition/complement
- Code cleaning and possibly refactoring into sub models (2nd attempts]
- Adding Lightmap back into the model so I can light up the tail logo and passenger windows at night. This has been on hold for a while because I wanted to stay away from creating one nasal listener per AI model but the research of these past days and the PA-28 animation code gave me some ideas for a workaround. see viewtopic.php?f=47&t=30000&hilit=+lightmap

Will keep you updated on the above

Cheers
Ian
Current Projects: AI Traffic, Models & Liveries
User avatar
BecOzIcan
 
Posts: 1302
Joined: Tue Oct 04, 2011 11:43 pm
Location: Sydney, NSW, Australia
Version: 2020.4.0
OS: Win10

Re: AI Aircraft beacon

Postby wlbragg » Sat Sep 02, 2017 8:41 am

BecOzIcan wrote in Sat Sep 02, 2017 6:37 am:
wlbragg wrote in Fri Sep 01, 2017 5:29 pm:Ian, I think you want,
Code: Select all
<not>
  <property>transponder-id</property>
  <value type="string">null</value>
</not>

I was hoping so as it looked clean and logical but unfortunately did not work

Interesting, I must have mistaken the results I thought I got.

BecOzIcan wrote in Sat Sep 02, 2017 6:37 am:- Making lights look good in Rembrandt. This is totally compatible with the ALS research wlbragg is doing as I understand regular lights (mine) do not show up if ALS is on, Rembrandt or not so it would be a nice addition/complement

Your lights aren't showing up under ALS? If not, that might explain why i never could get lights with your testbed, I run ALS exclusively.

I'll attach your lighting method to my pa-28 touch-n-go scenario and see what I get. I thought you were basically using a version of the pa-28 example, which does work under ALS?

If I understood you correctly and your lights really aren't working under ALS, then I will attempt to set them up procedurally
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q
User avatar
wlbragg
 
Posts: 7588
Joined: Sun Aug 26, 2012 12:31 am
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/RTX 2070

Re: AI Aircraft beacon

Postby BecOzIcan » Sat Sep 02, 2017 9:57 am

Sorry fr any confusion. My current implementation is same as PA-28 but searching doc on ALS procedural lights as a possible replacement I am reading "The lights are currently not supported in the default or Rembrandt renderer and will simply be invisible in these frameworks." http://wiki.flightgear.org/ALS_technical_notes
Current Projects: AI Traffic, Models & Liveries
User avatar
BecOzIcan
 
Posts: 1302
Joined: Tue Oct 04, 2011 11:43 pm
Location: Sydney, NSW, Australia
Version: 2020.4.0
OS: Win10

Re: AI Aircraft beacon

Postby gooneybird » Sat Sep 02, 2017 10:01 am

The lights are working fine for me with ALS on.

If anyone's interested here's the test traffic file I'm using, it's based at EGSS but that can be easily changed to another airport in a text editor.

Code: Select all
<?xml version="1.0"?>
<trafficlist>
    <!-- FLIGHT 1 -->
    <aircraft>
        <model>Aircraft/A350/359-FGFS.xml</model>
        <livery>RBH</livery>
        <airline>RBH</airline>
        <home-port>EGSS</home-port>
        <required-aircraft>TestAA-T001</required-aircraft>
        <actype>319</actype>
        <offset>0</offset>
        <radius>17</radius>
        <flighttype>gate</flighttype>
        <performance-class>jet_transport</performance-class>
        <registration>SRB101</registration>
        <heavy>false</heavy>
    </aircraft>
    <flight>
        <callsign>TestAA-11</callsign>
        <required-aircraft>TestAA-T001</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>06:05:01</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>06:50:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <flight>
        <callsign>TestAA-12</callsign>
        <required-aircraft>TestAA-T001</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>07:05:02</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>07:50:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <!-- FLIGHT 2 -->
    <aircraft>
        <model>Aircraft/A350/359-FGFS.xml</model>
        <livery>RBH</livery>
        <airline>RBH</airline>
        <home-port>EGSS</home-port>
        <required-aircraft>TestAA-T002</required-aircraft>
        <actype>319</actype>
        <offset>0</offset>
        <radius>17</radius>
        <flighttype>gate</flighttype>
        <performance-class>jet_transport</performance-class>
        <registration>SRB201</registration>
        <heavy>false</heavy>
    </aircraft>
    <flight>
        <callsign>TestAA-21</callsign>
        <required-aircraft>TestAA-T002</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>06:10:03</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>07:00:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <flight>
        <callsign>TestAA-22</callsign>
        <required-aircraft>TestAA-T002</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>07:10:04</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>08:00:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <!-- FLIGHT 3 -->
    <aircraft>
        <model>Aircraft/A350/359-FGFS.xml</model>
        <livery>RBH</livery>
        <airline>RBH</airline>
        <home-port>EGSS</home-port>
        <required-aircraft>TestAA-T003</required-aircraft>
        <actype>319</actype>
        <offset>0</offset>
        <radius>17</radius>
        <flighttype>gate</flighttype>
        <performance-class>jet_transport</performance-class>
        <registration>SRB301</registration>
        <heavy>false</heavy>
    </aircraft>
    <flight>
        <callsign>TestAA-31</callsign>
        <required-aircraft>TestAA-T003</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>06:15:05</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>07:00:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <flight>
        <callsign>TestAA-32</callsign>
        <required-aircraft>TestAA-T003</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>07:15:06</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>08:00:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <!-- FLIGHT 4 -->
    <aircraft>
        <model>Aircraft/A350/359-FGFS.xml</model>
        <livery>RBH</livery>
        <airline>RBH</airline>
        <home-port>EGSS</home-port>
        <required-aircraft>TestAA-T004</required-aircraft>
        <actype>319</actype>
        <offset>0</offset>
        <radius>17</radius>
        <flighttype>gate</flighttype>
        <performance-class>jet_transport</performance-class>
        <registration>SRB401</registration>
        <heavy>false</heavy>
    </aircraft>
    <flight>
        <callsign>TestAA-41</callsign>
        <required-aircraft>TestAA-T004</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>06:20:07</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>07:05:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <flight>
        <callsign>TestAA-42</callsign>
        <required-aircraft>TestAA-T004</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>07:20:08</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>08:05:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <!-- FLIGHT 5 -->
    <aircraft>
        <model>Aircraft/A350/359-FGFS.xml</model>
        <livery>RBH</livery>
        <airline>RBH</airline>
        <home-port>EGSS</home-port>
        <required-aircraft>TestAA-T005</required-aircraft>
        <actype>319</actype>
        <offset>0</offset>
        <radius>17</radius>
        <flighttype>gate</flighttype>
        <performance-class>jet_transport</performance-class>
        <registration>SRB501</registration>
        <heavy>false</heavy>
    </aircraft>
    <flight>
        <callsign>TestAA-51</callsign>
        <required-aircraft>TestAA-T005</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>06:25:09</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>07:10:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <flight>
        <callsign>TestAA-52</callsign>
        <required-aircraft>TestAA-T005</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>07:25:11</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>08:10:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <!-- FLIGHT 6 -->
    <aircraft>
        <model>Aircraft/A350/359-FGFS.xml</model>
        <livery>RBH</livery>
        <airline>RBH</airline>
        <home-port>EGSS</home-port>
        <required-aircraft>TestAA-T006</required-aircraft>
        <actype>319</actype>
        <offset>0</offset>
        <radius>17</radius>
        <flighttype>gate</flighttype>
        <performance-class>jet_transport</performance-class>
        <registration>SRB601</registration>
        <heavy>false</heavy>
    </aircraft>
    <flight>
        <callsign>TestAA-61</callsign>
        <required-aircraft>TestAA-T006</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>06:30:12</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>07:15:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <flight>
        <callsign>TestAA-62</callsign>
        <required-aircraft>TestAA-T006</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>07:30:13</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>08:15:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <!-- FLIGHT 7 -->
    <aircraft>
        <model>Aircraft/A350/359-FGFS.xml</model>
        <livery>RBH</livery>
        <airline>RBH</airline>
        <home-port>EGSS</home-port>
        <required-aircraft>TestAA-T007</required-aircraft>
        <actype>319</actype>
        <offset>0</offset>
        <radius>17</radius>
        <flighttype>gate</flighttype>
        <performance-class>jet_transport</performance-class>
        <registration>SRB701</registration>
        <heavy>false</heavy>
    </aircraft>
    <flight>
        <callsign>TestAA-71</callsign>
        <required-aircraft>TestAA-T007</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>06:35:14</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>07:20:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <flight>
        <callsign>TestAA-72</callsign>
        <required-aircraft>TestAA-T007</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>07:35:15</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>08:20:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <!-- FLIGHT 8 -->
    <aircraft>
        <model>Aircraft/A350/359-FGFS.xml</model>
        <livery>RBH</livery>
        <airline>RBH</airline>
        <home-port>EGSS</home-port>
        <required-aircraft>TestAA-T008</required-aircraft>
        <actype>319</actype>
        <offset>0</offset>
        <radius>17</radius>
        <flighttype>gate</flighttype>
        <performance-class>jet_transport</performance-class>
        <registration>SRB801</registration>
        <heavy>false</heavy>
    </aircraft>
    <flight>
        <callsign>TestAA-81</callsign>
        <required-aircraft>TestAA-T008</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>06:40:16</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>07:25:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <flight>
        <callsign>TestAA-82</callsign>
        <required-aircraft>TestAA-T008</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>07:40:00</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>08:25:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <!-- FLIGHT 9 -->
    <aircraft>
        <model>Aircraft/A350/359-FGFS.xml</model>
        <livery>RBH</livery>
        <airline>RBH</airline>
        <home-port>EGSS</home-port>
        <required-aircraft>TestAA-T009</required-aircraft>
        <actype>319</actype>
        <offset>0</offset>
        <radius>17</radius>
        <flighttype>gate</flighttype>
        <performance-class>jet_transport</performance-class>
        <registration>SRB901</registration>
        <heavy>false</heavy>
    </aircraft>
    <flight>
        <callsign>TestAA-91</callsign>
        <required-aircraft>TestAA-T009</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>06:45:00</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>07:30:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <flight>
        <callsign>TestAA-92</callsign>
        <required-aircraft>TestAA-T009</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>07:45:00</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>08:30:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <!-- FLIGHT 10 -->
    <aircraft>
        <model>Aircraft/A350/359-FGFS.xml</model>
        <livery>RBH</livery>
        <airline>RBH</airline>
        <home-port>EGSS</home-port>
        <required-aircraft>TestAA-T010</required-aircraft>
        <actype>319</actype>
        <offset>0</offset>
        <radius>17</radius>
        <flighttype>gate</flighttype>
        <performance-class>jet_transport</performance-class>
        <registration>SRB011</registration>
        <heavy>false</heavy>
    </aircraft>
    <flight>
        <callsign>TestAA-101</callsign>
        <required-aircraft>TestAA-T010</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>06:50:00</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>07:35:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <flight>
        <callsign>TestAA-102</callsign>
        <required-aircraft>TestAA-T010</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>07:50:00</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>08:35:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <!-- FLIGHT 11 -->
    <aircraft>
        <model>Aircraft/A350/359-FGFS.xml</model>
        <livery>RBH</livery>
        <airline>RBH</airline>
        <home-port>EGSS</home-port>
        <required-aircraft>TestAA-T011</required-aircraft>
        <actype>319</actype>
        <offset>0</offset>
        <radius>17</radius>
        <flighttype>gate</flighttype>
        <performance-class>jet_transport</performance-class>
        <registration>SRB111</registration>
        <heavy>false</heavy>
    </aircraft>
    <flight>
        <callsign>TestAA-111</callsign>
        <required-aircraft>TestAA-T011</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>06:55:00</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>07:40:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <flight>
        <callsign>TestAA-112</callsign>
        <required-aircraft>TestAA-T011</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>07:55:00</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>08:40:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <!-- FLIGHT 12 -->
    <aircraft>
        <model>Aircraft/A350/359-FGFS.xml</model>
        <livery>RBH</livery>
        <airline>RBH</airline>
        <home-port>EGSS</home-port>
        <required-aircraft>TestAA-T012</required-aircraft>
        <actype>319</actype>
        <offset>0</offset>
        <radius>17</radius>
        <flighttype>gate</flighttype>
        <performance-class>jet_transport</performance-class>
        <registration>SRB121</registration>
        <heavy>false</heavy>
    </aircraft>
    <flight>
        <callsign>TestAA-121</callsign>
        <required-aircraft>TestAA-T012</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>07:00:00</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>07:45:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
    <flight>
        <callsign>TestAA-122</callsign>
        <required-aircraft>TestAA-T012</required-aircraft>
        <fltrules>IFR</fltrules>
        <departure>
            <port>EGSS</port>
            <time>08:00:00</time>
        </departure>
        <cruise-alt>290</cruise-alt>
        <arrival>
            <port>EGSS</port>
            <time>08:45:00</time>
        </arrival>
        <repeat>2Hr</repeat>
    </flight>
</trafficlist>
My Github repository (mostly AI stuff) https://github.com/gooneybird47
User avatar
gooneybird
 
Posts: 3046
Joined: Sat May 31, 2008 2:57 pm

Re: AI Aircraft beacon

Postby BecOzIcan » Sat Sep 02, 2017 11:48 am

Update on valid=true condition as a way to detect aircraft has reached final destination gate and lights can be turned off.

Test complete, functionally ok but results not as expected.
Test Conditions/Data : FG 2.12, 4 aircrafts assigned to a shuttling service between LFPP and LFPG (1 flight leaves each airport every 15 minutes for a 15 minutes flight, round the clock)
Observed :
- Condition Valid=True does NOT turn to false on final parking
Once flight complete and aircraft has stopped moving :
- Callsign changes to a (return) flight leaving 4 hours later
- Transponder-id is retained.

It may well be that the [valid] turns to false if no return flight exist in the traffic file but this is not a valid test for production
I have made a point of ensuring all aircraft have fully looped (back to their departing hub) flight plans as part of the traffic files cleaning ongoing for the past two years.

Should you guys want to run extra testing on other versions, feel free to download the update main.xml for the A350 from HEREl

I ll get back to trying to set up my non nasal lightmap day/night switch

Cheers
Ian
Current Projects: AI Traffic, Models & Liveries
User avatar
BecOzIcan
 
Posts: 1302
Joined: Tue Oct 04, 2011 11:43 pm
Location: Sydney, NSW, Australia
Version: 2020.4.0
OS: Win10

Re: AI Aircraft beacon

Postby wkitty42 » Mon Sep 04, 2017 1:27 pm

valid turns to false if there's no flight within the next whatever hours... i don't know how long that period of "whatever" is... jus that if there's more records than there are flights, the unneeded ones will go "valid=false"... the transponder number also changes, IIRC...

i would guess that in your case, valid did go to false but immediately back to true as the AI system reassigned the record to another flight...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 9148
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: AI Aircraft beacon

Postby BecOzIcan » Sat Sep 09, 2017 2:01 pm

Final Implementation complete and ready for review; 7 days of UAT allocated. Final code will be pushed to GIT Saturday 16 SEP

Changes since last iteration :

- Light ac Models size increased so that lights are visible at larger distance . Confirmed that FG filter objects to draw based on size BEFORE any Dist-Scale factor applied.
- Lights still appear larger when Rembrandt is ON but I couldn't figure out what drives this behaviour. Dist-Scale updated so to reduce the size discrepancy between the two states. Feel free to play with this factor and suggest updated values
- Strobe Lights moved away from navigation lights to avoid superposition in the distance.
- Light map added : Independently of Navigation lights, Tail and Windows light up at night. Requires latest version of FG. For older versions, replace the local-weather-rules.xml files in FGROOT$\Data\Environments with this ONE successfully tested in FG 2.12
- Code structure updated. Navigation Lights commands split to a dedicated xml file.

Test Pack 3 available from HERE

Cheers
Ian

Image
Current Projects: AI Traffic, Models & Liveries
User avatar
BecOzIcan
 
Posts: 1302
Joined: Tue Oct 04, 2011 11:43 pm
Location: Sydney, NSW, Australia
Version: 2020.4.0
OS: Win10

Re: AI Aircraft beacon

Postby legoboyvdlp » Sat Sep 09, 2017 2:29 pm

BecOzIcan wrote in Sat Sep 09, 2017 2:01 pm:- Light map added : Independently of Navigation lights, Tail and Windows light up at night. Requires latest version of FG. For older versions, replace the local-weather-rules.xml files in FGROOT$\Data\Environments with this ONE successfully tested in FG 2.12


On airbus aircraft at least, the logo light automatically turns off upon liftoff, and turns on again when the flaps are set to three on final approach. To keep it simple, you could make them turn on at touchdown, if you do this?
User avatar
legoboyvdlp
 
Posts: 7981
Joined: Sat Jul 26, 2014 2:28 am
Location: Northern Ireland
Callsign: G-LEGO
Version: next
OS: Windows 10 HP

Re: AI Aircraft beacon

Postby BecOzIcan » Sat Sep 09, 2017 5:08 pm

legoboyvdlp wrote in Sat Sep 09, 2017 2:29 pm:
On airbus aircraft at least, the logo light automatically turns off upon liftoff, and turns on again when the flaps are set to three on final approach. To keep it simple, you could make them turn on at touchdown, if you do this?


Simply not happening with an AI aircraft. No detailed xml properties available
Current Projects: AI Traffic, Models & Liveries
User avatar
BecOzIcan
 
Posts: 1302
Joined: Tue Oct 04, 2011 11:43 pm
Location: Sydney, NSW, Australia
Version: 2020.4.0
OS: Win10

Re: AI Aircraft beacon

Postby BecOzIcan » Thu Sep 14, 2017 2:56 pm

Navigation Lights, Beacons and Strobes as well as Lightmap added to A380 AI model.

Image

Image
Current Projects: AI Traffic, Models & Liveries
User avatar
BecOzIcan
 
Posts: 1302
Joined: Tue Oct 04, 2011 11:43 pm
Location: Sydney, NSW, Australia
Version: 2020.4.0
OS: Win10

PreviousNext

Return to AI Traffic

Who is online

Users browsing this forum: No registered users and 8 guests