Your latest conversion utility crashes on EBBR.TXT Can I add it here or post it ?

Oh, and cant you include it in the exe ? so it does the job on the fly ?

Then we dont need a conversion :-)

 

Hmm, you must be using NavDataPro (I checked the Navigraph EBBR.txt and it worked).  Send it to my support address in the readme and I'll take a look.

 

Regards,

-Roland 

Mike, did you change the AImaxspawndistancefromstar parameter to 70 in the .ini file (i.e., AImaxspawndistancefromstar=70)?  AImaxspawndistancefromstar can be further reduced to 40 or 50 if necessary. This parameter allows the AI to complete the UT2 jet routes before getting vectored onto a STAR.  If the AI is vectored to a STAR entry point (transition) too early (e.g., the default 200 nm away from the airport), it will likely miss an UT2 jet route waypoint.  Then when the AI gets released for final approach, it turns back and tries to hit the jet route waypoint anyway.

 

That being said, I agree with you that the final STAR exit waypoint being co-located with the beginning of the ILS is problematic.  In the readme I recommend about a minimum 7 nm separation between the STAR exit and the final approach fix, although it is case by case (e.g., at some airports a lower separation doesn't seem to have any negative effect).  I would recommend just deleting the exit waypoint from the STAR file, the AI will probably fly a similar approach without the deleted waypoint.

 

Regarding the ATC telling the AI to climb back to 15000, are you using stock FSX ATC?  I mention this in the NOTAM section of the readme file, but unfortunately stock FSX ATC and AISIDSTAR are at cross purposes.  AISIDSTAR is making the AI fly published STARs and the "voice" part of FSX ATC gets upset about that.  I recommend buying a more advanced ATC program, such as Radar Contact or Pro-ATC/X, but only if that's something that really interests you in and of itself.

 

-Roland

 

Thanks a lot for the tips.  I will try them out as well as read the readme :-p

Worked very nice now!

Just take a look in a mountain area, like LOWI.

Amazed!

Just take a look in a mountain area, like LOWI.

 

Speaking of...

 

Are AI planes using the actual terrain avoiding approaches for LOWI now?

 

If so, one can save a ton of work making custom apporaches in AFX files.

Yes, if the sid or star takes it in account, and it should do that of course, the departures I saw at my sample at LOWI did it very nice.

Have to check more, but looks extremely good!

Just thinking of the VHHH approach.. one should of course disable the hardcoded approaches in addon scenery, or test with default, but cannot

remember if old Kai Tak is still in FSX.

 

EDIT: of course it wont work.. we have no star tekst file, and to lazy to make one.

Find another area with a curved approach..

Well, ASE or LCY would be other candidates for unusual approaches. And NYC for congested airspaces.

Speaking of...

 

Are AI planes using the actual terrain avoiding approaches for LOWI now?

 

If so, one can save a ton of work making custom apporaches in AFX files.

 

If the STAR or SID is designed to keep aircraft away from terrain, then yes, AISIDSTAR will prevent the AI from flying into terrain.  Just make sure to keep the AIPatternAlt at its default value of 3000 ft AGL or higher and avoid adding altitude restrictions (which are MSL) to the SID/STAR files unless they're well above the terrain.

 

You may notice when AI are holding, the altitude sometimes varies because the AI is adhering to an AGL altitude (unless a STAR MSL altitude restriction applies).

 

As for the final approach phase, you can also edit the STAR file to extend the waypoints beyond the STAR and into the terminal area of the approach, it might work on a case by case basis.   You would need to reduce the NoVectorDistance and NoVectorAltitude values from their defaults of 7nm and 1500 ft AGL.  However, vectoring the AI when it is closer than 7 nm to the airport may also cause the chronic go-around bug (this is an issue with AISmooth and AISeparation as well).  If you want to go below 7nm, one way to mitigate the chronic go-around bug  is simply to reduce traffic density and/or enforce large minimum separation distances (AISeparationDistance) with STAR exit holding enabled (AIHoldingAllowed = 2, 3 or 4).

 

There's also an issue with the FSX IAF waypoint usually around the 7 nm mark that the AI need to hit before it turns onto final.  If you're going to extend the STAR into the terminal area, you may need to make sure the STAR waypoint and this IAF waypoint (from the .bgl file) line-up using ADE or the like. 

 

BTW, I might be unavailable for a few days.  One issue I've noticed with 1.2N so far (now that I've tested it at more airports) regards a new feature - detection of "off angle" approaches.  False detection is happening more frequently than I expected.  The only side effect is occasionally an AI that appears to be on a "good" approach will be commanded to perform a go-around thus reducing arrival rates.  The false detections are probably worth it however because a valid detection prevents the AI flying from directly toward the airport low and slow, trying to line up for the runway too late at odd angle, then landing well past the threshold, missing the runway entirely, or going-around.  I'll look into tweaking the detection parameters for the final version, but if this is a problem for anybody, the feature can be turned off entirely by adding AIAntiOffAngleApproach=0 to the .ini file.

 

