Hi Roland

 

I can also confirm that the program'crashes' whilst in Germany. I'm sat at EDDF. It will start and connect to FSX then 'crashes'

 

 

 

Clive

 

Nizar and Alpha, found the error, it had to do with the act of checking the SID pattern names for the "JET" and "PROP" only keywords (even though none of the German SIDs are so restricted).  Another side effect of the bug is that the jet-only and prop-only SID(s)  feature is broken in Rev K.  Unrestricted SIDs are still working though.

 

I'll have a fix available shortly, I'm working another issue as well ATM.

 

Alvega, this is probably the fix for your issue too.

 

Thanks for the feedback guys.

 

-Roland.

Many thanks Roland, for your video.

 

Great help.

 

Regards,

Many thanks to you too Roland for fixing this!

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

 

http://www.mediafire.com/download/s88g1pnl79o8vtx/AISIDSTAR12L.zip

 

I'm pushing this beta version out ahead of schedule because the SID file read error discussed earlier today is a show stopper to those affected.

 

Fixed:  Act of reading SID file for the "prop" only and "jet" only parameter sometimes caused AISIDSTAR to crash, even if the SID file was not restricted to prop or jet only.  Also, the selection of actual prop and jet only SIDs was broken.

 

Fixed: Introduced bug in ver. 1.2K that made STAR exit holding less effective.  This bug has been removed.

 

Fixed: Holding tables out of sync causing program to miscalculate when forced releases from holds (overload condition) should start and stop.

 

Updated:  Forced release from hold "mode" will additionally temporarily disable STAR exit waypoint holding (if enabled in the .ini file) if the number of holding AI exceeds 35.  STAR exit waypoint holding will be re-enabled when holding AI falls below 25.   This is just to clear out the AI more quickly if too many are holding and to get them to land, however the risk of go-arounds increases. 

 

New:  Streaming Video Documentation.

 

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

 

Thanks!

-Roland

Hi Roland,

 

Do i have to convert the files again or i just copy and paste the AISIDSTAR.ini i already have over the new one?

 

Thanks.

Alvega, your converted files are fine.  Save them and any custom .ini you made.  Delete 1.2K entirely, unzip and install version 1.2L, then move your converted files and custom into the version 1.2L installation.

 

-Roland.

Tried with the default AISIDSTAR.ini, doesn't crash. As soon as i opened it with my AISIDSTAR.ini for the portuguese airports it crashes within 20 secs.

 

Doesn't crash with the German ini also, but all i get is this:

 

Tried with the default AISIDSTAR.ini, doesn't crash. As soon as i opened it with my AISIDSTAR.ini for the portuguese airports it crashes within 20 secs.

 

OK, re-run it with verbose = 1 and debug = 1 until it crashes.  Then zip up the log file, your portuguese SID/STAR files, and the .ini you're using.  Email it to my support email address on the last page of the readme file (or put the files in dropbox and email me the link).  I'm sure we'll get it straightened out.

 

-Roland. 

Files sent to your email, Roland.

Interesting, the program is saying it can't find any jets or turbo-props to vector.  The program reads the engine type of the AI and will only vector engine types 1 (jet) and 5 (turboprop).  The program assumes other engine types, such as piston (0), helicopter (3), none (2) and unsupported (4) are not commercial aviation (e.g., general aviation, gliders, experimentals) and thus doesn't vector them.

 

In the FSX display settings, do you have airline traffic density set to zero, but general aviation traffic density set to a non-zero value?  If not, what type of airliner AI package are you using?

 

-Roland

 

 

Tried with the default AISIDSTAR.ini, doesn't crash. As soon as i opened it with my AISIDSTAR.ini for the portuguese airports it crashes within 20 secs.

 

Doesn't crash with the German ini also, but all i get is this:

 

In FSX i have both airline and GA set to zero because i use Ultimate Traffic 2.

I also saw lots of these "Will not vector" when i tested in KDFW.

In FSX i have both airline and GA set to zero because i use Ultimate Traffic 2.

I also saw lots of these "Will not vector" when i tested in KDFW.

 

Very interesting,  I'll send you a special test version (to the email address you provided) that doesn't read engine types.  We can find out if AISIDSTAR will vector Ultimate Traffic 2 AI and if so, how well!  I wish I could buy all the commercial AI and ATC packages, but that would get very expensive, so I appreciate any feedback you can provide.

 

-Roland.

 

EDIT:  Here's the test version for you (or anyone) having compatibility issues with UT2.  This is the .exe only (zipped up), so replace the old Rev. L .exe with this file.  Give a try and let me know how it goes.  Feel free to use my support email address on the last page of the readme.

 

http://www.mediafire.com/download/dblzdqna3f1w5hq/AISIDSTAR_Rev_L_Special_No_Engine_Type.zip

Hi Roland,

 

Re UT2. One thing to note about that software is it only spawns aircraft within a 50nm radius of the users aircraft. I had mixed results with UT2 because aircraft would get picked up by your software and then vectored to the nearest STAR but because it began more than 50nm from my aircraft they would then drop off the radar never to return. Your program therefore does not work too well with UT2 due to this. Unfortunately there is no way to increase the spawning radius with UT2 which is a real pain tbh. It should have been a user configurable setting.

 

Andy

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

Hi Clive,

 

Are you using the new exe from the test version or the 1.2L version?