Thank you Roland for the video and the tip. I have created STARs for DTTA now with custom waypoints and it turned to be very easy!

 

Cheers

Nizar

Roland, I've only just had a chance to troubleshoot the util.dll CTD that a few of us seem to be having. Switching on UT2 compatabilty seems to be the culprit. The crash will happen about 30mins in (not an exact time, just a rough guess). I switched the function off and managed a 2 hour flight with no CTD.

Roland, I've only just had a chance to troubleshoot the util.dll CTD that a few of us seem to be having. Switching on UT2 compatabilty seems to be the culprit. The crash will happen about 30mins in (not an exact time, just a rough guess). I switched the function off and managed a 2 hour flight with no CTD.

 

Thanks, were you running AISIDSTAR on a networked computer?  This is necessary to avoid the FSX crashing problem you described (when UT2 compatibility it turned on).  I probably need to add a line that prompts the user to acknowledge the networked computer requirement when UT2 compatibility it turned on.  It is too easy to overlook, for example if someone has forgotten they turned on UT2 compatibility some months ago.

 

-Roland

Thanks, were you running AISIDSTAR on a networked computer?  This is necessary to avoid the FSX crashing problem you described (when UT2 compatibility it turned on).  I probably need to add a line that prompts the user to acknowledge the networked computer requirement when UT2 compatibility it turned on.  It is too easy to overlook, for example if someone has forgotten they turned on UT2 compatibility some months ago.

 

-Roland

I should of added that I am in fact using AISIDSTAR over a network. Always have. I seem to still be getting the program to work effectively without UT2 compatability turned on, getting a steady flow in to all of the airports I have monitored at that time.

I run AISIDSTAR locally, having never been able to run it in a networked configuration.  I don't use Ultimate Traffic, if that matters.

 

I can run some other Fsx add-ons (FSUIPC WIDEFS and EFB) with no problems, but when I try to run AISIDSTAR remotely, it doesn't seem able to connect and I've set the Simconnect cfg and ini files correctly according to what I've read on the Acticesky page, I think.

 

Does anyone have a simplified cheat sheet for this?

Those who use AISmooth with AIDISTAR, would you share your settings in AISmooth:

 

Minimum IFR Holding Altitude [ft MS]

Landing Release Altitude [ft AGL]

Minimum center line distance [NM]

Poll interval [msec]

Control Batchsize

Command Delay [msec]

Reduce speed on approach

Use dynamic speed table

 

 

Thanks,

Dirk.

 

PS: AISmooth is not compatible with AISIDSTAR according to the developer.

 

Rev. 1.2M (beta) can be found here: 

 

http://www.mediafire.com/download/8cdaa2si4bsihie/AISIDSTAR12M.zip

 

 

The link is dead. Please update.

 

Thanks,

Dirk.

The link works for me fine.

The link works for me fine.

 

Now it works for me, go figure.

 

Dirk.

I should of added that I am in fact using AISIDSTAR over a network. Always have. I seem to still be getting the program to work effectively without UT2 compatability turned on, getting a steady flow in to all of the airports I have monitored at that time.

 

OK, I'll take a look.  Right now I'm testing/trouble-shooting a new release-from-hold algorithms that I discussed earlier in the thread with andqui.  Hopefully I can revisit the UT2 issue soon as well as the telemetry table issue.

 

 

I can run some other Fsx add-ons (FSUIPC WIDEFS and EFB) with no problems, but when I try to run AISIDSTAR remotely, it doesn't seem able to connect and I've set the Simconnect cfg and ini files correctly according to what I've read on the Acticesky page, I think.

 

 

I think WideFS and EFB have more sophisticated networking capability, I'm just relying on Simconnect only.  Take a look at the HiFi Networked Configuration FAQ (not because it has anything to do with my utility, but because they have really good instructions about connecting to Simconnect via a network) at http://support.hifitechinc.com/Knowledgebase/Article/View/6/3/networked-configuration-with-simconnect.  If you can get AITraffic.exe to run over the network at the end of their instructions, then AISIDSTAR should run over the network as well.

 

 

 

 

PS: AISmooth is not compatible with AISIDSTAR according to the developer.

 

Yes, both are trying to vector the AI to waypoints in the terminal area.  AISeparation on the other hand does something so strange (yet effective) - slewing the AI backwards in a straight line - that ironically it only minimally impacts my program.

 

Regarding AISmooth, you could try increasing the NoVectorDistance and NoVectorAltitude values in the AISIDSTAR.ini file, so that only AISmooth performs vectoring in the terminal area.  Just watch out for STAR exit way points being closer than the NoVectorDistance distance.

 

-Roland

is it possible by any chance to manipulate arrival runways assigned to ai aircraft with this program? by default fsx assigns runways based on direction of origin airport of flight which at many airports leads to arrivals crowding on a particular runway. would be nice to have runways assigned randomly or by airline or aircraft type if fsx allows

FSX uses parallel runways just fine. Enabling the use of appropriate crosswind runways has to be done on a per-airport basis by creating a custom AFX file with ADE.

Running my first real AISIDSTAR test at BOS right now and it's working pretty neatly.

Since wind is practically nonexistant (3 kts)and since I've equipped BOS with working crosswind runways, I've got 22L (22R is t/o only), 27 and 33L and 33R operating.

Even with AISIDSTAR controlling arrivals, I got some go-arounds in the beginning when planes simultaneously tried to land on two of these four runways (also, because there's lots of small commuters coming and going).

 

I've seen one plane warping away so far after a go-around. Not pretty, but if it works...

 

Furthermore, AISIDSTAR crashed once, but I guess this was due to me scrolling around in the window and AISIDSTAR monitoring basically every airport within 200nm.

 

 

Let's see if the tool works as well during an actual flight (I'm only traffic spotting ATM).

Would it be possible to allow the importation of SIDS and STARS from flightplans created with a 3rd party programs like FSBuild or FSC. I only fly Australian skies, and at the moment I can't work out how to adapt this program for my use.

Small turboprops (Do228, TwOtter) tend to go warp 7 after takeoff. Is that intended?