Alvega,

 

I'm using this one

 

http://www.mediafire...Engine_Type.zip

 

This versions works with UT2

Hi Andy

 

I also run UT2.

 

From Roland:

Try this  Change the AImaxspawndistancefromstar parameter in the .ini file from 200 to 70. You could try some as small as 50 or 40.

 

Also, make sure AIholdingallowed=0 in the .ini file because a hold might be mistaken for an AI trying to "go back" to a jet route.

 

I've got mine set to 70 and was watching via EFB at EDDF today, looked very good.

The only slight issue I had today was on departures, in that some seemed to depart then return to departure airport and then turn around again and depart as normal, very strange.

 

Roland is aware of this issue and is looking into it.

 

Clive

 

Thanks for the heads up Clive. Surely it should be set to 50 though or there is still the potential for aircraft turning round to join a star and disappearing when they get 50nm's away from the users aircraft. I'll give it a go and report back.

 

Best

 

Andy

Thanks for the heads up Clive. Surely it should be set to 50 though or there is still the potential for aircraft turning round to join a star and disappearing when they get 50nm's away from the users aircraft. I'll give it a go and report back.

 

Best

 

Andy

 

That could be a problem.  However, AIConv.exe creates a parallel set of "short" STARs that are the regular STARs, but with the entry point being the first way point that is within 30 nm (default) of the airport.  The short STARs are designed for a issue with similar ramifications - AI spawned by FSX close to the destination airport and much closer than published STAR entry points.

 

These entry points should still be in front of the AI even if the AImaxspawndistancefromstar  is turned down to 35 or 40 unless the user is going with custom STARs or has decided to delete the short STARs.

 

I'm actually working on a fix right now - it might be possible to replace the UT2 AI's jet route flight plan when it is time for the AI to join the STAR with a much simpler (and AISIDSTAR friendly) flight plan direct to the destination airport.   Same concept for departing AI.  There is one drawback for departing AI though -- in the rare instance the user actually follows the AI through the SID the user may notice the AI will not transition to the UT2 jet route flight plan after exiting the SID, but instead flies direct like regular FSX AI.  I don't think this will be a big deal.  Most of the time the user will diverge from the departing AI and they will all go their separate ways, so the user will never even notice.

 

Unfortunately, it may take me two or three days to even get to the point where I can test the basic feasibility of this fix, so please bear with me.

 

In the mean time, keep experimenting with AImaxspawndistancefromstar .  You can also "comment out" the all the SIDs in the .ini if the tendency for the UT2 AI to "go back" toward the departure airport is too annoying.  I'm pretty sure AISIDSTAR should run without any SIDs to select. 

 

-Roland

There is one drawback for departing AI though -- in the rare instance the user actually follows the AI through the SID the user may notice the AI will not transition to the UT2 jet route flight plan after exiting the SID, but instead flies direct like regular FSX AI.  I don't think this will be a big deal.

 

Sorry Roland, but this would be a major drawback to me, and i guess for other UT2 users also.

Flying jet routes is perhaps the main feature of UT2, the one that makes it different from all other AI addons. I like to fly to the destination and see the other planes aligned on the same airway or crossing below or above me, as it is in real world. I guess i prefer not to have them fly SIDS and STARS than losing that feature.

Sorry Roland, but this would be a major drawback to me, and i guess for other UT2 users also.

Flying jet routes is perhaps the main feature of UT2, the one that makes it different from all other AI addons. I like to fly to the destination and see the other planes aligned on the same airway or crossing below or above me, as it is in real world. I guess i prefer not to have them fly SIDS and STARS than losing that feature.

 

No, that's not how it would work.  The arriving UT2 AI completes its jet route per normal, then when it is ready to join the STAR, the flight plan gets replaced.  The departing UT2 AI will get its flight plan replaced on takeoff, but unless you follow a particular AI to the destination, you won't notice.  Much more likely, the departing AI will quickly leave your reality bubble and disappear.  If a departing AI ever re-enters your reality bubble, the AI is re-injected by UT2 and it will have its jet route flight plans back per normal.

 

Anyway, I'm not sure the code is feasible, so you may not even have to worry about how you think it will work.

Sorry Roland, looks like i misunderstood how it worked.

Hi to all

 

To abort thank you Clipper Ocean Spray. I use Prepar3D + The latest version "AISIDSTAR Rev L" and Sids and Stars "FRANCE PMDG" Well, I have a bug with traffic as:

 

MyTraffic V-5.4Ba

-Orbx (all traffic)

 

If I use the "No Special AISIDSTAR Rev L Engine Type.exe" everything is ok

 

I continued testing, good luck (sorry for all my English, am French and translate it with Google)

Bertrand

Guys,

 

If you think that the AI separation is not right, then have a look at this video that Roland has made. This explains how it works.

 

http://mfi.re/watch/74e3kqyt4sndhwd/AISIDSTAR_Video_3_Operating_Parameters_Part_2.mp4

I can't open the video, it's only 62KB here.

 

Thanks,

Dirk.

Dirk 

 

Does this link work?

 

