Request for an option to disable PMDG integration in GSX Pro

[Davide]

Dear GSX Pro Development Team,

First of all, I would like to express my gratitude for the outstanding features GSX Pro brings to the MSFS experience. Your continuous efforts in enhancing realism and functionality are highly appreciated.

I am writing to request the addition of an option to disable GSX integration with PMDG aircrafts (the 737-800 in my case). While the current integration works flawlessly, I would prefer to have the ability to turn it off due to personal preferences.

The ideal solution, from my perspective, would be a simple checkbox in the GSX options that disables this integration. My reasons for this request are as follows:

• Manual Control Preference: I prefer not to have any buttons in my aircraft operated automatically. Specifically, I find the automatic pressing of the right FMC buttons and the accompanying sound distracting.
• FMC Availability: There are times when I would like to use the right FMC myself, but GSX is actively utilizing it, forcing me to wait until it finishes before I can access it, for instance, to set up the LEGS page.
• Door Operations: With PMDG recently adding the ability to open doors via the EFB, I am happy to manage these operations manually when needed.
• Notification Consistency: I find it unnecessary for GSX to notify me to open doors when it proceeds to do so automatically. I would prefer to be notified only when manual action is genuinely required.

I am aware that this option has been requested in the past, which reinforces the idea that it could be of interest to a broader user base.

As an alternative to GSX’s integration, I am satisfied with the existing integration between PMDG and SimBrief, and I continue to enjoy all the other features GSX Pro offers.

Thank you for considering this request. I believe that providing users with this additional flexibility would further enhance the GSX experience. Please let me know if further clarification is needed.

Best regards,
Davide

[pete_auau]

thought if  you dont  want  to use  gsx  than  dont  select  any  request  from  the  drop  down menu  as  far  as i know  pmdg intergration  is  not  the  same  as   the  fenix   where  you do it  thru  the  efb  and  is  all  done  automatically

[Davide]

thought if  you dont  want  to use  gsx  than  dont  select  any  request  from  the  drop  down menu  as  far  as i know  pmdg intergration  is  not  the  same  as   the  fenix   where  you do it  thru  the  efb  and  is  all  done  automatically

Thank you for your reply, but I believe there has been a misunderstanding. I am not asking to stop using GSX entirely, I greatly appreciate its vehicles, animations, pushback and all other features. My request is simply to have the option to disable the integration with the FMC, so I can use GSX normally without it interacting with the aircraft’s systems automatically.

[pete_auau]

gsx  interacts  with  the  right  cdu  so  you still can use  the  left cdu

[Captain Kevin]

gsx  interacts  with  the  right  cdu  so  you still can use  the  left cdu

Yes, but there are instances where one might use both, and that's not possible if the right one is being used. Additionally, I can also set up SPAD.neXt to have the doors open automatically when called via the script panel and event trigger, as I have done in P3D, negating the need to have GSX use the FMC to do so.

[pete_auau]

well  there  your  option  than

[Davide]

gsx  interacts  with  the  right  cdu  so  you still can use  the  left cdu

Thank you for your response. To clarify, my request specifically concerns the right FMC. I understand that GSX utilizes this particular FMC for its operations, but I would prefer to have the option to manage it independently while continuing to use all other GSX features.

Yes, but there are instances where one might use both, and that's not possible if the right one is being used. Additionally, I can also set up SPAD.neXt to have the doors open automatically when called via the script panel and event trigger, as I have done in P3D, negating the need to have GSX use the FMC to do so.

I completely agree with Kevin’s points and appreciate his enriching response.

[Davide]

I kindly request an official response.

[Copper]

I agree with this request, especially since in my case GSX sometimes causes wrong fuel values entered (I guess the sequence of clicks and wait times is not accurate), resulting in 2t instead of 20t being loaded in the 77F.

The other part of the integration (opening doors etc.) seems to work fine but I rather enter the weights and fuel myself and currently there is no option to inhibit this being done by GSX.

[Davide]

I agree with this request, especially since in my case GSX sometimes causes wrong fuel values entered (I guess the sequence of clicks and wait times is not accurate), resulting in 2t instead of 20t being loaded in the 77F.
The other part of the integration (opening doors etc.) seems to work fine but I rather enter the weights and fuel myself and currently there is no option to inhibit this being done by GSX.

I agree with your points. The issues with the 77F might be due to its recent release, as there could still be some bugs in the integration. To prevent similar problems with newly released products in the future, having this option available would indeed be very useful.

[virtuali]

I agree with this request, especially since in my case GSX sometimes causes wrong fuel values entered (I guess the sequence of clicks and wait times is not accurate), resulting in 2t instead of 20t being loaded in the 77F.

Can you please make a video of this ? We have a custom time delay between key presses that is different for every aircraft and of course every system might be different, so we might just have to adjust that.

[Davide]

Can you please make a video of this ? We have a custom time delay between key presses that is different for every aircraft and of course every system might be different, so we might just have to adjust that.

Dear Umberto, could you kindly respond to the initial request?

[virtuali]

Dear Umberto, could you kindly respond to the initial request?

- Disabling the automation just for personal preference is something we can do, but it's not a very high priority task, because we have other things to do first. That doesn't obviously mean we won't do it, just we won't do it now, because as you said yourself, it works flawlessly in your case.

- If somebody has an actual problem, like setting wrong values (possibly due to timing issues), that's an much higher priority task, because it IS a problem that must be fixed and it's not supposed to happen, that's why for THIS reason, I need some help replicating it, but adding the ability to remove it JUST for this reason, is wrong and won't be done, because in general it's wrong to spend time to add options to prevent possible bugs, when we might take less time to fix the actual bug instead, assuming we can replicate it and if we can't, at least understanding why it's happening to somebody else.