I installed the update yesterday, enabled the PMDG 738 pax loading option, then this morning set out to fly the plane and now get this.  Someone on PMDG forum mentioned this happened to him and disabling the feature in GSX resolves the issue thankfully:

 

If I recall they also had issues with Fenix based on the Livery.  Perhaps Livery issues?   

You didn't mistakenly buy the home cockpit version did you?

/sarc

Works fine in 777

2 hours ago, Noel said:

I installed the update yesterday, enabled the PMDG 738 pax loading option, then this morning set out to fly the plane and now get this.  Someone on PMDG forum mentioned this happened to him and disabling the feature in GSX resolves the issue thankfully:

You should have reported this in the proper places:

- the FSDT support forum

OR

- the GSX Community channel on Discord ( I suggest this, for a faster reply )

Those are being discussed already, and there are ways to troubleshoot those, and this is not really the place to do that.

Edited July 23, 20241 yr by virtuali

1 hour ago, virtuali said:

You should have reported this in the proper places:

- the FSDT support forum

OR

- the GSX Community channel on Discord ( I suggest this, for a faster reply )

Those are being discussed already, and there are ways to troubleshoot those, and this is not really the place to do that.

You should realize I had no idea about the source of this and wanted anyone HERE to know in case they run into it as well.  I assumed it was the PLANE, had no idea it was GSX, and by visiting the PMDG forum that is where I learned about the cause of this.

Since this is being discussed already YOU should have posted about this issue here as I'm sure others will be fooled into thinking this is PMDG's issue.

Edited July 23, 20241 yr by Noel

Sorry Umberto, I disagree. AVSIM is my primary source for news/updates/info. I don't frequent your fourm, nor do I plan to. It's perfectly okay to discuss products on this site. I appreciate your products, but I do not appreciate constantly vilifying the customer.

12 minutes ago, V1ROTA7E said:

Sorry Umberto, I disagree. AVSIM is my primary source for news/updates/info. I don't frequent your fourm, nor do I plan to. It's perfectly okay to discuss products on this site. I appreciate your products, but I do not appreciate constantly vilifying the customer.

Just because it is your primary source does not mean it is where developers track or monitor their own individual product issues.  Almost EVERY developer will ask you to post in their forums or nowadays their discord if you are having an issue with their products.  PMDG provides NO support via Avsim posts and Umberto and other developers always ask for issues to follow the correct support protocols. 

Expecting the developer to put up informational posts about every update/issue here at Avsim or other public forums has never been how things worked, similar to how the 777 issues are being discussed in the PMDG forums, not here... 

Edited July 23, 20241 yr by psolk

6 minutes ago, psolk said:

Just because it is your primary source does not mean it is where developers track or monitor their own individual product issues.

Sure, but people should still continue to post here so we can all learn. If they then want to also post on the dev's forums (or the dev politely asks them to), that's fine. But some devs seem to not want their product's flaws/bugs/issues discussed outside their own forums, which I don't agree with. The OP didn't ask for support, they just posted something that happened, and also posted a workaround/fix. This is what I come to Avsim for. 

This is a discussion forum, and for a dev to say "this is not the right place to discuss", just comes across as disingenuous. Just ask people to post on the support forums, that's fine. But don't tell us not to discuss your product. 

8 minutes ago, psolk said:

Expecting the developer to put up informational posts about every update/issue here at Avsim or other public forums has never been how things worked, similar to how the 777 issues are being discussed in the PMDG forums, not here... 

I never said that the developer should support their products on here....but it seems as if you are suggesting that NO support, including from other users, should be allowed here. Linking an existing discussion topic is helpful. Telling people they shouldn't discuss it here is NOT.

11 minutes ago, V1ROTA7E said:

I never said that the developer should support their products on here....but it seems as if you are suggesting that NO support, including from other users, should be allowed here. Linking an existing discussion topic is helpful. Telling people they shouldn't discuss it here is NOT.

