You guys are making up a bit of a panic. GSX is not gonna destroy your MSFS installation or windows. If you uninstall it, it's gone with all its effects.

As for the CTDs make sure to have a clean reinstall of GSX (completely uninstalling and deleting the addonmanager folder) and perhaps delete your content.xml (if you are on SU9). Whenever something crashes often (like every flight) it's a sort of scenery/addon conflict in my experience. A rebuilt content.xml can often solve that.

59 minutes ago, Higgy68 said:

I have not purchased GSX and wont be after seeing this. Seems like a money grabbing effort from FSDreamTeam. Very poor.

Typical for someone (737NG driver makes wonder about the rest 😅) that hasn't a clue what he is doing and didn't read the manual 🤣

Edited August 19, 20223 yr by awf

1 hour ago, micstatic said:

I decided to totally uninstall GSX for now.  Too much going on with installs/CTDs.  I'm confident it will get sorted out eventually.  

Yep, I still haven't been able to install it. 😕

After watching this video I'm glad I haven't purchased GSX Pro yet. I'm going to wait until it's had a few updates under it's belt. 

Edited August 19, 20223 yr by Wise87

This is why I never buy anything on day one. I figure, I've waited this long, I can take a week and let other people leave reviews after testing. I'm sure they'll get this sorted out, but it's always good to wait and see how things play out. 

4 minutes ago, Bdub22 said:

This is why I never buy anything on day one. I figure, I've waited this long, I can take a week and let other people leave reviews after testing. I'm sure they'll get this sorted out, but it's always good to wait and see how things play out. 

When I bought it yesterday I figured it’d be a little rough around the edges. But I had no idea that a full 24 hours later I’d still be unable to even launch it. 

How do I see which version of GSX I have installed, and how do I see which is the latest published version?

The Live Update tool don’t seem to give that information. Every time I start   it, it lets me run Update, but it never says what it is doing. 

3 hours ago, Fiorentoni said:

You guys are making up a bit of a panic. GSX is not gonna destroy your MSFS installation or windows. If you uninstall it, it's gone with all its effects.

As for the CTDs make sure to have a clean reinstall of GSX (completely uninstalling and deleting the addonmanager folder) and perhaps delete your content.xml (if you are on SU9). Whenever something crashes often (like every flight) it's a sort of scenery/addon conflict in my experience. A rebuilt content.xml can often solve that.

I just completed a 1 hr 32 min flight from Flightbeam KIAD to FlyTampa KBOS in the 737-700. No crashes. Everything worked as it should according the the settings I had when I started the flight. Some options were not set the way I wanted them to, so I'm going to tweak them for the return trip. I did not experience any performance issues. 

The good:

• I read the manual and played around with it at the gate for good a bit before I flew. This was a good choice. 
• Customizing vehicle positions is easy once you get used to some minor kybd changes from the older version.
• Catering worked great
• Fueling worked as it should for the options I had set up.
  • I forgot to turn the option to "Show MSFS Fuel and Cargo" for the plane, so I had to key in the fuel quantity on the MCDU. It's more realistic this way anyway, so I may leave that off. 
  • I forgot to turn on progressive fueling altogether. Grrr...
• The push back from gate C17 was spot on. I chose nose right / tail left and GSX left me right on the CL.  
• Marshaller service was good in Boston.
• De-boarding service was great. Jetway connected automatically, the handlers got the cargo, and the pax walked up the jetway. 

The bad:

• No matter what I try, once I have customized a single gate position (FB KIAD during test) at the airport, all of the Flightbeam jetways were replaced with FSDT jetways (the next time MSFS loaded the airport). I tried excluding them on the installer screen as well as used the "Exclude 3rd party" button. And yes. I remembered to "apply" the changes. 😉
• The FSDT jetway bridges did not attach to the same spot where the FB jetways were. Some were very close, others were clearly offset to one side or another of where they should be. Some had the angles wrong. It said it was using the correct (FB) scenery file, but it looked like it might be using the default KIAD file instead.  
• After de-boarding was complete, I had to tell the airplane that it was empty in the MCDU

It was nice to fly with services again. The minor issues I did have will get squared away. This is Umberto after all. We know for sure that he will be working tirelessly on GSX for the next 10 years. Give him a little time to get past the odd stuff that was bound to appear and he'll be back at the usual cycle of fixing and adding things.

Edit: I know some folks don't like doing this, but if you are having major problems, try deleting all of the .dat files in your localcache sceneryindexes folder before you launch the sim next time. I do this every time I add something new, and frequently in between. I don't think MSFS likes it when the actual scenery doesn't match what's in the indexes.

Edit #2 - After that little sim update we just got, I started a flight at FT KBOS and now I'm getting their jetways instead of GSX's. Don't know why, but I'll take it. It seemed like it made the 737 recompile its WASM, so maybe GSX's WASM recompiled too?

Edited August 20, 20223 yr by MDFlier

1 minute ago, MDFlier said:

I just completed a 1 hr 32 min flight from Flightbeam KIAD to FlyTampa KBOS in the 737-700. No crashes. Everything worked as it should according the the settings I had when I started the flight. Some options were not set the way I wanted them to, so I'm going to tweak them for the return trip. I did not experience any performance issues. 

