bib974

Hi Roland, Thanks for this, sorry I havent replied sooner, was still testing this extensively as well as the new hotfix release. I think I figured out a bit better the AI Separation, though some additional feaures would be nice (for example, some AIs following the same STARs get assigned the same altitude while in real life they would be assigned 1000 below or above so as to pevent potentil conflict). I am actually using and trying all features but since I cannot seem to make AI taxi work I had to temporarily mae without the feature. The thing is if for this reason I dont want AI taxi im forced to disable custom approach (one not working with the other due to fsx limitations of AI not landing without clearance, i guess you got rid of the options to kill AI if they land without fsx clearance). Anyway with each new release I try full features, the last one is slightly better for me, limiting AI taxi speed to 10 knots as was suggested to me by toegl, but still my AI do not park where supposed, and often point their nose left to right while taxiing. If I play with one or two options to tweak this it becomes difficult to really understand what does what, any chance you can provide your customised options? Regarding IAF intercept, just for the records since I guess this won be used again, I noticed that when AI reach the last STAR waypoint at the right altitude, most of the time they will land correctly. If they are too high they will circle at east once. With latest release, even though i do have custom approach in the folder, they are not read if enhanced mode is off. Besides this, with full new version, I noticed the following: 1) Sometimes AI on jet routes get wrong altitude assignement (odd instead of even and vice versa), specially happens above FL380 or below FL290. 2) I noticed on parallel runways operations, that AI approaching a STAR for 25L for example, get put in a hold because of loss of separation (while there are no AIs ahead at all, except for the ones landing on 25R) 3) Would be nice if holding could stop when separation is regained (and not just through a decreasing timer based on number of AI. I do play with landing rates for this purpose) Some thoughts for the future of AI taxi landing and take off: -I tweaked the taxi graph to disfavor some taxiways for ai landing, I hope when AI take off comes in, the same disfavored taxiways will not apply and there will be a two-way system to tweak the taxi graph settings so that the landing taxiways are not disfavored for take off. Thank you!

Thanks I will give it a try. Roland, I still have some issues I cant seem to resolve, not necessarily about taxi but also all the previous and original options AIController was designed for. 1) The first of which is AI Separation. To me it is not working well, no matter what number I use for AI separation the results often gets compromised at big airports with many AI. In this regard, I have some questions on how your program works so as to better design my STAR a) How does the program calculate the spacing between AIs? Is it only by the exact time they will reach the last STAR waypoint? the airport? If I have many STAR, should at least one (or the last) STAR waypoint be common to all these STARs so separation works? b) Could there be a way that th program commands a different altitude for close AI. Often I have a long queue of AI separated by less than 2-3 nm and descending from the same altitude, at the same descent rate etc...not really realistic Eventually I often have finals with 3 to 4 AIs separated by only a few nm 2) I switched back to enhanced mode off a few days ago to try the STAR, and I have a lot of this issue: reaching the last STAR waypoint, AI cirle around a bit and then intercept to land, some intercepts directly, some not. I tried different setting with AI assigned altitude when exiting star=0, i modified the STAR to specify an altitude for the last waypoint, everything, but it is still very random. Trying to understand how this works. The weird hing is for the north runway this seldom happens, for the south runway, it almost always does. How to prevent this? My last STAR waypoint is distant to the IAF by a few miles. 3) I cant seem to be able ot use custom approach. Even if the files are in the right folder, it is not recognised unless enhanced mode is on (I did put 1 in the use custome final approach setting) SIDs work flawlessly Thanks for your help!

My bad indeed, I was doing it a stupid way by looking for the specific nodes coordinates and then research them into the taxi graph file. Will try your way with closing taxi link an compile from that. However, I still have lots of trouble with AI taxiing behaviour, I cant get them to stop point their noses left and right everytime (except sometimes maybe on a straight taxi line). Tweaking the 4 options that effect this behaviour is still quite difficult for me Thanks!

Thanks for this, I am currently trying this, even though it can be quite troublesome if there are many node. Do you confirm increasing from 1 to 2 (for example) actually disfavors the said node? There are actually two numbers at the end of each statement (usually 1,0), what does th 0 stand for? Testing the new beta now, and I have to issues: 1) I have a warning message about the fsuipc link, but I cant seem to get any info on this issue in the readme. I just installed the new beta on a networked computer, ASN works great so I guess the link to the server PC is ok. How can I show your program the right way to fsuipc on the server computer? 2)Is there any way you can force a take off runway when we use the force landing runway feature of AIController? Because if due to some winds I force 25L for landing, AI still use fsx 07R for take off, and that is quite conflicting^^ Thanks for your support!