-Roland

I am seeing the bug also.. trying with 0

EDIT: Done, but still no approaches anymore.. they all seemed to be way to high, and go missed well before reaching the airport.

I set the distance to 10nm, but doesnt help

Just wanted to check and see if this is still being developed? Been away from FS since summer. 

Just wanted to check and see if this is still being developed? Been away from FS since summer. 

 

Yep, new version should be available shortly!

 

-Roland

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

 

http://www.mediafire.com/download/8pjd27qiqa5mcel/AISIDSTAR12P.zip

 

New:  Travis (from AivlaSoft and FSCaptain) added the very nice Northern California custom SID/STAR files including:

 

The Bay Area Hubs (KOAK, KSFO, KSJC)

The Bay Area Regionals (KCCR, KHAF, KHWD, KLVK, KNUQ, KPAO, KRHV, KSQL)

The Cascade Regionals  (KSIY, 3S8), North Bay Regionals (KAPC, KSTS, KDVO, O60, O69)

The North Coast Regionals (KACV, KCEC, KEKA, KFOT, KLLR, KUKI, O28), 

The Central Coast Regionals - (3O7 aka KCVH, E16, KMRY, KOAR, KPRB, KSTS, KWVI), 

The Sacramento Central Valley Regionals (0O5 aka KEDU, 2Q3 aka KDWA, KAUB, KBAB mil, KCIC, KMCC, KMHR, KMYV, KOVE, KRBL, KRDD, KSMF, KSUU mil, KVCB, KWLW, O08, O17 aka GOO, O37, O41, O88)

The San Joaquin Central Valley Regionals (1O3, C83, F34, KFAT, KFCH, KHJO, KMAE, KMCE, KMER, KNLC mil, KPTV, KTCY, KTLR, KVIS, O27)

The Sierra Regionals (E45, KBIH, KCPU, KMMH, KPVF, KTVL, O22, O68, O70).

 

Please be sure to check out his readme file included in the NORCAL directory.  A huge thanks to Travis for all your help!

 

New: a stand-alone windows monitoring program, similar to AISeparation/AISmooth called AISIDSTAR_Monitor.exe.  This windows program will provide you a tablular overview of AI traffic in your area including which AI is under the control of FSX and which is under the control of AISIDSTAR.  The program will also summarize the AI special command modes under control of AISIDSTAR.  Requires Net Client 4.0 (should already be present on most Windows computers).

 

New:  Along with the smaller regional airports added by Travis, AISIDSTAR now supports vectoring of piston (e.g., general aviation) aircraft and VFR (e.g., DPART) procedures, if optionally enabled.

 

New: Target landing rate parameter added to better control landing flow rates.

 

Revised: Landing rate code.

 

Revised:  UT2 mode no longer requires specification of any filepath.

 

