Rollback to the previous version of GSX

[ozflyer]

How can I get hold of the previous version of GSX ?

The latest one is causing too many issue, the only reason I downloaded was the feature to select parking before landing, which was nice, as did have to go into gsx menu while taxiing from the runway back to gate.

But with the issue I am seeing with the new version, prefer to rollback.

Thanks

[villaloha]

Hi Ozflyer.

I requested the same. Awaits their response.

[Bruce Hamilton]

Even if you can roll back, any FSDT installer you run will pull any outdated file from the server, you'll be right back where you started.

[villaloha]

I saved the file "gsx_setup.exe dated 2014, unfortunately, it won't work. I guess only way is FSDT would have to fix the new version.

[virtuali]

We are fixing all the issues reported, one by one.

The new features asked by many users, such as support for airports with non-standard elevated ground and the gate preselection, had a lot of side effects, but we are fixing all of them, and we already published 3 updates today and won't obviously stop updating as long there are still bugs left.

[villaloha]

Here's 2 examples but it applies to almost all airports. Looking forward to see it working again soon.

[virtuali]

Your screenshots clearly indicates GSX is operating correctly and instead, it's a result of having improved picking up of AFCADs that it might have ignored before and caused the "no AFCAD data at this position" error many users complained about.

Now, it probably never leave any AFCAD behind, so it's now more important to use the airport_visibility_xxxx command to exclude those airports with fake ICAO made only to simulate small seaplane bases, helipads, etc.

This feature has been there since several versions ago, and it's fully documented in the manual, at Page 21.

In case of the two airports in your screenshot, you should add the following lines to your %APPDATA%\Couatladdons.INI file, under the [GSX] section:

airport_visibility_ZYYZ = 0
airport_visibility_ZMIA = 0

DO NOT use the other documented command disable_on_airports! This will do an entirely different thing, and will completely disable GSX on any airport.

[villaloha]

I found Couatladdons.INI and opened. Please bear with me, I'm not an expert on this kind. I am puzzled that there is no airport_visibility_xxxx list. Should I add all add-ons? If so, which line should I add under? Thank you for your patience.

[gsx]
refueling_time_min = 15.0
deboarding_time_factor = 0.1
refueling_time_factor = 0.0022
deboarding_time_min = 15.0
parking_editor_sash = 150
show_vehicle_editor_help = 1
disable = 0
disable_on_airports = NONE
parking_editor_width = 874
boarding_time_min = 15.0
boarding_time_factor = 0.2
parking_editor_height = 640
waiting_msg_delay = 10.0
followme_speed_knots = 18
slowdown_speed_knots = 7.5
straight_pushback_meters = 40.0
ui_verbosity = 2
ui_volume = 0
marshaller_distance_readout = 0
editor_disable_joystick = 0
deboarding_time = 0
boarding_time = 0
refueling_time = 0

[parkme]
disable = 1

[common]
audiodevice = Generic Software on Speakers (Realtek High Definition Audio)
audiovolume = 1.0

[cyvr]
lastspringday = 300
lastwinterday = 32

[liveupdate]
last_check = 1465222237.77
major_version_installed = "b4031a-4-53440040258ed"
major_version_ignore = "b4031a-4-53440040258ed"
live_version_installed = "9801b9-b0068-5349be474fa40"
live_version_ignore = "9801b9-b0068-5349be474fa40"

[virtuali]

I am puzzled that there is no airport_visibility_xxxx list. Should I add all add-ons? If so, which line should I add under?

Of course there isn't one, you are supposed to add your own excluded airports. The _xxxx is just a example that you must replace with the (fake) ICAO code you want exclude.

As I've said, you should add the following lines to your %APPDATA%\Couatladdons.INI file, under the [GSX] section so, that PART of the file will look like this:

[gsx]
refueling_time_min = 15.0
deboarding_time_factor = 0.1
refueling_time_factor = 0.0022
deboarding_time_min = 15.0
parking_editor_sash = 150
show_vehicle_editor_help = 1
disable = 0
disable_on_airports = NONE
parking_editor_width = 874
boarding_time_min = 15.0
boarding_time_factor = 0.2
parking_editor_height = 640
waiting_msg_delay = 10.0
followme_speed_knots = 18
slowdown_speed_knots = 7.5
straight_pushback_meters = 40.0
ui_verbosity = 2
ui_volume = 0
marshaller_distance_readout = 0
editor_disable_joystick = 0
deboarding_time = 0
boarding_time = 0
refueling_time = 0

airport_visibility_ZYYZ = 0
airport_visibility_ZMIA = 0

The other sections will be left untouched. Just add those two lines anywhere under the [GSX] section.

[villaloha]

It's now working at CYYZ, KMIA and I added more.

I also add TJSJ, it still won't work. Could be wrong code, is there somewhere where I can find the correct airport's code? Thanks.

[virtuali]

I also add TJSJ, it still won't work. Could be wrong code, is there somewhere where I can find the correct airport's code?

TJSJ seems to be the correct code, that scenery must have some other .BGL with a fictional code.

[cbarbas]

Hi,


is it possible for a sticky post and list off the airports with the details such as "airport_visibility_xxxxxxxxx = 0" that someone has to add in case off a problem.

I know its easy to find the AFCAD via the "GSX Customization" but maybe it will be useful.



Regards

[virtuali]

is it possible for a sticky post and list off the airports with the details such as "airport_visibility_xxxxxxxxx = 0" that someone has to add in case off a problem.

I don't see why we should have a sticky post about a procedure that has been fully documented in the GSX manual since several releases.

In addition to that, the current version of Couatl.exe we have online now (that everybody installing anything will get from now one), automatically skips airports with no parkings, so the need for the airport_visibility_xxxx command should be now limited to a very few borderline cases.

[cbarbas]

Hi,

I didnt mean the procedure but the "airport_visibility_xxxxxxxxx = 0".


I have update my GSX and Addon Manager yesterday, am I still(updated) or should I download them again?


Thanks.

[virtuali]

I didnt mean the procedure but the "airport_visibility_xxxxxxxxx = 0".

That's precisely what I meant. The procedure to use the airport_visibility_xxx = 0 command to exclude an airport.

I have update my GSX and Addon Manager yesterday, am I still(updated) or should I download them again?

No, you should already have the latest Couatl.exe which automatically removes auxiliary airports with no parkings, since it's online since June 6th:

http://www.fsdreamteam.com/forum/index.php/topic,13601.msg101344.html#msg101344

Of course, you will STILL have to use this command, if the auxiliary airport that get in the way has at least 1 parking! In this case, GSX cannot possibly know it's "useless", unless you explicitly tell it so.