Hi Roland, As always, this looks promising! Do you think it would be possible to add a feature to specify preferred routings for taxing after landing (and later on for take off), as in real life. It could be specified for example in the airport converted file, in a section after the SID or STAR, or in a new text file reserved for taxi routing (I guess the AFX file for he airport would have to be correct regarding taxi names. That would be great for some big airports with one way taxiways and so on. Likewise, it would be great if besids the jet routes file, we could have a file where we can specify which route will be used between two airport (again here there are some one way airways, preferred routes between some airport and so on), as preferred route J M W is not enough in some countries. Just my thoughts. Thanks

Hi Roland, Thanks for this new version 1.4A I am noticing while testing it that it does not take into account anymore the JET or PROP that you can add in front of the STAR or SID names. I have lots of my Jet AIs using SID or STARs for props and it is quie annoying. Hope you can fix that for next version I also have what looks like a new error warning: WAYPOINT HAS EXCEEDED range, but i am not sure whether it is bcause of my first STAR waypoint is too far. It seems that selective STAR still do not work either (I enter specific runway for my STAR, ie 25L, ad some AI still get assign to these STARs even though they do not land on this runway, specifically in this case as runways in use are 07s) Thanks!

Hi Roland and all, Aisidstar was already an excellent enhancement of our aging fsx, this new aicontroler does look promising too! I havnt had the chance to download it and tried it yet, but from what i read on this forum it seems to be a great tool in progress. Does it actually make ai fly actual airways? Where do you get the data from? Still pmdg navigraph? Looking forward to try it on Cheers

Hi Roland, Good news! What triggers these patterns? Coming from a certain anglr. Do you recomlend then to route ai towards a wpt where theu could start this pattern automatically (if realistic) On a recent flight, i noticed some ai on approach freezing to 0kiats on final. I use custom final. Do you see what coukd cause this? Thanks very much!

Hi Roland, I am reverting to you again with my question regarding the AI behaviour after it exits the last point of the star. Here in the new airport I am designing, the VOR approach makes the AI overfly the VOR on terrain 5so they overfly the airport at 4000ft) then descend on a heading before turning right to align with the runway. I am not sure it is doable with the final approach system of the program, so I wrote the approach as a prolongation of the STAR: http://www.philskies.net/library/Charts/New/RPVM.pdf See on this link the VOR rwy 04. I created two dummy waypoints for the descent to 1500 and the turn to the right to align. The thing is they do align (mos of the times with correct altitude and speed) but then circle a wpt called FS04 in FSX (which seems to be a kind of FAF here), regain some altitude, realign again and then land. It also happens sometimes to aircraft on another STAR coming in as a straight in approach. Do you have any recommendations on how to write that type of approach? (With and without using the final to see the difference. Here I dont see how they could first overfly the FSX algorythm generated IAF before commencing the approach over MCT). Thank you. Best Regards, Renaud

Hi All, Sorry I have not been able to spend too much time on this lately. However, I did test the latest version this afternoon and was pretty impressed. I am not sure if it is because it has been a long time or not bu the latest version seems to work much better that some before. The Ai Separation looked better. I did notice some weird behaviours but not as much as in the previsous versions. The one thing that surprised me at the very begining is that it took a while for the arriving aircraft to show up (using FlightSim Commander), much longer than when tester before some time ago. I also noticed one aircraft reaching the last waypoint of a STAR and go in a holding pattern (no mention of the command in the programm window) while there was no other aircraft in front . I might have missed some thing here I havent started using final approaches again yet, as even with very precise coordinates for waypoints, some behaviors were still erratic. Still, more and more wonderful program! Thank you BR

Hi Roland and everyone, Now.that the.forum is.back online, is there any news about the latest version? Ir is it already online in the library? Looking forward to it! Thanks BR

That's a good start too me! I wish I could say the same for FSX Style a mystery for me where this area is and how it is defined

Indeed, I will have to check again for the stored autogen approach. I do have the latest version but not sure to have tried it yet for a long enough time. FlyTweety, for LOWI you may try to position the Iaf if and faf fix for the approach somewhere more appropriate using ADEX. To go back to autogen approach, i still have issues once an autogen approch is recorded and stored. Many AI planes will fly the final towards the airpot flying right and left in wide.turns, doing this again on the airport ground. Am I the only one to have that? Thank youbfor your help Edited for typos du to smartphone typing

I noticed that sometimes autogen approach are saved in the autogen cached.folder in aisidstar folder. Might be a good start fir further.customization. Is it so intended Roland? However it seems that the file gets deleted once the program exits. I couldnt see the file at all times either when running the program. Couldbyou shed some liggt on this? Thank you!

Hi Roland, Sorry i havent been able to revert yet but thank you for the time spent in your replies ever since. I have continued tedting and tweaking your great program and actually started using autogen approach and design my own. Looks promising for now. One issue I had with autogen approach is the Ai plane flying right and left and right and let from glide slope intercept to touchdown. Dont know if it is a bad tweak on my side, will keep testing and look into it. I have some other remarks i would like to share for.future updates as well, will write you an email. For your question about autogen final approach speed, i did think tobhave read somewhere it was for separation purpose. Im in favor of slowing the ai from 160kias on long final to 140 before touch, although customizable speeds depending on aircraft category/type would be more realistic. Thanks for all! BR