Fixed: Waypoint names and altitude restrictions were sometimes printed incorrectly in telemetry output file.

 

Fixed.Writing telemetry output sometimes caused AISIDSTAR to crash.

 

Please consult the following video documentation (Note: for Rev. M, but still mostly applicable to the latest revision).

 

Video 1 - Working with the Included Sample SID/STAR Files and Creating New Files Using AIConv.exe:  http://www.mediafire.com/watch/mj3hgm33w24thcv/AISIDSTAR_Video_1_Sample_SID_STAR_Files_and_Creating_New_Ones_Using_AIConv.mp4

 

Video 2 - Custom Editing SID/STAR Files - http://www.mediafire.com/watch/t9irz80c497beo7/AISIDSTAR_Video_2_Custom_Edit_SID_STAR_Files.mp4

 

Video 3 - Operating Parameters.

 

Part 1: http://www.mediafire.com/watch/urlrrdp09v5y5l4/AISIDSTAR_Video_3_Operating_Parameters_Part_1.mp4

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

Part 3: http://www.mediafire.com/watch/24s4ek5x7xtiuf8/AISIDSTAR_Video_3_Operating_Parameters_Part_3.mp4

Part 4: http://www.mediafire.com/watch/24s4ek5x7xtiuf8/AISIDSTAR_Video_3_Operating_Parameters_Part_3.mp4

Part 5: http://www.mediafire.com/watch/24s4ek5x7xtiuf8/AISIDSTAR_Video_3_Operating_Parameters_Part_3.mp4

 

 

Thanks!

-Roland

Eeek!  I couldn't keep up with Roland and his manic "here's a new [something]" and "here's a new [something-else]"!"

 

AISIDSTAR is a wonderful addition to what we know of as our generic MSFS AI ATC. (It gets my vote as add-on of the year!!)  You can listen to your ground controllers.  You can listen to your tower controllers.  You can even listen to your bleeding enroute controller if you like....

 

But just ignore your built-in Departure and Arrival controllers because with this utility Roland has given us the ability to guide all of our AI on realistic arrival and departure procedures!!  Wooah!!!

 

Anyway, all I've done is to tweak procedures near and dear to where I'm at... just so that I can make my FSCaptain airline flights and not have civvies dash around willy-nilly in my presence.  :rolleyes:

 

Over the next week or so, I'll branch out to finish the remainder of the Nevadian airports under control of Oakland Center.  Then I'm looking forward to guiding the souls going into and out of Iceland and other island airports in the North Atlantic.  Because to mimic a now well worn (well-stomped upon?) mainstream catchphrase, "Winter is coming...."  <_< 

First, please be patience with me because I am not familiar with cmd commands on windows..

 

Could anybody help to convert PMDG airport files?

I have FSX installed in this way C:\FSX\AISIDSTAR12P

Then, I created two folders called: "Brazil PMDG" where contains SID/STARS texts and "Brazil Sample" where should be the output path.

Finally I type on cmd line (following the example of the program):

 

C:\FSX\AISIDSTAR12P>aiconv .\brazil pmdg\*.* .\brazil sample\ 

 

But it comes a message that the output path must be existing.

 

Just to explain, I put *.* because I want to convert all files of the Brazil pmdg folder, since it has several aiports. But don´t know why the program says the patch does not exist, because the line C:\FSX\AISIDSTAR12P>aiconv .\brazil pmdg\*.* .\brazil sample\  says by itself the the path. Finally, I actually have the folder Brazil folder under c:\FSX\aisidstar12p it was created with this objective. 

 

Thank you, any help will be be very appreciated.

Please, ignore my last post, I found the correct instructions here http://forum.avsim.net/topic/408490-ai-aircraft-sid-and-star-controller/page-5#entry2704441

 

However, aiconv crashes in the first airport that he finds. 

So I am new to this program and was wondering if this would make ai approach as real real aircraft do at MHTG ( Toncotin ) ?