Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

GSX v3.0.0 - Seated Passengers update

Featured Replies

1 hour ago, B777ER said:

Can you shut down that coualt program once your pushed back and ready to go?

You can tell GSX to disable itself when above 10,000 and going faster than 250kts

Either way coualt uses less than 50MB of memory when in the air, it's hardly noticble.

  

1 hour ago, B777ER said:

Also, is there a YT video anyone knows about on how you set it up as far removing default jetways, etc... ?

It happens automatically for default airports.

Edited by Tuskin38

  • Replies 174
  • Views 46.4k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • virtuali
    virtuali

    The usual boring technical explanation: Yes, of course, we know passengers will look dark at night but, it's not as if they are like that because of a bug or something, they are just missing some

  • virtuali
    virtuali

    You can be sure support for Seated Passengers in the PMDG will come. There are several reasons Fenix HAD to be first: Practical This was a huge release for us, and the way the system works,

  • The level of self entitlement amongst some people is amazing. FSDT release a huge free update that no doubt took a significant amount of time to produce, and instead of simply saying "thanks" some peo

  • Commercial Member

From what I know and have experienced, you need a gsx profile for the aircraft and the airport for everything to align properly. Search .to for aircraft gsx profiles and airport gsx profiles. For example, I have a profile for the pmdg 777 and a profile for flytampas Sydney. 

Forgot to ask, is there still the issue of GSX and the simobject limit in MSFS? Are people still having issues with that? for context, I only fly on Vatsim so I don't use AI planes. I only see other users that are online so if this is tied to GSX servicing AI planes, I won't have that issue. 

Edited by B777ER

Eric 

 

 

1 hour ago, B777ER said:

Forgot to ask, is there still the issue of GSX and the simobject limit in MSFS?

There was never an issue of GSX and the simobject limit.

It's the combination of multiple add-ons that reaches this limit, not GSX specifically.

 

That being said: Nothing has changed as far as I know. I have made the necesarry precautions and use AIG and GSX with reduced ground clutter. Were I to revert to the full clutter I'm sure the issue would return.

Edited by Farlis

1 hour ago, B777ER said:

Forgot to ask, is there still the issue of GSX and the simobject limit in MSFS? Are people still having issues with that? for context, I only fly on Vatsim so I don't use AI planes. I only see other users that are online so if this is tied to GSX servicing AI planes, I won't have that issue. 

Yes. Hopefully one of the 500 devs has removed this arbitrary simobject limit for MSFS2024. Though if I'm being honest, I doubt it's on their list of bugs to be addressed.

Take-offs are optional, landings are mandatory.
The only time you have too much fuel is when you're on fire.
To make a small fortune in aviation you must start with a large fortune.

There's nothing less important than the runway behind you and the altitude above you.
It's better to be on the ground wishing you were in the air, than in the air wishing you were on the ground.

In regards to Jetways not reaching the aircraft when using GSX, my understanding is this should never happen with default MSFS scenery and appropriately sized aircraft for the bay (i.e. A320 in this case). I do not use addon scenery, so I'd have 100% expected GSX and the Jetways to be working fine for YBCS and YPAD for example ... but there is a great deal of non-alignment there 😥 ... they either don't reach the aircraft or they go straight through it.

3 hours ago, B777ER said:

Forgot to ask, is there still the issue of GSX and the simobject limit in MSFS? Are people still having issues with that? for context, I only fly on Vatsim so I don't use AI planes. I only see other users that are online so if this is tied to GSX servicing AI planes, I won't have that issue. 

To reduce the chance, you can disable ground clutter in the GSX options. I haven't hit the limit ever since that option was added.

Edited by Tuskin38

  • Author
  • Commercial Member
1 hour ago, Captain_K said:

In regards to Jetways not reaching the aircraft when using GSX, my understanding is this should never happen with default MSFS scenery and appropriately sized aircraft for the bay (i.e. A320 in this case). I do not use addon scenery, so I'd have 100% expected GSX and the Jetways to be working fine for YBCS and YPAD for example ... but there is a great deal of non-alignment there 😥 ... they either don't reach the aircraft or they go straight through it.

Assuming you are referring to the GSX replacement jetways on default airports, which are the only airports you are supposed to used GSX replacement jetways (with "default" meaning really default, NOT Handcrafted/Premium airports: these *cannot* use GSX replacement jetways), a possible reason why you'll find the default jetways to "work better", is because they have been modeled using unrealistic too forgiving constraints, the jetway head is allowed to bank, something a real jetway head will never do. Also, they use 5 coaxial sections, when in real life they usually have 2-3 sections with different sizes.

The GSX replacement jetways, even if they have the same measurements and are placed in the same position as they ones from the default scenery, have more realistic constraints and are modeled over more real life jetways, which means they look more accurate, but they might have more issue connecting, because they respect realistic constraints, they never bank for example.

You might be able to improve this by setting a Custom Stop position in GSX, which is what custom Airport profiles do, but the main problem is, not many do and share profiles for default airports, because they have so many other issues, that most creators don't find worthwhile to make profiles for default airports.

And of course, you are not forced to use GSX replacement jetways, since you can disable them, either individually by airport, or entirely.

Edited by virtuali

Thanks - good suggestion. I tried disabling the GSX Jetways ... but no change to the outcome unfortunately (Jetways don't reach at YBCS, and go through the middle of the aircraft at YPAD). I also noticed an additional issue at YPAD ... where I was parked at Gate 26 and when I operated the Jetway, the one next door moved (Gate 25 I think???).

  • Author
  • Commercial Member
On 7/8/2024 at 2:11 PM, Captain_K said:

I tried disabling the GSX Jetways ... but no change to the outcome unfortunately

Then you now are sure it's nothing related to GSX.

 

On 7/8/2024 at 2:11 PM, Captain_K said:

where I was parked at Gate 26 and when I operated the Jetway, the one next door moved (Gate 25 I think???).

Yes, this happens, the default jetway animation system in MSFS is quite limited, jetway treat all airplane doors equally, so they'll dock to the first one solving, if you place the airplane forward enough, they'll dock on the rear door, and sometimes they even dock on the service door with the head reversed.

Or, they don't dock at all, or dock from the wrong parking.

Again, nothing to do with GSX, which just sends a single Trigger command to operate the jetway, the rest is done entirely by the sim.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.