October 26, 20223 yr Thanks for point out these two utilities. Looking forward to giving them a whirl tonight after work.
October 26, 20223 yr 1 hour ago, Shack95 said: This sounds very promising. How is performance? Not noticing any degradation, but because I have removed the AIG models I am getting less traffic. FSTL traffic is set to a moderate 56. Did a flight from KMDW to KSTL. As noted before, AI taxi and take off seem smoother. Only managed to witness a few landings. AI used all the runway at KSTL after landing but that may be due to the scenery. They did vacate the runway promptly once they reached the final turn off point, so that seems to be working. I only heard 1 traffic alert during the flight - usually I get a handful of those on this route. But again that may be due to the reduced traffic without AIG. Undercarriage lever a bit sticky was it, Sir?
October 26, 20223 yr The crash with AIG models is still happening even with all the legacy MDL models removed so it's not that, so I wonder what it is. It even crashed when using live traffic, not injected. Maybe it's the amount of traffic, at smaller airports it doesn't crash right away. Edited October 26, 20223 yr by Tuskin38
October 27, 20223 yr Did some planespotting at default KJFK between Z1300 and Z1400. Using MSFS Online Traffic to get the labels and monitoring tower comms. 31L + 31R in use. With AIFlow+AIGround ON: did not witness any go-arounds, taxiing aircraft moving steadily. No apparent performance loss. Then turned AIFlow+AIGround OFF: did not take long to see a go-around, AI getting stuck or lost on taxi (including an RPA flight making its way on to Rockaway Blvd 🙂) AIFlow+AIGround ON again: takes some time for things to stabilize, then traffic flow is improved again This is definitely getting added to my exe.xml 🙂 Undercarriage lever a bit sticky was it, Sir?
October 27, 20223 yr 9 minutes ago, Johan217 said: With AIFlow+AIGround ON: did not witness any go-arounds, taxiing aircraft moving steadily. No apparent performance loss. This seems so promising. You’re in SU10? 7950X3D | RTX 4090 | 64GB DDR5
October 27, 20223 yr SU10, indeed. Earlier at default LFLL I did get a few AI going missed (not because of traffic) using AIFlow+AIGround. But that could be an issue with the scenery. Edited October 27, 20223 yr by Johan217 Undercarriage lever a bit sticky was it, Sir?
October 27, 20223 yr I'm trying AIFlow + AIGround, with FSLTL, in SU11 Beta, and so far, so good after a couple of hours testing.... Mainly just been spotting at several USA and Canadian airports, only had time to do one take off and a very brief flight. Seeing more departures than arrivals, but ai aircraft behaviour looks a lot better, no spinning and not seen any go arounds. Departing aircraft will hold to allow an arrival - seen this at KSAN for example. I've also put AIG aircraft into the FSLTL base airplane folder and not had a CTD....yet at least. I've only moved the AIGAIM files from the airplane folder, no effects or sounds, to minimise chance of CTDs. As others have seen there can be a delay before any action once the FSLTL injector is started, although at KSAN planes started taxiing almost immediately. Edited October 27, 20223 yr by MorrisMinor
October 27, 20223 yr 10 minutes ago, MorrisMinor said: I've also put AIG aircraft into the FSLTL base airplane folder and not had a CTD....yet at least. I've only moved the AIGAIM files from the airplane folder, no effects or sounds, to minimise chance of CTDs. Which AIG aircraft are you placing in the FSLTL folder? I guess the point of this is to have models and liveries that so far are not included with FSLTL? E.g. A380s. It's an interesting idea as I'm not loading MSFS with the AIG folder nowadays (due to the long loading times). Edited October 27, 20223 yr by Cpt_Piett 7950X3D | RTX 4090 | 64GB DDR5
October 27, 20223 yr Only using FTSTL... Definite improvement. Airport operations actually seem like operations and not a circus. Not perfect though. You still get random stupidity like this (Note I'm on SU11 beta) Edit: Just watched a plane literally do a touch and go. It touched down like 200ft from the end of the runway and immediately took back off Edited October 27, 20223 yr by styckx ASUS ROG STRIX Z390-E GAMING / i9-9900k @ 4.7 all cores w/ NOCTUA NH-D15S / 2080ti / 32GB G.Skill 3200 RIPJAWS / 1TB Evo SSD / 500GB Evo SSD / 2x 3TB HDD / CORSAIR CRYSTAL 570X / IPSG 850W 80+ PLATINUM / Dual 4k Monitors
October 27, 20223 yr I agree, definitely a significant improvement. On SU10. I spent perhaps 30-40 mins at KLAX and didn’t see too much nonsensical AI behaviour. Just a couple: -One AI pushed back into another AI on the taxiway -Some AI kept flying at low altitude for a while after takeoff Other than that, AI were moving in an orderly fashion. I think I saw one go-around (another AI was still on the runway after landing). Some useful info from the official forums: Quote I used the AIFlow and AIGround apps and found that at KLAX and KLAS, the number of go-arounds was sharply reduced - not totally eliminated, but definitely reduced. I’d noticed watching LNM on my first run that the planes enroute to KLAX tended to circle and then fly east away from the airport, but the author suggested that I change these lines in the ini file to resolve that, and it worked wonders. His explanations included below: AITERMINALAREAMINSPEED=180 //slower spacing speed AITERMINALAREAMAXSPEED=250 //higher spacing speed AITERMINALAREAMINDIST=5.0 //can bump this down a little bit usually You can also usually reduce the short final distance to give the AI more distance to separate with speed changes: AITERMINALAREAMINDIST=5.0 //usually can bump this down to 5, but be careful going lower As for the holds, they can be made tighter (quicker): AITURNSCALAR=3.0 //tighter quicker holds You can also bump down arrival spacing, but there will be more incursions that slip through during heavy traffic (but could be a good compromise): AIARRIVALSPACING=2.0 Finally, you can put a hard clamp on the max number of holders per airport (e.g., to 5) for those busy periods. AIMAXHOLDING=5 I made the changes except for the last one, as I didn't quite understand the purpose. Testing at YSSY now. 7950X3D | RTX 4090 | 64GB DDR5
October 27, 20223 yr On 10/26/2022 at 12:36 PM, G550flyer said: Sounds like it. I am using AIG, so that might be an issue unless I decide to switch. use the AI Companion as recommended by the AIG group, does all these things and more, small footprint and very FPS friendly. https://www.mediafire.com/file/n8kqvifwscgvqon/AI_Companion_P3D_20220531.zip/file CPU: Core i5-6600K 4 core (3.5GHz) - overclock to 4.3 | RAM: (1066 MHz) 16GB MOBO: ASUS Z170 Pro | GeForce GTX 1070 8GB | MONITOR: 2560 X 1440 2K
October 28, 20223 yr That file says P3D, is it working in MSFS as well? Dave Current System (Running at 4k): ASUS ROG STRIX X670E-F, Ryzen 7800X3D, RTX 5090, 55" Samsung Q80T, 64GB DDR5 6000 RAM, EVGA CLC 280mm AIO Cooler, Brunner CLS-E NG Yoke, Thrustmaster Warthog HOTAS & Stick, Thrustmaster TCA Quadrant & Add-on, VirtualFly Ruddo+, TQ6+ and Yoko+, GoFlight MCP-PRO and EFIS, Skalarki FCU and MCDU
October 28, 20223 yr 1 hour ago, Mike S KPDX said: use the AI Companion as recommended by the AIG group, does all these things and more, small footprint and very FPS friendly. https://www.mediafire.com/file/n8kqvifwscgvqon/AI_Companion_P3D_20220531.zip/file Downloading some random file from MediaFire is red flag city. Let alone P3D is in the file name. I suggest no one do this. ASUS ROG STRIX Z390-E GAMING / i9-9900k @ 4.7 all cores w/ NOCTUA NH-D15S / 2080ti / 32GB G.Skill 3200 RIPJAWS / 1TB Evo SSD / 500GB Evo SSD / 2x 3TB HDD / CORSAIR CRYSTAL 570X / IPSG 850W 80+ PLATINUM / Dual 4k Monitors
October 28, 20223 yr I wonder what the FPS trade off will be if we get aircraft vacating properly allowing all landing aircraft in. Busy taxiways ! Good times. Regards, Max (YSSY) i7-12700K | Corsair Vengeance LPX 64GB 3600MHz DDR4 | Gigabyte RTX4090 24Gb | Gigabyte Z690 AORUS ELITE DDR4 | Corsair HX1200 PSU
October 28, 20223 yr 11 hours ago, Cpt_Piett said: Which AIG aircraft are you placing in the FSLTL folder? I guess the point of this is to have models and liveries that so far are not included with FSLTL? E.g. A380s. It's an interesting idea as I'm not loading MSFS with the AIG folder nowadays (due to the long loading times). At the moment I've copied all of the AIG aircraft since I wasn't sure exactly which models aren't needed. If it continues to work ok I can remove unnecessary ones later.
Archived
This topic is now archived and is closed to further replies.