FlyTweety

Yes

I already installed the voice control version (but not used it) . Is a next to next installation possible and maybe a simple switch between both versions? Or have i to uninstall the voice control first (or during the installation process)?

Do you think, this limitation is still valid for P3D? As far as i know LM has changed and expanded a lot in the new SDK, maybe by chance you have more possibilities there? Unfortunatly i´m still to "stupid" to read the SDK, i only follow the statements from LM.

One single question: Do you have control about the landing gear during take off? I noticed as i tried to set up "realistic" prucedures for TNCM (St. Maarten) that i need to handover the control to AISIDSTAR very early (at the latest 300ft over ground). But, doing this that means that the Aircrafts don´t have the time to fully retract the landing gear. Smaller Ai´s slightly better, the KLM 747 continues the climb with landing gear 3/4 outside. Not a showstopper, but it is looking strange though :rolleyes: .

Well, after a couple of hours in EDDF i´m still unsure :mellow: No doubt, the assign of the STARs regarding the Wind direction now works great. Not perfect is, that it now happens that the AI follow e.g. a STAR dedicated to the RWY 07L and finally the ATC assign the RWY 07R. That´s not perfect because obviously this swing overs crack the separation because the final is short. What me really leave desperated is the fact, that it seems to be impossible to "trust" the ATC. I wrote long spreadsheets of where P3D asssign the Runway (IAF). Now you can think, it is simple to "optimize" the STARS and let each AI pass this Area. At the certain day i noticed, that all Traffic of a certain STAR receive their Runway between Fix DF439 and DF444. Great. Now you go to work 5 days and start the sim again one week later. What happens? From 10 Aircrafts only 3-4 get the Runway in the usual area, 6-7 NOT :angry: . And you know what happens when you have a "sixpack" of Airliners entering the Final without clearance <_< . Looking at the ATC window show tons of messages like "25 expedite your climb to 12,000 ft", "1048 expedite your climb to 15,000 ft" It´s all the traffic that was failed to assign the runway while the AI in front at the same track did. I think, as long as the fu...g built in ATC will not be replaced by a more smarter your tool will have a hard stand. But also with assigned Runway it happend often, that the AI turned back at short final. First it had a STAR and a Runway, after leaving the last STAR WP the Runway was left. After passing the first one or two Final WP the AI turned and the Runway wasn´t shown at the monitor as well. So the AI was wandering arround. This happend randomly for about 15-20% of the landing Aircrafts.

First observation: Basically now the assigned runway fits to the STAR (and vice versa) Now frequently a message appears: EXEPTION = 20 = "six digit number" index = 1chData = 24 Also, the seperation is kept less. Testground is now EDDF included the "new" Runway. But i definitly need more time to "play"

I will check it out, but compared to January/February i have much less time because i´m back in my Job. So it might take a few days.

Good to know :smile:

As described earlier, i start AISIDSTAR at the earliest when the conditions are stable. The first 2-3 Aircrafts taxi out to RWY 23L, my Laptop with FSC 9.2 shows matching wind direction, all good. Then i start the AISIDSTAR Monitor, from there i start the tool itself. After the startup you read in the Traffic, i start the Data collection, and from the first second i notice a 50:50 allocation between 05R and 23L regarding the STARs. And, as described, this continued yesterday for more than half an hour. At no time one AC was taxiing or departing from 05R. I wonder, why you don´t use your readout of the Data collection to verify the plausability of the STAR? There is a existing telemetry file that says, 23L is assigned for each and every taxi out from EDDL. Isn´t it possible to take that file to read e.g. every 10 seconds the landing runway and if the assigned STAR isn´t matching, you reassingn? Also strange, the new version seems to produce more "breakouts" than before. Traffic that is just feets away from the first Final Waypoint and switches to the "enroute" mode turns 180° to catch the IAF again. This happens randomly, from a complete chain of 5 AC using the same (correct) STAR and with a valid assigned Runway 2-3 do not enter the Final but turning arround. I´ve no clue why.

Copy that. On my testground EDDL still 30-50% receive the wrong STARs, not only at startup but also after 30 minutes uptime. No runway change at this time, all aircrafts departing at the same (odd directed) runway.

I wouldn´t die for it but i am sure, that the first part is without any acceleration, means 1x. Will confirm it tomorrow after trying the same flight again. You are right, this is right in the IAF area. But apart from LOWI i experienced that behavior (Rattlesnake"walk") at many places as soon as the AI is assigned to the "Final" File. Would be great to have this additional parameter, this would wipe out some of the "unrealistic" flight patterns where we don´t really need them. Take LOWI again into account, here we need first the AITurnScalar (i used 1.4 for the "normal" STAR) to be able to turn 180° in the tight Valley (soft mode), even later the "hot" mode to enter the short final (no further turns needed). Otherwise, with the default setting, the Valley is to tight!