Dear Roland, As pomised a few weeks ago, I am reverting with some feedbacks on this promising programs. First on the SIDs, as most of us it seems, reading this forum, this part goes pretty smoothly. I had some problems with some AI plane on the ground, taxing to the runway and going straight out of the taxiway instead of making the turn towards the runway. I dont think your program controls AI on the ground yet (or is it some hidden code?) so it might be my AFCAD. A nice improvement, if feasible, would be turn when reaching a certain altitude (like at 3000'MSL, right turn to next waypoint) Second, on the Stars and approaches, where most of my concerns and issues still lie (in no specific order): 1) Would it be possible, if not already the case, to have an option to put AI on hold again for a limited number of times after release from a previous hold, if needed. I had the impressions that if the AI had hold before, it could be made to hold again at every waypoint after if the program deemed necessary. Would be interested to be able to disable that as it may not be too realistic. 2) SID or STAR altitude restrictions at or above or at or below or between (I note that you wrote in the readme it is not possible, but maybe someday it would be) 3) Option to disable final appraoch controlled by the program if no specific customized approach file was made, ie not use autogen approach but default FSX. (For now I tried to let your program focus only on the STAR part and disable all autogen approach, or I think I did by specifying 0 in the parameter). 4) I noticed that AI bank and remain in same bank position when acquired in slew mode by the program the first time. Some turns left are made with a bank to the right and vice versa, which is not too esthetic when following some AI. They tend to level the wings at some point but sometimes that weird bank attitude appears again. 5) AI climbing back up towards FL500 and above (I guess this is because I dont have a registered FSUPIC, but I thought that on go around they would follow fs default go around procedure, if set in the ini file) 6) Is it possible to input in the SID or STAR file different coordiantes format in the same file. I think it does work as the readme file says what are the accepted coordinqtes format, but just in case. 7) The most important to me, as I guess it is the main source of my issues: the distance from last waypoint of star to FSX IAF. How to efficiently place one or the other: 5nm in any directions, in the flying directions of the IAF? After exiting the star exit point, does the Ai directly head towards fsx IAF or to a certain heading like I seem to rember reading somewhere here? Could you elaborate a bit more on how the transition is made when passing back the AI planes to FSX after the star exit waypoint. On that regard, I had some plane completely disappear after this last waypoint. 8) Could you by the way elaborate a bit more on this 10 sec period of time:AIIAFDetectionDelay=10 (default) 9) 2 error code or note I had when running the program: error:24 sendid 101080 index 1 cbdata 24 reset altitude constant separation I hope this is useful to you and other users, I am constantly trying to improve my ini.file and SID STAR file for RPLL, some clarification on the above would be much useful. Thanks a lot! Best regards

Dear Roland, Wonderful!! Please give me some time to digest all that and I will give you more feedback on the program and the tweaks you offered. Again, many thanks!

Hi everyone, I must say, I sign up to AVISM forum almost specifically for this post. WOW! What a great utility we have now I found out about this program a few fays ago and have been reading through the entire topic before posting this. Only one remark I dare say here, more of my opinion actually, about this in the new features you exposed for version Q: When first reading this I first was really excited, because I thought you meant the AI landing roll would actually be lengthened. From what I have been reading on forums for years now, it seems that the general consensus would be that AI have the shortest landing roll so they can vacate the runway and avoid too many go-arounds for the following landing aircrafts. However, with the growth of programs like AI Smooth and AI Separation (and now yours!), the number of go arounds at busy airports was greatly reduced. it seems to me that AI users are now looking for realistic vacating of the runways. Rather than having the plane vacating via the first exists (more often than not one in a reverse directions, or not the one intended in real life) I prefer it to continue rolling to the appropriate rapid exit taxiway (which in the ned is not only more realistic but also better for the rest of the AI flow on the ground). You can see on many forums that people seek to tweak their AI FDEs to achieve this purpose (basically lengthening the landing roll-out, increase AI taxi speed on runway, sometimes ajusting the AI approach speed). It appears to me that this new feature of AISIDSTAR would work against this tweaks. Am I right to assume that? Therefore, if this feature could be made optional/activable like some other options in your great program, I guess that would serve many users too. I am even thinking that you could maybe implement the actual complete opposite option and allow the program to extend the AI landing roll after landing. This is my remark, although I have to admit that I haven't had the time to fully test your program, so all my apologies if this is not relevant. Just an idea however. On a different note, if I may offer a suggestion for your next round of new implementations: Could it be possible that, if go arounds occur, the AI would follow the Missed Approach procedure rather than a SID? Anyway congratulations on this great utility and thank you for bringing it to our FS, it's been much needed and appreciated. Best Regards Bib974