3catcircus

This. There shouldn't by any overlapping. Lots of comms at large airports, but no overlapping. I wonder if the radio stack control option being turned on would fix this by turning down VHF2 volume?

While this is true, it seems the latest release (non experimental) has broken vectoring. Stock MSFS2024 KLAX, on the ORCKA5 SID. BATC, after passing the first fix, it kept vectoring me so I was orbiting KLIPPR. Finally just did a lost comms procedure to get myself to the waypoint and on my way. Successive controllers kept trying to vector me in circles until I was handed off to the Center controller who cleared me up to my cruise altitude.

So, If I'm using GSX, BATC, with AIG and FSLTL models, how does it all play together? Any conflicts since BATC can move jetways for AI aircraft? Any collisions between the traffic and that placed by GSX?

Had an interesting thing happen last night. KLAX - EGLL, fairly heavy, parked at gate 41 at stock KLAX. GSX and BATC. Pushback was a little funky in that it pulled back forward towards the gate for a second or two before continuing and it did some side to side movement before finishing the pushback. Upon disconnecting the tug, the aircraft tipped over so that the right engine was touching the ground. Reset flight and tried a second time. Second time, the aircraft overlapped a BATC generated aircraft at the same gate and pushback resulted in the same behavior. Third try was at gate 43. Different style tug and pushback still did the pull and push but then pushback completed normally. Any ideas?

Your first post stated "I'm currently at iniBuilds VHHH using the iniBuilds A350." 🤷

It's on the EFB in the Ground tab. Here's the screenshot

Have you turned off the rear stairs when jetways are available? Then have you called the jetways from within the A350 EFB with the GSX Integration button turned on?

It isn't actually that hard to start the engines. Engine order is 3, 4, 2, 1. The FE will line up the fuel tanks, APU, and call out the completion of the pre-start flow. Engine start switch (on the overhead panel) to ground. At 15% N2, fuel control/start lever to start. At 40% N2, check that the engine start switch snaps back to cutout. At 50% N2, fuel control/start lever to idle. Repeat for engines 4, 2, 1.

My experience has been that both FSLTL and AIG are smooth using BATC's injection. I've not tried FSLTL's injector. But, I'm using Gigabit Ethernet (702 Mbps download speeds while the kids are also typically streaming Netflix or Hulu on two devices at the same time) and I generally wait more than a few minutes before looking at any traffic since I always start cold and dark and am focused inside on bringing on power, aligning nav, etc.

I've got a Navigraph Ultimate. Using AIG and FSLTL models with BATC. Smooth as butter.

I don't need fancy addon airports for the most part - many of them are solid. I only purchased payware KPHL and KBOS because I'm so familiar with the real airports. Addon aircraft, in the other hand... I don't need pretty visuals with every single wiring harness in the wheel wells modeled, but as long as the systems at least appear to act correctly, I'm good. It doesn't even need to be so detailed that the circuit breakers for the galley coffee maker are modeled - just that the FMS and autopilot function and that the handling feels right.

BATC isn't yet great for VFR, but for IFR on a STAR, it's been pretty solid for me - I hadn't even recently needed to tell it I'm ready for descent - was on an approach to LSGG and it gave me descent instructions about 30 seconds before I was going to tell it I was ready to begin the descent. It then gave me vectors with various off-plan speeds and it worked like a champ - intercepted the LOC/GS perfectly.

Yes - to all except the amount of VRAM - but I'm using an Intel ARC A770 with 16GB which seems, per consensus, to be not as great a performer as an Nvidia or AMD. I've got both FSLTL and AIG traffic, GSX, and BATC running. The A220 served to be just fine performance-wise for me - but I only use the lower res terrain server maps. What I generally have to do, regardless of which aircraft (PMDG, iniBuilds, iFly, Fenix) I use, is to wait. 6+ minutes to load to the start screen. 2-3 minutes from clicking the button to begin the flight until the Ready to Fly button And then once I get the Ready to Fly button, I'm waiting 2-3 minutes for the world to spawn in full detail before I hit that button. Not waiting results in stutters, faults, and errors. I can't say for certain since everyone's rig is different, but I've only ever had issues when I've downloaded rather than streamed.

Yes - to all except the amount of VRAM - but I'm using an Intel ARC A770 with 16GB which seems, per consensus, to be not as great a performer as an Nvidia or AMD. I've got both FSLTL and AIG traffic, GSX, and BATC running. The A220 served to be just fine performance-wise for me - but I only use the lower res terrain server maps. What I generally have to do, regardless of which aircraft (PMDG, iniBuilds, iFly, Fenix) I use, is to wait. 6+ minutes to load to the start screen. 2-3 minutes from clicking the button to begin the flight until the Ready to Fly button And then once I get the Ready to Fly button, I'm waiting 2-3 minutes for the world to spawn in full detail before I hit that button. Not waiting results in stutters, faults, and errors. I can't say for certain since everyone's rig is different, but I've only ever had issues when I've downloaded rather than streamed.

Just played around with my first flight in this bird. Really really liking it. If you have GSX, a profile is a must. So far the only issue is that when I pan views, there are trim wheel sounds (but no actual train wheel movement).