Basically like a Kameleon: Right eye at my Notebook, where FSC runs. You might see the AI meander left and right about 10° The left eye on the main screen where i follow the AI from anywhere by using large zoom settings. There i can see that FSC is WYSIWYG (What you see is what you get) The only thing that is different are the stutters, this is related to the slow hardware of my Laptop and the CPU consuption during recording (single core). In the Sim the AI really looks like a snake... By the way, in the second half you can see what happens to me with 4x speed

*sigh* OK, you say, it works for you, my opinion is, it don´t. Maybe i´m to German, expect to much perfection. I tried your procedures, though you use different waypoints, the behaviour is quit the same: After leaving the STAR and entering the Final the AI switch to the Approach Mode, means e.g., it flys all the way with extended landing gear. Further is begins to react like complained, 90° turns within a circle of 100 ft, barely able to fly straight but allways meanderings within 10° left/right. By the way, time warp 4x let your control totally collapse in this mode, the AI is turning unpredictable on its way to the next WP. So you might be right when you be convinced "it works" if AIsidstar bring the AI down to the Runway somehow, but to me it is not comparable to "normal" Approaches. Therefore if have again some questions to understand the tool better. 1. What is the trigger for a successful handover from the last STAR WP to the call of the FINAL Approach? Why did it not work for me to use the STAR to pass the P3d IAF, earn the Runway assignement, continue the STAR down to the short final in RWY direction? The only what had to happen is, that at the end of the STAR, (which provides me the smooth 2 min. turns) it need the switch to the FINAL file. In my opinion all desires are fullfilled: IAF passed, Runway assigned, Runway and first WP of the Final close straight ahead. 2. WHAT is controlling the AI attitude during the Final Mode? Is it part of the .air file or has AISIDSTAR the full control at this time? Would it be possible to add triggers into the program to enable us to change the assigned algorythms depending to the waypoint. So that the very fine control e.g. starts at or below 2000 ft AGL? Like <attitude>NORMAL</attitude> <attitude>FINE</attitude> 3. HOW do you really read the Runway direction? You told me before, that you first start your sim with customized weather to be sure that all the traffic has the same wind. I tried it again and again. Start the sim, switch off OPUS, choose EDDL as the desired Airport, change the time, customize wind to 230° 16 kts change the Aircraft to BOB. Then i open the flight and move in a position where i can observe the Traffic. At my networked Notebook i let run FSC 9.5, GPS connected. I can read in the upper left corner windspeed and direction, 16 kts 230°, like selected. 100% of the Ground Traffic is taxiing to the Runway 23(L) THEN i start the AISIDSTAR Monitor.exe , from there i start AISIDSTAR. At this time the sim is running about 2 minutes. The Monitor Window shows all "taxi out" Traffic to RWY 23L, and guess what? Out of 10 incoming Traffic AI´s 3 to 7 will equipped with STAR Files for RWY 05. At no time the Wind has changed for more then 5 milliseconds, you know, it is fixed in the setting and i can read it all the time. So, what is wrong? Also, as mentioned, it don´t turn better, after one hour ore more it seems to turn even worse with less than 30% correct STAR´s. What can i offer to you that you see that i don´t cheat? Regarding to your depression about using your Tool preferred for the "extreme" Airports: What did you expect? Simple Approaches working satisfiing anyway. OF COURSE we use Aisidstar to crush the limits. circling Approaches, visuals with changing headings, steep Approaches. And yes, to keep the separation. We really need it not at simple Hillbilly Airports with one Runway, no obstacles arround and one flight per hour.. The fun is to create working Aprroaches under circumstances where FSX/P3d fails. It is no alternative to delete AI before taxiing in, if i don´t want to see that i can allready free the Approach way earlier with FSUIPC. And if i want it simple, why using decent AI at all? We could use cubes instead of frameeating Models. Big red cube for Heavys, midrange yellow cube for narrowbodys, small green for Buisness and GA. FSX does´t care about the shape, it will "fly" anyway related to the config, but with far better FPS... You should surrender, the main reason is that we are childish and want to watch traffic as spotters or love to tinker like the guys with their model railway...

For LOWi basically this is easy: You need a second program like Flightsim Commander that shows you all the traffic. Without AISIDSTAR running you open the ATC Window and watch/listen where the ATC assign the Runway to the AI. Finaly you add a Waypoint (or use a existing) in this area and add it at first to the STAR´s. The problem is that is looks stupid regarding traffic that is is injected in the odd corner. The AI appears east from RTT, flys direct to the clearance area southwest of the Airport, then all the way back to RTT and starts his "visual" approach. But i didn´t found another way to be sure that i have a valid assignement :(

I tried it, but without success. Though i changed some Waypoins (one per test of course) from type "Named" to "IAF" and "FAF", P3d doesn´t care about it. I could find the area, where i get the runway assignement for sure, but that was it. The rest is in god´s (ah, P3d´s) hands.