FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: trisho0 on February 18, 2021, 05:10:57 am
-
Hi to all, I have a concern regarding on the GSX ground services with PANC scenery. I launch FSX with PMDG 737 and after loaded the PANC scenery all SODE jetways are there. I call GSX ground services via CRTL+F12 and the GSX menu pops-up as it should but it says "No Jetways Here".
So, I close the GSX menu and I restart Couatl. I call GSX again and now, the jetways operate nicely. On the way, I load another gate with jetway and all working just fine.
I shut down FSX. Later, I launch the same exactly scenario and again GSX says "No Jetways Here". I restart Couatl and all as normal again. I close FSX and come back, same thing.
Do I have to restart Couatl every time after loaded the scenery? I thought, such "restart couatl" is automatic. Am I missing something?
Patricio
EDIT:
After loading PANC scenery with FSX and GSX still the "No Jetways Here" message and close GSX but I don restart Couatl. So, continuing with this I load another scenery as SAWH and the jetways from SAWH work just fine with GSX. Then, I load back to PANC scenery and the jetways works as expected. It didn't work at first loading.
Is it a "bug"?
-
Is this the Aerosoft scenery. If so, check to make sure the jetways are actually for Anchorage and not for one of the other two airports that are right next to Anchorage since that scenery comes with two airports that are literally right next to Anchorage. It's possible you were too close to one of these two airports and GSX thinks you're at one of them. Check page 26 of the GSX manual to see how to fix this, so it doesn't do this.
-
Is this the Aerosoft scenery. If so, check to make sure the jetways are actually for Anchorage and not for one of the other two airports that are right next to Anchorage since that scenery comes with two airports that are literally right next to Anchorage. It's possible you were too close to one of these two airports and GSX thinks you're at one of them. Check page 26 of the GSX manual to see how to fix this, so it doesn't do this.
Hello my dear Captain Kevin for your help. So glad to see you again.
I explored the GSX manual page 26 and yes I found the way to fix my Aerosoft Anchorage PANC jetways but not a success.
I edited the CouatlAddons.INI file with:
[gsx]
airport_visibility_z41 = 0
airport_visibility_lhd = 0
airport_visibility_palh = 0
None of those lines did the trick. I tried also with:
airport_visibility_PALH = 0.4
Still not working ... So, I have to keep restarting Couatl after loading PANC in order to let GSX resurrect the jetways docking (lol).
Patricio
-
I'll have to investigate this the next time I'm home because I do have the Aerosoft scenery, and I don't remember it ever doing this. Are you using the SODE jetways that are available as an option for the scenery or did you use a GSX configuration that had GSX jetways.
-
I'll have to investigate this the next time I'm home because I do have the Aerosoft scenery, and I don't remember it ever doing this. Are you using the SODE jetways that are available as an option for the scenery or did you use a GSX configuration that had GSX jetways.
I appreciate your efforts and help my Captain Kevin!
Regarding on SODE, first I removed original static jetways from the Anchorage-Airport\scenery folder:
PANCjetways.BGL
PANCjetwaysteil2.BGL
Then I added the SODE jetways stuff from http://www.sim-wings.com/SUPPORT_SODE.htm that perfectly match all jetways position. Also, after restart Couatl all jetways docking nicely.
I don't know about GSX configurations and I prefer SODE instead.
Using SODE command SHIFT+D the jetways work. GSX is blind (lol).
Patricio
-
You actually didn't have to remove those files, that installer you got from that link sorts that out automatically for you. In any event, I'll have to investigate this next time I'm home.
-
You actually didn't have to remove those files, that installer you got from that link sorts that out automatically for you. In any event, I'll have to investigate this next time I'm home.
Those removed files are static and leaving back as they were originally then we see double jetways. I will double check if GSX can see better now.
EDIT-1:
I placed the removed static 2 files back to the PANC scenery and ran another test. Result was an exact experience as mentioned earlier and this time I saw double jetways. So, I removed the intruders (lol). I can't find yet another attempt to go rid of the blind GSX.
SODE works just fine but GSX still not working unless I restart or rebuild Couatl.
That installer I got from that link will not sort that out automatically for me because it is not an Installer, it is copy/paste SODE files.
Patricio
EDIT-2:
After loaded PANC to Gate B3 which is the testing matter, I changed to another airport and from that airport I came back to PANC then GSX recognized the jetway. I didn't restart Couatl.
Also, after running GSX Liveupdate then I load PANC it is obvious the jetways work because Couatl restart/rebuild process the new update (LOL)
That is really weird!
Patricio
-
I just did my last PANC Gate B3 GSX testing. I found so far the only solution is to load the aircraft on any other airport than PANC and then to load on the way the PANC scenery and GSX will recognize jetways. Or, to load directly to PANC and restart Couatl.
If I do a flight plan Departure as any ICAO but PANC then Arrival to PANC, GSX will handle the jetways as expected.
If I do a flight plan Departure with PANC then I have to restart Couatl right after loaded the scenery in order for GSX to handle jetways as expected.
It is a "bug" definitely that needs GSX attention.
The addition of "airport_visibility_z41 = 0 and other exclusions in CouatlAddons.ini file is doing nothing.
Any comments and help are welcome.
Patricio
-
As I said, I will investigate this when I get home from work, but you have to be patient here since I don't get home for another week and a half.
-
The addition of "airport_visibility_z41 = 0 and other exclusions in CouatlAddons.ini file is doing nothing.
What do you mean "doing nothing" ? Is GSX still assuming you are located at Z41 ?
-
The addition of "airport_visibility_z41 = 0 and other exclusions in CouatlAddons.ini file is doing nothing.
What do you mean "doing nothing" ? Is GSX still assuming you are located at Z41 ?
I meant or trying to explain that by adding any of the following lines in [GSX] group of CouatlAddons.ini file didn't make any differences in order to get GSX working with PANC scenery as expected. Still I think is a "bug" that I would like to report you Umberto. Please, take the time to read this whole thread to learn my experience.
Umberto, if you have any thoughts I would like to follow you up your recommendations how to fix it.
CouatlAddons.INI
[GSX]
airport_visibility_z41 = 0
airport_visibility_lhd = 0
airport_visibility_palh = 0
Patricio
-
As I said, I will investigate this when I get home from work, but you have to be patient here since I don't get home for another week and a half.
Sorry too fast, I didn't see this reply. You don't get home until almost 2 weeks ahead? Don't you miss home (lol)?
-
I just found P3Dv4 has exactly the same PANC issues in question.
Now 2 different sim with GSX not handling PANC jetways at the first loading.
BUT:
Found P3Dv5 doesn't have such issue.
I think would be great to add a command line telling the Couatl to restart after the first scenery load regarding if FSDT Liveupdate ran before or not.
Patricio
-
I meant or trying to explain that by adding any of the following lines in [GSX] group of CouatlAddons.ini file didn't make any differences in order to get GSX working with PANC scenery as expected.
And that's precisely why I asked if GSX still thinks it's located at z41. Is it ?
-
I meant or trying to explain that by adding any of the following lines in [GSX] group of CouatlAddons.ini file didn't make any differences in order to get GSX working with PANC scenery as expected.
And that's precisely why I asked if GSX still thinks it's located at z41. Is it ?
Hi Umberto and many thanks for helping me on this. I don't know what GSX is looking at but I added the line airport_visibility_z41 = 0 and airport_visibility_lhd = 0 in CouatlAddons.INI
I found the Z41 and LHD almost in the center of the PANC airport stock by looking from ADE. So, I added those ICAO to exclude them following the idea from Captain Kevin to look at the GSX manual page 26. I guess GSX still looking at Z41 and LHD. I removed those added lines and leave the INI file as it was because there are no difference, GSX doesn't look at the exclusions.
What do you think or what can I try? I don't mind testing for you, it's fun.
Patricio
-
I guess GSX still looking at Z41 and LHD.
And again, that's precisely why I asked if it's really doing that. This should be pretty obvious to spot: when you open the GSX menu, you'll see the airport name right in the title!
-
Sorry too fast, I didn't see this reply. You don't get home until almost 2 weeks ahead? Don't you miss home (lol)?
I'm a truck driver, so if you think that's bad, I'm usually away from home for FIVE weeks, then I go home for five days.
-
I guess GSX still looking at Z41 and LHD.
And again, that's precisely why I asked if it's really doing that. This should be pretty obvious to spot: when you open the GSX menu, you'll see the airport name right in the title!
From the GSX I can see the AFCAD is PANC (AFX_PANC_sim-wings_04.bgl) and nothing else. GSX Menu doesn't show any ICAO or airport name. I think I am not looking at the right spot.
I launched ADE and I can see the Z41 and LHD on the same PANC airport only from Default Stock. I don't see Z41 or LHD in the Aerosoft AFCAD.
Screenshots ...
Patricio
-
Sorry too fast, I didn't see this reply. You don't get home until almost 2 weeks ahead? Don't you miss home (lol)?
I'm a truck driver, so if you think that's bad, I'm usually away from home for FIVE weeks, then I go home for five days.
My Captain Kevin, not bad because is work and a good one. So, you have Cargo Airplane very nice. I am still have PANC issue with FSX and also with P3Dv4. P3Dv5 works just fine. That's rare. Probably adding a line in the Prepar3D.cfg file could resolve it and the same for FSX.cfg files. P3Dv5 is smart (lol).
Patricio
-
From the GSX I can see the AFCAD is PANC (AFX_PANC_sim-wings_04.bgl) and nothing else. GSX Menu doesn't show any ICAO or airport name. I think I am not looking at the right spot. I launched ADE and I can see the Z41 and LHD on the same PANC airport only from Default Stock. I don't see Z41 or LHD in the Aerosoft AFCAD.
So what you reported as a "bug" in GSX that you couldn't exclude Z41, wasn't true. The visibility WORKED, because GSX IS seeing PANC, as clearly indicated in the scenery editor page, which lists PANC as the active airport. So yes, visibility exclusions are working perfectly fine.
So, the problem is that GSX is not seeing any jetways. Which jetways is the scenery using right now ?
If they are made with SODE, a common problem is the developer has used wrong gate names in their SODE.XML file, which is not a problem if you only use SODE, but if you use GSX, the gate name MUST be correct and conform to the SDK standard, otherwise SODE cannot communicate with GSX which jetways is at which gate, see a more detailed explanation here:
http://www.fsdreamteam.com/forum/index.php/topic,23691.msg157932.html#msg157932
-
From the GSX I can see the AFCAD is PANC (AFX_PANC_sim-wings_04.bgl) and nothing else. GSX Menu doesn't show any ICAO or airport name. I think I am not looking at the right spot. I launched ADE and I can see the Z41 and LHD on the same PANC airport only from Default Stock. I don't see Z41 or LHD in the Aerosoft AFCAD.
So what you reported as a "bug" in GSX that you couldn't exclude Z41, wasn't true. The visibility WORKED, because GSX IS seeing PANC, as clearly indicated in the scenery editor page, which lists PANC as the active airport. So yes, visibility exclusions are working perfectly fine.
So, the problem is that GSX is not seeing any jetways. Which jetways is the scenery using right now ?
If they are made with SODE, a common problem is the developer has used wrong gate names in their SODE.XML file, which is not a problem if you only use SODE, but if you use GSX, the gate name MUST be correct and conform to the SDK standard, otherwise SODE cannot communicate with GSX which jetways is at which gate, see a more detailed explanation here:
http://www.fsdreamteam.com/forum/index.php/topic,23691.msg157932.html#msg157932
Umberto, I appreciate you pointed a solution about. I apologize if I called "bug". I thought it was a "bug" because after restarting Couatl or reloading the scenery from another one then the GSX worked.
I will take a look on your provided link and start editing the SODE xml file for good.
I can identify the Gates from the SODE xml file but I don't know the process so, I will learn from that address link.
Many thanks,
Patricio
-
I visited http://www.fsdreamteam.com/forum/index.php?PHPSESSID=6i2chkmpq4836qnhnrt1nso962&/topic,23691.msg157932.html#msg157932
I understood what to look at SODE xml file. How to work with this as an example?
<Stand AfcadICAO="PANC" AfcadGateName="GATE_B" AfcadParkingNumber="6" CustomDesignator="GATE B;6">
<SimObject Name="To Door 1L or 2L">
<Placement Lat="61.17286353" Lon="-149.984447" Alt="0#AGL" Hdg="134.53" />
<Model SimTitle="AJS_320-PANC" StaticSimTitle="AJS_320-PANC-static">
<Jetway InitialState="50;30;50;0" />
</Model>
</SimObject>
</Stand>
When I looked the AFCAD from ADE, the Gate_B is shown as "Gate B" (not underscore line)
What do I need to change now? I want to give a try just with this jetway number 6 for testing before going further.
Patricio
-
I loaded ADE 179 and opened AFCAD PANC and I can highlight the Parking circle then right click to show xml. The info matched with SODE xml. But, still the GSX still "No Jetways Here" message.
-
PANC with P3Dv4.5 fixed SODE files were in backward.
FSX still in question ... not resolved yet.
Patricio
-
Just curious, did you place the line airport_visibility_z41 = 0 in CouatlAddons.INI under the [GSX] header or elsewhere like at the bottom of the file? I have it under [GSX] and it works for me.
-
PANC with P3Dv4.5 fixed SODE files were in backward.
So, again, it wasn't a GSX problem after all. What do you mean with "SODE files were in backward ?"
FSX still in question ... not resolved yet.
No difference between P3D and FSX from a GSX point of view. But the AFCAD files of the scenery can be different so, again, just one of the issues you had in this thread were a GSX problem, the FSX remaining issue is surely not related to GSX as well.
-
Just curious, did you place the line airport_visibility_z41 = 0 in CouatlAddons.INI under the [GSX] header or elsewhere like at the bottom of the file? I have it under [GSX] and it works for me.
Yes, I did and it didn't work ...
Patricio
-
PANC with P3Dv4.5 fixed SODE files were in backward.
So, again, it wasn't a GSX problem after all. What do you mean with "SODE files were in backward ?"
FSX still in question ... not resolved yet.
No difference between P3D and FSX from a GSX point of view. But the AFCAD files of the scenery can be different so, again, just one of the issues you had in this thread were a GSX problem, the FSX remaining issue is surely not related to GSX as well.
SODE-OFF.BAT and SODE-ON.BAT files I had to rename them the "OFF" to "ON" and the other file vice versa to get P3Dv4.5 working GSX as expected.
Yes, AFCAD from FSX and P3Dv4.5 PANC scenery are different.
For right now, I left FSX with the issue as is. Solution so far is to load other scenery first and then to load PANC. Or, to load PANC and to restart Couatl before continuing with the flight plan.
Patricio
-
Yes, I did and it didn't work ...
Why you keep repeating this, after it was obvious from your own screenshot IT DID WORK, and why you keep repeating this, when I clearly explained WHY I said it worked ? I'll repeat it again:
what you reported as a "bug" in GSX that you couldn't exclude Z41, wasn't true. The visibility WORKED, because GSX IS seeing PANC, as clearly indicated in the scenery editor page, which lists PANC as the active airport. So yes, visibility exclusions are working perfectly fine.
So, please, stop saying the GSX visibility "didn't work", because it did. If it really didn't work, GSX menu and the scenery editor would say your are located at Z41! Instead, PANC is listed, which proves the visibility exclusion WORKS.
-
I apologize so sorry about this. I am trying to say "didn't work" I meant the jetways didn't go to dock doors regardless if the exclusion Z41 is added or not in CouatlAddons.INI file. I know GSX identified PANC but still "No Jetways Here".
Patricio
-
I apologize so sorry about this. I am trying to say "didn't work" I meant the jetways didn't go to dock doors regardless if the exclusion Z41 is added or not in CouatlAddons.INI file. I know GSX identified PANC but still "No Jetways Here".
The exclusion is required to let GSX know you are at PANC, so that's working,.
If GSX reports no jetway, as explained already, it's likely because a problem with that scenery XML file, that don't match the gate names in the AFCAD.
-
Umberto, I don't know how to figure the scenery XML not matched gates names in the AFCAD.
-
Umberto, I don't know how to figure the scenery XML not matched gates names in the AFCAD.
I think I already explained it earlier in this thread.
-
Just investigate this, and it works fine on my end. Just to confirm, is your SCENERY up to date. I only ask because in a previous post, you mentioned having to remove these two files:
PANCjetways.BGL
PANCjetwaysteil2.BGL
Looking at my scenery folder, those files don't exist.
-
Just investigate this, and it works fine on my end. Just to confirm, is your SCENERY up to date. I only ask because in a previous post, you mentioned having to remove these two files:
PANCjetways.BGL
PANCjetwaysteil2.BGL
Looking at my scenery folder, those files don't exist.
Hello Captain Kevin, You are looking at your P3D sim instead of FSX? My question is for the FSX sim only. P3D works just fine with jetways.
Patricio
-
Hello Captain Kevin, You are looking at your P3D sim instead of FSX? My question is for the FSX sim only. P3D works just fine with jetways.
Okay, that changes everything. That SODE jetway file you used wasn't even designed for that FSX scenery, which is why you had issues. In fact, I'm not sure if the scenery developer is even the same. I know SimWings did the P3D version, not sure who did the old FSX version.
-
Hello Captain Kevin, You are looking at your P3D sim instead of FSX? My question is for the FSX sim only. P3D works just fine with jetways.
Okay, that changes everything. That SODE jetway file you used wasn't even designed for that FSX scenery, which is why you had issues. In fact, I'm not sure if the scenery developer is even the same. I know SimWings did the P3D version, not sure who did the old FSX version.
I see... well, the jetways in FSX with Aerosoft PANC works but in different way. GSX can see the jetways after a second attempt; restarting Couatl or at Arrival. I can leave it as is.
Maybe I can find something else on the way. Thanks Captain Kevin for sorting this out.
Patricio