Tried parking at most of the gates and the nose of the plane is inside the building. I even installed the GSX profiles and made sure to update GSX Pro as well but still having those issues. Anyone else having the same problem?

I'm guessing it just isn't built for a aircraft using L2 as the main door.

Same thing happened to me a FT's Sydney.

Similar things happen with Headwind's A330

Edited June 26, 20241 yr by Tuskin38

So the problem is using the wrong (farther back) door?

should the simulated airport have enough room for the simulated aircraft, if both are size compatible in real life? (And the right stand is used)

I was able to park at United gate G9 with no issues.

1 hour ago, Merawen said:

So the problem is using the wrong (farther back) door?

should the simulated airport have enough room for the simulated aircraft, if both are size compatible in real life? (And the right stand is used)

I imagine since the sim only supports single jetways, most airports are built with L1 on shorter aircraft in mind.

GSX also positions the aircraft based off the primary door location relative to the jetway I think? If the profile maker hasn't set a custom stop point for the aircraft type.

Edited June 26, 20241 yr by Tuskin38

So is this a GSX or Flightbeam issue?

Yeah I’ve had to edit the stop point using the airport editor in GSX to get the parking right. Not sure how that’s going to effect other aircraft types tho!

9 hours ago, Tuskin38 said:

GSX also positions the aircraft based off the primary door location relative to the jetway I think? If the profile maker hasn't set a custom stop point for the aircraft type.

Not exactly. GSX position is based on the Preferred Exit, which it's usually L1, especially considering we didn't had much of long haulers before, but the chapter in the manual named Understanding the Stop Position, at Page 48, and especially the diagram in the following page, explains quit clearly how this works.

However, if the issue is the airplane is too far ahead, so it would end up inside a building, seems to indicate Stop positions hasn't been set, because for all of that to work properly, a custom Stop position must have been set for each gate, using any airplane (doesn't matter which one), since what GSX will do, is to position the airplane so the Preferred Exit of the airplane *you* are using, would end up in the same place as the Preferred Exit of the airplane used to customize the Stop position.

That's even without considering a GSX airport profile can even use custom Stop positions for different airplane models, in case the above strategy of "aligning the Preferred Exits" doesn't work in some particular spots.

 

Thanks for the explanation 

So we have to fix this ourselves for every single airport and at each gate? I really wish it would just work out of the box. Especially for those who own a lot of 3rd party airports. Having to go in to every single gate and configure the right position would take a really long time.

1 hour ago, captain420 said:

So we have to fix this ourselves for every single airport and at each gate? I really wish it would just work out of the box. Especially for those who own a lot of 3rd party airports. Having to go in to every single gate and configure the right position would take a really long time.

That's why other peope do it for us lazy slobs and upload their work on Flightsim.to. 😉

If you join the flightbeam discord, There is a WIP progress GSX file with all of these issues fixed.

 

Is there a simple way to find out which airports gsx files hasn’t stop positions? Like a grep on the files in the gsx profile folder?

43 minutes ago, Mroberts95 said:

If you join the flightbeam discord, There is a WIP progress GSX file with all of these issues fixed.

 

would it be possible for you or someone to share that file here with the rest of us?