G-YMML1

Fenix A320SL. Truck is OFF again, passenger boarding stopped at 108 out of 168, Horrible!

Okey, fuel truck finally works as it should with both types, however passengers' loading always stops at 65-80% level. Each time I have to reset GSX and load a plane manually. Happens with both a bus and a jetway.

Idk. Everything worked perfectly through 3.9.1 for years!!!

329 and 321

The latest set of the updates is a total mess. With Fenix I have a fuel truck standing near the wing again (not under) and boarding of passengers from the bus stopped at 60%. Feel myself like I'm a beta tester.

Yes. I tried SFO again yesterday and it was fine in terms of traffic volume.

KSFO 22Z yesterday. 11 planes line for 28L departure in my sim. I use AIG exclusively. KSFO is one of the best-behaved airports from PSXT/RT standpoint.

1. Always use EFB to update Navdata. Avoid the Hub. It's good for Fenix, iFLy, FSL, Active Sky. 2. DO NOT import Simbrief created flightplans via FMC RTE import. Type it into FMC manually (I know it's a pain, but...) 3. Make sure you have identical Navdata for both sim and PMDG birds (all of them) There is a possible issue with converting SB flighplans into PMDG format. It's very difficult to say, who's to blame in this instance, PMDG or Navigraph, but since beginning of March forums have exploded with PMDG WASM complaints. PMDG marketing guru insists that WASM probability correlates with a number of add-ones you have installed, which is total BS, as you may understand. Anyway, entering FP manually and updating navdata via EFB only, keep me away from WASM crashes (knock on the wood)

No chance. FSHUD or any other ATC software, such as SI or BATC, cannot control PSXT traffic. However, SI can see AI planes injected by PSXT and report them either on a taxiway or for TCAS purposes.

My local provider announced recently that due to replacement of equipment, short outages are possible for a month during evening times (Duhhh!!!!). Yesterday, I encountered of these outages. Though it lasted 10 minutes, my entire flight was ruined during the approach. I tried to switch quickly to my phone internet, but then the sim hangs. Is there any way to protect from these type of "outages"?

You can do that for sure, but you'd need to disable FSHUD traffic injector. I'm using SayIntentions as ATC (its AI injector is being disabled) + PSXT traffic. So far, so good, as SI provides a plethora of flexibility.

No issues on my side. Testing GSP KLAS, works as intended.

3.9.3 fixed the fuel truck issue. Umberto - thank you!

Umberto in his best - always disappearing in the moments like this, even from his own forum 🙂 instead of simply stating - "Yeah, there is an issue, a fix is on a way". I bet that patch will follow soon, the issue will be fixed, and it will be like "there never was an issue" supported by multiple paragraphs of blah-blah-blah.

Yes, he did. The height adjustment does not affect the truck positioning in 3.9.2, I posted a request to investigate on their forums. Other users confirmed the issue. Hopefully it will be resolved.

It had been perfectly positioned all these years with Fenix and PMDG until yesterday. Hence, I'm not asking for impossible things.

Fuel Truck behavior is totally wrecked for PMDG. The height should be increased to minimum 3.65 and even after that the truck does not stand under the wing.

Old version of PSXT had "exception radius" parameter to deal with problems such as above, I don't know whether it's still here.

To be specific- those crashes started at the end of February. It was faulty 2603 update from Navigraph which they fixed 3 times. I’m wondering if it has any relations. For now, in the PMDG world I’m entering FP into FMC manually. So far, so good, but who knows

Which is the most VRAM hog now, new 737-700 or FSL Bus NEO?

It's been done zillion times by many users, still - Mr. Kok insists that WASM crash depends on a number of add-ones installed. Funny, but I have had 75 sceneries installed, Fenix, FSL, PMDG, and it's only PMDG that started to wasm only recently. My first WASM ever for the entire duration of 2020/2024 experience. Even FSL after the most recent patch works well.

I'm curious if we, 2k users, should start worrying about VRAM.

There are suspicions that FMC import of Simbrief flightplans has issues and causes WASM crashes. The safe procedure is following for now. 1. Update Navdata for both MSFS2024 via Navigraph updater and PMDG via EFB. 2. Create FP in Simbrief. 3. You may import FP via EFB for reference, but DO NOT import it via RTE page in FMC - enter it manually into FMC instead. Since then I have had 4 WASM free flights with 738/8/777. Again, it's just theory, Mr. Kok is totally reluctant to communicate on this issue.

Do you import your simbrief flight plan via FMC or enter it manually? Does Navigraph navdata in sim matches PMDg navdata?

Keep in mind that after deleting WASM in the PMDG folder, you would need to correct all the settings via FMC/EFB. By default, the sim rate is set to AUTO. You need to switch it to DIRECT CONTROL.