GSX Pro Short-term Roadmap: what to expect in the next updates.

[WebMaximus]

Coming back to this one now when SU4 has been released and I still seem to have a huge performance hit when enabling seated passengers. It was mentioned above how that problem was supposed to be fixed in SU4?

[virtuali]

As already explained in other posts, the big performance hit happened from SU2 (zero impact) to SU3 (big impact), SU4 has IMPROVED compared to SU3, but it's not at the same level at it was with SU2.

Nothing we can do from our side, of course, the only thing that changed was the simulator, and we are already using the most 2024 native way to attach objects to another object, in MSFS 2024, IF the airplane is a native MSFS 2024 airplane.

[WebMaximus]

The iFly 737 MAX8 which I fly isn't native MSFS2024 which could explain the drop in performance with seated PAX enabled.

[virtuali]

The iFly 737 MAX8 which I fly isn't native MSFS2024 which could explain the drop in performance with seated PAX enabled.

The iFly is a special case (I think I already explained this to you, several times), that requires attaching passengers both on the interior and the exterior, which is the only way to have them working and not causing other visual side effects which happened when we didn't use this method.

As I've said, this worked fine until SU2, because in SU2 the sim was capable to effectively completely optimize attached objects not passing a visibility test, it got MUCH worse in SU3 (with any airplane), then it went to acceptable (but still not zero impact) with SU4. However, whatever residual impact of invisible objects is left in SU4, it would be duplicated in the iFly because the way it's made.

It MIGHT be improved if an eventual MSFS 2024 native version of the airplane will come out, either because the sim is more optimized when using the native attachment method we already use for all the other native 2024 airplanes OR because the new version might not require a double attachment on both exterior and interior models.

[WebMaximus]

Yep, I know

[TorbenJA]

I've allready expressed this suggestion on the backdoor forum, however never got an answer (guess we're all busy).

"I understand that GSX supports the use of wheel chocks for planes, which comes with them from the manufacturer.

Would it be possible to have GSX have their own wheel chocks?

When loading the cold and dark plane, it could be with chocks in position and so I could call for airbridge or stars, so I can come into the cockpit. In Prosim using specific hardware, I can't set the parking brake unless hydralic system 2 in powered (which I can't as I can not get into the cockpit etc.).
If it was a feature in GSX the all planes (not only specific 3rd party planes) could get a more realistic handling, which is all GSX is about.
Upon arrival at an airport stand the setting of the parking brake could the trigger GSX to apply chocks and the usual services could continue.

Just an idea."

I do not know if this is feasible, but I guess that the contact points between (main)wheels and ground can be read - or you can mad a pair of chocs, which can be addapted to a plane much the same way a door height can be adjusted. It would naturally take some effort to change the logic of GSX to suit such a change. But IRL the plane doesn't have the parking brake set, when on stand for several reasons - e.g. brake cooling.

Would love your comment on such an idea -

regards
Torben

[ScaryDuck3]

Hello Umberto,

Hues ZCore was updated recently to include compatibility with GSX seated passengers. They have a compatibility mod that allowed for the inibuilds a350 cabin packs (like the Qatar QSuites) to be used again. If I recall correctly, GSX seated passengers did have configurations for the a350 cabin packs variants but maybe they were removed with a recent update? Would it be possible return those seat configurations to the FSDT installer so that we may see seated passengers again in those cabins?

Thank you and happy new year.

[virtuali]

If I recall correctly, GSX seated passengers did have configurations for the a350 cabin packs variants but maybe they were removed with a recent update? Would it be possible return those seat configurations to the FSDT installer so that we may see seated passengers again in those cabins?

Nothing changed in the A350 support, it will still be detected (or not), depending how the package name is named according to the normal package naming rules discussed in the manual at Page 99.