I still don’t get what i do wrong. I have a couple of a320 liveries installed. Load and update GSX Pro, uncheck and check the A320 box. But i still don’t see passengers sitting in the plane. The come in, walk to their seats and disappear. What am i doing wrong?
3rd party or from Fenix Livery Manager? They need to be installed in a certain folder structure and files names. Old liveries from Flightsim.to don’t follow this rule and you need to rename the folders.
1 Like
Is this the Fenix? You seem to have to do the check/uncheck and then ‘close’ in the FSDT installer GSX config after every change so that can include changes such as a new livery install.
If 3rd party livery outside of installer then what @Marklar666 says.
1 Like
Mostly 3th party. I guess that is the issue then, didnt know that tbh. I only thought that was for the announcement sounds… i’ll try to find that and try tomorrow…don’t want to mess up my flight i am on now 
Thanks
purple inside
I suggest checking the manual, Page 98, there’s a chapter named Seated Passengers disappearing when they sit which lists all the possible reasons why it happens.
1 Like
Version 3.1.8 – September 27th, 2024
GSX (all versions) NEW: Option to connect Pushback tug during Boarding, saving time on Departure. The option will show as an additional menu request, which defaults to “No” if no choice is made within a few seconds. A new option in the settings “Connect Pushback on Boarding” will Skip the request menu, always assuming a “Yes” reply.
GSX Pro restarter: The Couatl auto-restarter will now only give back focus to Flightsimulator.exe if it was in focus before a restart was required.
The new early Pushback connect option was currently the most voted feature in the GSX Discord channel.
19 Likes
I love the way GSX devs are so responsive to user suggestions, that early connect tug will be awesome! Thank you.
2 Likes
Great work @Umberto67! Love this extra realism, thank you!! Here in the US we almost always connect the tug during boarding. If you wanted to take it even further, you can connect the towbar to the plane during boarding and then connect the tug to the towbar just after boarding.
@Umberto67 I’ve had a 4K monitor for a couple of months now and I’ve noticed that the FSDT Installer application isn’t all that sharp.
Is it possible to improve the quality? It’s a minor detail and doesn’t affect the software’s performance at all, of course, but it would be nice.
The most recent update seems to have introduced a regression or bug - after requesting boarding, when GSX asks if the tug should connect, if you click YES, you get the dialog from the full “Ready for pushback” text replies back from GSX, but that prevents GSX from loading the passenger and payload values for the PMDG 777, which are left at whatever defaults are set in the load-in panel state. I have not yet checked to see if the same bug occurs with the PMDG 737 lineup.
If you click NO at the prompt to connect the tug, pax and payload entries are made by GSX as expected.
More improvements for this new feature.
- The sounds no longer make sense. “ready for pushback” and “departure checks completed” sound silly with a jetway connected and passengers just starting to board.
- I find the pushback gets stuck where it needs to know the direction but hasn’t asked. I need to go into “continue pushback” manually and select the direction otherwise it just does nothing. I have not closed the GSX menu with the toolbar, I use a keybind on my joystick, so it should just pop up when needed like normal.
Fenix for me. I use the Fenix GSX option for boarding but select pushback from the GSX menu as turning on the beacon light to request pushback is just wrong.
I cannot replicate this. After you press YES to the request to move the tug early, there are two possible outcomes:
-
If you have the “Ignore crew boarding” option enabled in the settings, the menu will close and the Simbrief values will be inserted in the 777 CDU.
-
If you have the “Ignore crew boarding” option disabled in the settings, you will first see a menu asking if you want to board pilots/crew, and the Simbrief values will be inserted only after this extra menu closes.
I tried with both options, it works like this.
I have this option set, but GSX did NOT enter any values in the CDU after I accepted the request to connect the tug. I had my cockpit camera facing all three of the 777 CDUs and nothing was entered in any of them, nor was I making any inputs - I was specifically waiting for GSX to enter the values before continuing my pre-flight, which I had paused before doing PERF INIT, as that step requires the ZFW for the flight to have been entered and correct.
Prior to the most recent update, I simply wait a couple moments for GSX to enter the pax and cargo weights for the resulting ZFW, the when I see it’s done, I continue with PERF INIT. That did NOT happen yesterday during my tests.
I have a long-haul planned today so I will check again when I fly that route.
I can only confirm I couldn’t replicate the problem with either options.
Version 3.1.9 – September 30th, 2024
GSX (all versions) Fix: When choosing the option to connect the Tug early and the tug has a Towbar, the airplane won’t be frozen on Boarding but only later during Departure.
GSX (all versions) Fix: Fuel Truck not arriving on gates with Jetways, if called after Boarding, with airplanes where the refueling point is under the Left wing.
GSX (all versions) Fix: Unicode error with some liveries.
GSX (all versions) Fix: XML Expression for Conditional Embedded stairs not visible in the Airplane configuration editor.
GSX (all versions) Fix: Error if “Connect tug when boarding” is checked in menu and stand has no pushback.
GSX (all versions) Fix: Unicode error with some liveries.
GSX (all versions) Fix: Memory leak if logging is enabled and a VGDS gate is not closed in time after departure.
I’m sorry if this version is mostly bugfixes but, stability is as important (if not more) as new features. Next week we’ll have something new to look at, promise.
11 Likes
Thanks! Also, please do something about the download URLs being classified suspect by a host of anti virus programs and firewalls. It is only a matter of time before it becomes rampant and starts affecting a large number of people.
This started with 3.1.7 update - did you make any changes to your cloud infra just before that release?
We haven’t made any changes except updating the Couatl64_MSFS.EXE file which hasn’t been updated since a couple of months. We had to update it to fix a small issue which caused vehicles making a small stuttering while reversing their movement, but that’s not really the point: we should be able to update the software if we need.
And this is the main source of the problem, in order to advertise being able to catch threats “before they are discovered”, some antivirus use questionable heuristic behavioral patterns and in some cases even less reliable “reputation scores”. This last is particularly bad, because it would basically prevents updates, since everything new is at risk of being classified as dangerous “just” because it’s new, so it doesn’t have enough reputation score (it’s new…).
When dealing with false positives, the usual suggestion to prevent those, is to use Digital Signatures, namely the Authenticode signature from Microsoft (which we pay hundreds$/year just to keep it current and it has raised in price 3x in the last years) but on top of that, we have a 2nd Digital Signature called “Software Taggant”, which is an IEEE standard that antivirus vendors are supposed to use to help their software differentiate between real threats and false positives. We have both, of course.
The problem is, some antivirus vendors decided to trust their own heuristic more than these industry standards, and the result is you have an antivirus that catches more false positives than it should.
The only recurse we have, is to REPORT these to the antivirus vendors, but we can’t do it without help from users. If we don’t know which antivirus was at fault, we can’t report it.
Many routers (Asus, and others) use security software from Trend Micro and of course, as soon as we got a report from an affected user, we filed a reclassification complaint with Trend Micro and of course, a few hours after we reported it, Trend Micro reclassified the affected URL as Safe
This should cover a lot of routers but, again, if there are other routers around using different software or blocking different URLs, we can’t report if we don’t know about it.
3 Likes
Thanks for explaining it Umberto. I agree, heuristic matching in the world of s/w is not really encouraged due to the false positives/negatives it can potentially generate.
Is anyone getting constant warning “You need to set Parking Brakes or Wheel Chocks to request ground services” when starting in PMDG 737? This plane spawns with chocks by default so why this warning? I even enabled parking brakes in startup cockpit state, so it spawns with both brakes and chocks. I am still getting this annoying warning.
I’m getting these with the PMDG 777 however I noticed the parking brakes are not set because of the PMDG 777 is not keeping the LOAD STATE at cold & dark and cold & dark gpu.