The good:

• I read the manual and played around with it at the gate for good a bit before I flew. This was a good choice. 
• Customizing vehicle positions is easy once you get used to some minor kybd changes from the older version.
• Catering worked great
• Fueling worked as it should for the options I had set up.
  • I forgot to turn the option to "Show MSFS Fuel and Cargo" for the plane, so I had to key in the fuel quantity on the MCDU. It's more realistic this way anyway, so I may leave that off. 
  • I forgot to turn on progressive fueling altogether. Grrr...
• The push back from gate C17 was spot on. I chose nose right / tail left and GSX left me right on the CL.  
• Marshaller service was good in Boston.
• De-boarding service was great. Jetway connected automatically, the handlers got the cargo, and the pax walked up the jetway. 

The bad:

• No matter what I try, once I have customized a single gate position (FB KIAD during test) at the airport, all of the Flightbeam jetways were replaced with FSDT jetways (the next time MSFS loaded the airport). I tried excluding them on the installer screen as well as used the "Exclude 3rd party" button. And yes. I remembered to "apply" the changes. 😉
• The FSDT jetway bridges did not attach to the same spot where the FB jetways were. Some were very close, others were clearly offset to one side or another of where they should be. Some had the angles wrong. It said it was using the correct (FB) scenery file, but it looked like it might be using the default KIAD file instead.  
• After de-boarding was complete, I had to tell the airplane that it was empty in the MCDU

It was nice to fly with services again. The minor issues I did have will get squared away. This is Umberto after all. We know for sure that he will be working tirelessly on GSX for the next 10 years. Give him a little time to get past the odd stuff that was bound to appear and he'll be back at the usual cycle of fixing and adding things.

 

Just FYI: Don't use MSFS Fuel and Cargo, this does no good with the PMDG (or any 3rd party custom w&b aircraft). You have to key in the fuel quality in the CDU (unless PMDG decides to integrate GSX after all those decades...).
As for progressive fueling: Yes, that's gotta be on 🙂
 

32 minutes ago, MDFlier said:

Edit: I know some folks don't like doing this, but if you are having major problems, try deleting all of the .dat files in your localcache sceneryindexes folder before you launch the sim next time. I do this every time I add something new, and frequently in between. I don't think MSFS likes it when the actual scenery doesn't match what's in the indexes.

I keep forgetting about that, good point.

3 hours ago, NovemberUniform said:

First flight with GSX installed and a few minutes after takeoff CTD. Around 10 minutes might be right. Event viewer shows a crash with Couatl64_MSFS.exe as the cause. Interestingly with a timestamp not matching the actual crash of the sim. 

Did you reinstall? If so, has the problem been solved? 

I will try to reinstall it to see.

I had the issue as many reported at the first download where GSX just did not work at all. I removed it, and the installers and re-installed a second time a few hours later. From then on it has been working pretty well. as in the seervices are conncecting fine, passengers and crew are loading as predicted, the only issue i come across is having to click the GSX logo in the drop down window 2-3 times to get it to work.

So far i have only done one flight of just over the hour in the Fenix A320, with no issues so far.If i do start getting Ctd's i'll just remove it until it.s more stable.

21 minutes ago, Fiorentoni said:

Just FYI: Don't use MSFS Fuel and Cargo, this does no good with the PMDG (or any 3rd party custom w&b aircraft). You have to key in the fuel quality in the CDU (unless PMDG decides to integrate GSX after all those decades...).
As for progressive fueling: Yes, that's gotta be on 🙂
 

Have you seen page 60 of the manual? The behavior is a bit strange given the name of that option, but it works as described. Try it.   

If you have a Simbrief flight that meets the 3 criteria, GSX will add the "Use Simbrief fuel" option to the standard GSX menu with the percentages in it. It doesn't actually open the MSFS fuel and cargo screen.

This has been a complete disaster for me. The buggiest most finicky piece of software I have ever tried. I have been thoroughly enjoying MSFS for months after moving from XPL and the last two days I have been troubleshooting more than flying. I’m ditching it for now. 

3 minutes ago, MDFlier said:

Have you seen page 60 of the manual? The behavior is a bit strange given the name of that option, but it works as described. Try it.   

If you have a Simbrief flight that meets the 3 criteria, GSX will add the "Use Simbrief fuel" option to the standard GSX menu with the percentages in it. It doesn't actually open the MSFS fuel and cargo screen.

On page 58 on the "show MSFS fuel and cargo screen" option:
"Some airplanes might use non-standard Fuel systems or might exhibit issues if an
external program changes the Fuel quantity and, by disabling this option, when the
Fuel Truck connects, GSX will just ask you to use any Fuel loading option provided
by the airplane itself (like a loader, an EFB or FMC menu), and will wait for the Fuel
quantity to change."

PMDG uses non-standard fuel systems, so what you are trying to do will not work. In the best case nothing will happen (no fuel will be added), in the worst case you will do something wrong with the 737. I remember RSR saying that people should not touch the MSFS fuel screen with the 737, at all, or it will create problems.

At least that's how it was in P3D, but sure go ahead and try it 🙂