GSX 3.0 Update RAM PC Crash ***SOLVED in 3.0.2***

[medibasti05]

Hello,

I updated the GSX to 3.0 today. Since then GSX no longer loads properly and courtl loads the RAM so full that the whole PC crashes. Even a new installation does not help.     

Does anyone have this problem and know a solution?

[medibasti05]

The error can be traced back to the GSX profiles.

If you start Courtl with the profiles, the RAM loads completely full.

If you start Courtl without any GSX profiles, then the GSX works.

For comparison: Other system from friend, runs normally with GSX profile. The same profile in my system leads to a crash again.

[MrRoper]

its the custom Walker coordinates I think. look for "walkerwaypoints" in your profile and try removing it at the stand you are at.

[MrRoper]

Confirmed by trying to create a new profile at a default airport. As soon as custom walker coordinates exist in the profile, Couatl memory and disk usage goes through the roof.

[medibasti05]

I will try that, but...

it makes no sense if the same GSX profile works on a different system.

[medibasti05]

I can confirm that it is due to the walk in coordinaten.

This means that over 90% of GSX profiles no longer work without these coordinates being deleted.

And it also doesn't explain why it works for some, but not for others...

[MrRoper]

Has your friend got enable walkers enabled in the main GSX settings?

[MrRoper]

I can confirm that disabling the "Enable airport walkers" checkbox in the main GSX settings fixes this issue without editing the profiles. easy work around until its fixed!

[Fornax]

Just confirming same here...GSX Menu stuck in Loading.
EHAM, DL profile, so it got walker waypoints. Latest FSDT installer etc.
"Couatl Scripting Engine" using an insane amount of RAM. First the Config error, now this.

Is "Enable airport walkers" in the in-game menu?
Don't see it in the (pre-game) installer menu. Kind of hard to disable them if the in-game menu doesn't even load.
Trying to kill Couatl, it just re-loads itself. Unable to fly at all as of now.

DX12, Steam, 4080, 7900x3d.

[bwbriscoe]

Trying to get GSX to load at EGLL (iniBuilds) all I get is the GSX loading screen.

It was working fine before the update.

Can anyone help? Thanks

[Ricarte]

Hi guys, after last update my GSX stuck on this screen and increase a lot memory use of PC and doesnt work. Any one having the same problem?

[Ricarte]

Same here, I think its a problem related to all ini sceneries. I tried JFK and LAX and both has the same problem.

[Fornax]

http://www.fsdreamteam.com/forum/index.php/topic,31658.0.html ?

[Tuskin38]

Just confirming same here...GSX Menu stuck in Loading.
EHAM, DL profile, so it got walker waypoints. Latest FSDT installer etc.
"Couatl Scripting Engine" using an insane amount of RAM. First the Config error, now this.

Is "Enable airport walkers" in the in-game menu?
Don't see it in the (pre-game) installer menu. Kind of hard to disable them if the in-game menu doesn't even load.
Trying to kill Couatl, it just re-loads itself. Unable to fly at all as of now.

DX12, Steam, 4080, 7900x3d.

Can you not open it at another airport?

[Fornax]

Yeah, I did, tnx!
Go to airport with no profile -> turn off walking pax in in-game GSX menu -> use any airport.
So working as of now, but no walking pax.