Yep lets keep supporting and apologizing for these developers that break things we pay for.  Yep, lets bite our tongues and not call out bugs and lack of action to fix them.  Yep let's keep castigating users for not being patient for fixes promised with no deadlines as to when these fixes will actually come.  Yep we get what we deserve because we get what we allow.  Tin hat conspiracy here but its my speculation these things are being done intentionally to force adoption and increase sales on the "new platform", remember the one that was supposedly set to improve our choices in whichever platform we choose to use? Competition is better for the consumer? The 3 great 64bit platform choices we had seems to have disappeared now hasn't it? why is that? FSDT is not alone here we all know it.  Imagine the results we would get if P3D/MS/LR simultaneous install users decided to uninstall MSFS until developers addressed AND FIXED the issues on P3D AND VICE VERSA? and the same with LR. How would MS, LM or LR feel about that?

 

5 hours ago, fluffyflops said:

Let me jog your memory again about the bgl CTD in certain areas in  Nova Scotia, Scandinavia and Central Russia  caused by coutl that people on this forumn pinned down to coutl and it took 2 years for Umberto to admit his software was at fault namely coutl. 

Until he finally admitted defeat and made coutl.exe not read BGLs from a certain height when flying, the issue was rectified. It was only after 2 years of a group of us on telling him it was the combination of coutl and bad BGLS (which LM did nothing to help with) that finally got him to change coutl.  That 2 year episode taught us many things, 1. how hell bent on coutl umberto is and how much of a pain in the bum it is.   2.  How LM where not to invest any time in a issue relating to "simmers".  They let us do the hard work of pinning down the issue.

Look, I see why he uses coutl its to stop people pirating it, hes admitted that,  and Ill admit ive had hours and hours and hours of enjoyment out of GSX,  but this coutl is the root of all evils here, thats what causing the issues in P3D and MS2020, as its riddled with bugs and issues, always has been. 

Maybe I should jog your memory, then, and remind you that couatl was attempting to read scenery bgl files in remote areas using standard calls that work everywhere else, and that triggered a CTD. 

What you mischaracterize as an "admission" was recognition that couatl was encountering some bad bgl file interaction in a select few super-remote places by reading bgl files that otherwise would probably never be touched, and he found a way to work around that by dumbing-down the program a bit to prevent those reads.  The problem was/is within P3D--either the data in those bgl files was bad or some untrapped error occurred when processing something within them--coatl wasn't the faulting module, it was P3D itself.  The CTDs weren't "caused" by his software issuing a legit read call in the middle of nowhere any more than they were "caused" by the users who were repeatedly flying through those known problem areas.

Analogy: If you use your iPhone to dial the number of your local pub and BT's switching center routs you to "Dial-a-Prayer" instead, that's a BT problem, not an Apple problem.  And if you keep dialing the pub and keep getting "Dial-a-Prayer" it still isn't Apple's problem, no matter how many times you do it, how long the problem lasts, or how red-faced you get in the process.  Now Apple might help you resolve the problem by sending calls to that number through a different network, but it still was never something they did or were responsible for, and their workaround to fix the problem is not an admission or indication that it was their fault.

The dead horse beating here is getting old.  Let's stick with the problems at hand rather than dredging up ancient grudges.

w/r/t the Cartayna ini files not working--is there anything in the couatl.log file?  The logging couatl does is usually pretty helpful in finding issues with configurations.  Might be something easy to identify, like file path problems.