http://www.mediafire.com/watch/74e3kqyt4sndhwd/AISIDSTAR_Video_3_Operating_Parameters_Part_2.mp4

I can't open the video, it's only 62KB here.

 

Thanks,

Dirk.

 

Don't try to save the lideo from the link, just click it instead. It takes you to a page where it'll start playing, and if you want to you can download it there.using the 'Download' option.

 

Pete

1. The readme says that traffic will be sped up as well as slowed down to maintain separation. I've only seen console messages for 60% speed reductions, not for speeding up. Is this as intended? If the "lead" aircraft sped up while ones behind it slowed down that would help a lot for separation.

 

2. I'm currently testing for a flight I'm planning to do from LPPT to LPPR. I converted the PMDG data for these two airports and made them the only two being monitored. Departing traffic from LPPT are vectored around on SIDs perfectly, EXCEPT for those that are going to LPPR (the other monitored airport). For example, "Arriving Portugalia flight no 1978 (CS-TPH) spawned more than 10 nm from monitored dep arirpot LPPT, and more than 200 nm from monitored dest airport LPPR" after takeoff rather than a SID assignment, and it just flies direct. Don't know if it's a problem with the message wording or the code logic, but the flight did not spawn more than 10 nm from LPPT AND more than 200 nm from LPPR, but rather it spawned more than 10 nm from LPPT OR more than 200 nm from LPPR. Is it impossible to vector traffic that's flying between two monitored airports? I get the same unable to vector message from traffic arriving at LPPT from LPPR.

 

thanks

Roland,

 

Been having an crash issue. I have loaded all the SIDS and STARS from Germany, created from NavDataPro, and the application will crash before it starts to detect any AI. I have used the original version L and the engine type version with crashes with both.

 

I have attached the crash dump from windows for you to have a look at and see if the shows anything. If you need anymore info let me know!

 

 

 

EDIT: I'm currently working through a process of elimination to see if I can solve this crash myself. I will report back shortly.

Edited August 16, 201312 yr by jambo50

1. The readme says that traffic will be sped up as well as slowed down to maintain separation. I've only seen console messages for 60% speed reductions, not for speeding up. Is this as intended? If the "lead" aircraft sped up while ones behind it slowed down that would help a lot for separation.

 

2. I'm currently testing for a flight I'm planning to do from LPPT to LPPR. I converted the PMDG data for these two airports and made them the only two being monitored. Departing traffic from LPPT are vectored around on SIDs perfectly, EXCEPT for those that are going to LPPR (the other monitored airport). For example, "Arriving Portugalia flight no 1978 (CS-TPH) spawned more than 10 nm from monitored dep arirpot LPPT, and more than 200 nm from monitored dest airport LPPR" after takeoff rather than a SID assignment, and it just flies direct. Don't know if it's a problem with the message wording or the code logic, but the flight did not spawn more than 10 nm from LPPT AND more than 200 nm from LPPR, but rather it spawned more than 10 nm from LPPT OR more than 200 nm from LPPR. Is it impossible to vector traffic that's flying between two monitored airports? I get the same unable to vector message from traffic arriving at LPPT from LPPR.

 

thanks

 

Thanks, I'm reworking that section of the code to grab airport position data from the external airports database if FSX doesn't post it internally, that should alleviate problem.

 

Roland,

 

Been having an crash issue. I have loaded all the SIDS and STARS from Germany, created from NavDataPro, and the application will crash before it starts to detect any AI. I have used the original version L and the engine type version with crashes with both.

 

I have attached the crash dump from windows for you to have a look at and see if the shows anything. If you need anymore info let me know!

 

AISIDSTAR Crash.txt

 

This is probably related to an error that Alvega reported earlier with AIConv.exe.  One or more of the converted SID or STAR files probably has "HOLD" in the altitude restriction field.  This issue has been fixed in Rev. M, which should be available shortly.

 

BTW to all, Rev. M will provide UT2 compatibility.  The algorithm I discussed earlier seems to be working well.

 

-Roland. 

Thanks, I'm reworking that section of the code to grab airport position data from the external airports database if FSX doesn't post it internally, that should alleviate problem.

 

 

This is probably related to an error that Alvega reported earlier with AIConv.exe.  One or more of the converted SID or STAR files probably has "HOLD" in the altitude restriction field.  This issue has been fixed in Rev. M, which should be available shortly.

 

BTW to all, Rev. M will provide UT2 compatibility.  The algorithm I discussed earlier seems to be working well.

 

-Roland. 

I found where the error lies by turning on the logging and verbose features. Let me just elaborate a little more...

 

It wasnt only Germany files I was loading, I also had Italy, Switzerland, France and Spain files loaded, as my flightplan took me over these areas.

I disabled all the areas, then one by one enabled them again to find where the problem files was. It seems to be one from Switzerland that is causing the hassle. I've attached the log file to confirm this. Not a big deal, I can disable Switzerland for now.

I was probably a bit quite to point the finger at the German files, as I know there was an issue with a previous release which has now been fixed.

Anyways keep the development going, Roland!

 

Thanks again