Nope, this is exactly that, a user forum so getting a developer to respond at all is hit or miss.   Where did I ever suggest no support should be allowed here?   Please, I beg you to point out to me how you even turned my words into that... 

However, if you are going to take the time to post it here to let other users know developers usually like you to also make them aware so they can gauge how large the issue is, how many people are impacted, what liveries etc so they can troubleshoot.   The developer actually troubleshooting the issue almost always takes place in their forums which is all that was being said.    

 

 

Edited July 23, 20241 yr by psolk

14 minutes ago, psolk said:

Where did I ever suggest no support should be allowed here?   Please, I beg you to point out to me how you even turned my words into that...

Ok, sure.

Firstly, you upvoted Umberto's comment, suggesting that "[he] should have reported this in the proper places." This suggests that he should not have reported it here at all -- i.e. a public forum open to getting support from whomever.

Secondly, the OP never specifically asked for the developer's response, he was simply reporting the issue, and you still had something to say about it. This suggests that your issue is with the act of bringing it up in this forum in the first place.

24 minutes ago, V1ROTA7E said:

Ok, sure.

Firstly, you upvoted Umberto's comment, suggesting that "[he] should have reported this in the proper places." This suggests that he should not have reported it here at all -- i.e. a public forum open to getting support from whomever.

Secondly, the OP never specifically asked for the developer's response, he was simply reporting the issue, and you still had something to say about it. This suggests that your issue is with the act of bringing it up in this forum in the first place.

Ah, so you are implying and reading my mind, got it...  

I also didn't respond to the OP, I responded to your post that you disagreed with Umberto because this was "Your" first stop for information.  The OP already had another thread regarding reinstalling the 737 due to this issue and came to the same resolution anyway plus there is another separate GSX thread so I personally didn't see a need for a 3rd and you have no idea "why" I upvoted Umberto's post, perhaps it is because there are not very many developers that say anything here at all and yet he has been here repeatedly throughout the years.  I appreciate that even if I don't always appreciate what he says..  Interesting he said the same thing to a user in the other thread and there response was "done, thanks" so not sure why what he said is a big deal... 

But you go on assuming you know what I was thinking and saying.  😉  

Edited July 23, 20241 yr by psolk

1 hour ago, psolk said:

I also didn't respond to the OP, I responded to your post that you disagreed with Umberto because this was "Your" first stop for information. 

This is going to be my last post arguing with you. Regarding what I said, I also specified "It's perfectly okay to discuss products on this site." My point of contention was where he said:

aid:

Those are being discussed already, and there are ways to troubleshoot those, and this is not really the place to do that.

I don't care whether the developer pops in here to support their product or not, because I know that I'm likely able to get support from another user on here. Over the years, Umberto's attitude towards customers has been full of disdain, and I'm honestly exhausted by it. He could just as easily have said "Hey OP, there's already a topic about this bug on our forum. Here's the link to the discussion; feel free to follow to stay updated. Thanks for your support." Spoiler alert, there's no info in that "discussion."

Edited July 23, 20241 yr by V1ROTA7E
clarification

1 hour ago, V1ROTA7E said:

I don't care whether the developer pops in here to support their product or not, because I know that I'm likely able to get support from another user on here. Over the years, Umberto's attitude towards customers has been full of disdain, and I'm honestly exhausted by it.

You quoted my sentence, without really understanding it:

Quote

Those are being discussed already, and there are ways to troubleshoot those, and this is not really the place to do that.

The subject of the sentence was the troubleshoot action so, when I say "not really the place to do that", I'm referring to the troubleshooting only, you can discuss about this here as much as you like, but to get something solved, steps must be taken to understand what is really happening, and this is not the place to do that.

I don't think the OP posted here just to put a possible issue out in the open. Instead, I think he IS genuinely interested in getting the problem fixed, so I gave him several useful information, including the fact his issue was already being discussed so, in that small sentence of mine which you quoted as your point of contention, there was everything he needed to know to find a solution in the fastest way possible.

 

Edited July 23, 20241 yr by virtuali