I read through his forums and I am reminded of why I am so reluctant to ever release a general purpose tool, considering how demanding, unforgiving and impatient many GSX users are. Then I have a problem or want to report something and I am convinced that Umberto through his tone (not sure if it's intentional) makes things twice as bad for himself. I think Umberto and his most unpleasant users are locked in each others' Hell.

GSX, despites its occasional issues and its developer's inability to get useful feedback at times, is still an amazing piece of software and to this day I am surprised both at how well it works and the ecosystem that it needs to support.

Cheers!

Edited September 6, 20223 yr by Bob Scott
Mod edit: quote from hidden post removed

27 minutes ago, Luke said:

I read through his forums and I am reminded of why I am so reluctant to ever release a general purpose tool, considering how demanding, unforgiving and impatient many GSX users are. Then I have a problem or want to report something and I am convinced that Umberto through his tone (not sure if it's intentional) makes things twice as bad for himself. I think Umberto and his most unpleasant users are locked in each others' Hell.

GSX, despites its occasional issues and its developer's inability to get useful feedback at times, is still an amazing piece of software and to this day I am surprised both at how well it works and the ecosystem that it needs to support.

Cheers!

I agree. If you're lucky to pick-up correct and not faulty update (their cloud service is a different story), GSX is superb.

I also deem GSX invaluable. I use it on every appropriate flight. For me it works well - except for the follow-me car, which often shows really weird behavior (wildly flipping direction, driving straight while front wheels are steering in a direction)

I am seeing the ground staff doing unusual things, and when I ask for pushback the tender does not move, but the pushback starts. Then the rear wheels of the 737 bury themselves halfway into the tarmac.  The process completes, and once the disconnect has been made the wheels return to the surface. Have others experienced this?  I am using P3D5.

I unistalled and downloaded afresh to re-install, but nothing changed.

Until the latest update GSX has always worked perfectly for me.

On 9/6/2022 at 8:15 AM, d.tsakiris said:

I also deem GSX invaluable. I use it on every appropriate flight. For me it works well - except for the follow-me car, which often shows really weird behavior (wildly flipping direction, driving straight while front wheels are steering in a direction)

I noticed that "wheels locked sideways" problem in some of the other service vehicles when I watched a YouTube preview of the MSFS version of GSX recently. It is a minor issue, but it would definitely annoy me if I had the product.

4 hours ago, Jonahbird said:

I am seeing the ground staff doing unusual things, and when I ask for pushback the tender does not move, but the pushback starts. Then the rear wheels of the 737 bury themselves halfway into the tarmac.  The process completes, and once the disconnect has been made the wheels return to the surface. Have others experienced this?  I am using P3D5.

I unistalled and downloaded afresh to re-install, but nothing changed.

Until the latest update GSX has always worked perfectly for me.

Yes, I noticed that in P3D, but the man moves and then announces he is ready and only then does the truck take position. After that all proceeds fine. I use the 747 and no problem with wheels. GSX does have an intermittent problem in that it sometimes seems to lose track of what is happening. As in it will tell me that I cannot ask for pushback as the stairs are still operating, when that completed long ago. Then a reset is the only answer.

Hi all

What is the current status of GSX with P3D?

Is all working as it should now?

 

Thanks

33 minutes ago, Mejjo said:

Hi all

What is the current status of GSX with P3D?

Is all working as it should now?

 

Thanks

Depends on which version of P3D. v5 seems ok if installed on it's own.  V4 still open issues, simultaneous installs v4/v5,MSFS in any combination still open issues. 

 

24 minutes ago, jalbino59 said:

Depends on which version of P3D. v5 seems ok if installed on it's own.  V4 still open issues, simultaneous installs v4/v5,MSFS in any combination still open issues. 

 

Thank you,

I have P3D V5 and GSX, I also have MSFS but without GSX. What are the open issues still?

1 hour ago, Mejjo said:

Hi all

What is the current status of GSX with P3D?

Is all working as it should now?

I updated this morning for v5.3HF2. The isolated position problem at KORD was solved but KDEN, KSFO and KIAD all by Flightbeam only have one parking position. Umberto is still investigating that.

Otherwise it seems okay.

41 minutes ago, Mejjo said:

Thank you,

I have P3D V5 and GSX, I also have MSFS but without GSX. What are the open issues still?

In your case, since it's similar to mine, I would say none that cannot be overcome. In my troubleshooting I found that the character encoding for the addon.cfg file in two locations were incorrectly set which seemed to have caused some flightbeam sceneries (KDEN, KIAD, KSFO, LFBO are the ones I have) not to work (not necessarily caused by GSX). Also, the need to place custom aircraft gsx.cfg files in the alternate location, inside aircraft root folder rather than appdata-roaming-virtuali-airplanes causing some aircraft customizations, (CS titles in particular), not being saved once the sim is exited (again not necessarily caused by GSX, since the manual mentions this as an option, but in my case it was mandatory rather than optional to fix that issue.)  The program is fine, but it requires quite a bit user troubleshooting to make it work right. Those are 2 examples I had to correct. l don't think that level of troubleshooting should be required in an RTM product. 

Edited September 7, 20223 yr by jalbino59

22 hours ago, Ray Proudfoot said:

I updated this morning for v5.3HF2. The isolated position problem at KORD was solved but KDEN, KSFO and KIAD all by Flightbeam only have one parking position. Umberto is still investigating that.

Otherwise it seems okay.

Ray, has the "hieroglyphics issue" with the marshaller-related floating text also been resolved now, do you know? Umberto suggested as a workaround to turn the Marshaller off. Am wondering if that has been finally resolved now?

22 minutes ago, 787flyer said:

Ray, has the "hieroglyphics issue" with the marshaller-related floating text also been resolved now, do you know? Umberto suggested as a workaround to turn the Marshaller off. Am wondering if that has been finally resolved now?

Mark, my only flight today was into Munich and I parked at a gate with a jetway. So no opportunity to check how a marshaller would behave.