FlightSim Development Group

Hey All, FSDG will the update include GSX compatibility? GSX won't work.

If GSX doesn't work please follow the advice from "abhi" in this post: viewtopic.php?p=9298#p9298

I did follow the steps and it doesn't work.

What exactly does not work?

The message I received when trying to initialize GSX was " [GSX] There are no parkings available at this airport".

If you receive that message and the steps described earlier in this thread did not help please contact the GSX support.

USAIRBRO wrote:The message I received when trying to initialize GSX was " [GSX] There are no parkings available at this airport".

GSX doesn't take the good AFCAD file for VOBL but the one in FSDG common secenry which correct altitude. it's the reason why you have this message.

As already said in this forum the most simple is to exclude one folder from GSX scan:
Edit the file Couatl.ini under "C:\Users\xxxxxx\AppData\Roaming\Virtuali" where xxxxxx is your username.
Add the line:
airportCacheExcludeArea=FSDG\scenery\world\scenery

To be sure GSX uses this new parameter you can force it to rebuild the aiport cache (Couatl menu entry in Addons, restart couatl and rebuild...)

Skip.

USAIRBRO wrote:I did follow the steps and it doesn't work.

See u need to install all updates whatever u get it from here... no need to do anything... all of my friends did same and GSX works without any problems....

v1.1 Issues:

displaced threshold 1000 feet each end of the runway, why?
Gate 5 is where Emirates always arrive and park, radius still too small in the afcad.

We displaced the runway threshold because AI would otherwise turn around on the runway and get in conflict with other AI waiting for take off. Since the offset should not affect the user (ILS & lights unaffected) we decided to use that trick to help AI behave more realistic.

horst18519 wrote:We displaced the runway threshold because AI would otherwise turn around on the runway and get in conflict with other AI waiting for take off. Since the offset should not affect the user (ILS & lights unaffected) we decided to use that trick to help AI behave more realistic.

Got it thank you. One more question should sode .cfg files be set to the different encoding? Lockheed say encoding should be

xml file: UTF-8

cfg file: UCS-2 LE BOM

horst18519 wrote:We displaced the runway threshold because AI would otherwise turn around on the runway and get in conflict with other AI waiting for take off. Since the offset should not affect the user (ILS & lights unaffected) we decided to use that trick to help AI behave more realistic.

sode jetways not linked to gates, required to open sode window manually and request. It should be linked to each gate number so gsx can operate it. Instead of Gate X Sode is named Terminal X

That is how we do it. SODE link is not part of the scenery, it's a free service for those who like to use SODE jetways.

horst18519 wrote:That is how we do it. SODE link is not part of the scenery, it's a free service for those who like to use SODE jetways.

If the sode gate is called "gate 5" then gsx can pick up there is a sode jetway for that gate. You have the name "terminal: 5" and that confuses gsx. Also gate 5 is so small the radius if I make it bigger only one jetway can attach the first attempting to connect to door 1L says "too close"

I am able to connect only 1 jetway the front jetway to 2L door.

We cannot influence the radius. If the door is too close you might want to try parking further back.

Are you familiar with SODE xml files? You can access the VOBL jetway definitions file and change terminal to gate if you want. We might change it if that succeeds.

horst18519 wrote:We cannot influence the radius. If the door is too close you might want to try parking further back.

Are you familiar with SODE xml files? You can access the VOBL jetway definitions file and change terminal to gate if you want. We might change it if that succeeds.

In the afcad file you provided, the radius of the gate 5 parking spot, the gate that Emirates brings their 777 every flight to, is very small the radius of a 777 is 35meters and the gate 5 radius in your afcad is half that. If I raise the radius myself, the sode gate only connects the front to my second left door.

It is your decision to which door you dock which jetway. The parking radius should be big enough for heavy AI to use the gate.

horst18519 wrote:It is your decision to which door you dock which jetway. The parking radius should be big enough for heavy AI to use the gate.

That is the problem, they are not big enough, gate 5 in your afcad is too small for any jet.

Attached is a picture of the afcad see gate 5 and the parking radius of 5 meters. a 777 has a radius of 35 meters. I cannot park at gate 5 in a 777, and no AI will be able to park at a gate with a radius of 5

Gate 2 is the A380 gate, that's why we decided to make the next gates smaller ones so the big birds don't interfere with each other.