I was going to set a custom push back position at KSFO G93, already had the node in an AFCAD loaded in the session, when GSX stops working at all KSFO gates. Error message is approx 'Gate is isolated no ground services available' triggered with Ctrl+Shift+F12. I can still pull up Customize Parking Position and even vary the parking position. The manual does not mention this error message. What is likely cause? I undid my custom push back entries, deleted the appdata\roaming\virtuali\gsx file save for ksfo. Out of ideas.
UPDATE: GSX will respond when I enable the original airport bgl (KSFOHD.bgl), but making a copy of that bgl with ADEv1.75 (beta for P3Dv4) and using that as the airport file results in the isolated parking error. Still looking for ideas here with the KSFO. Yes, already ran a fault finder on the file and fixed a few open nodes but nothing major.
Now that I have determined that KSFOHD.bgl works but a copy of it from ADEv1.75 does not, I have my troubleshooting direction but it would be most helpful to know precisely how GSX determines a gate is isolated. Obviously, the gates I've tried at KSFO are all connected with apron links so what else is involved? Thank you.
UPDATE: Looks like a problem with ADEv1.75 because of the four locations that I have modified the AFCAD with it there is a GSX isolated parking message at all parking locations. I have compared the XML files created by ADEv1.70 and ADEv1.75 and the taxiway parking elements and links look the same and compared to the P3D SDK I don't see a problem. Again, looking for understanding what GSX is looking at when it determines a gate is isolated.
UPDATE: We have ruled out a problem with ADEv1.75, working with Scruffyduck we know that ADEv1.70 uses P3Dv3 bglcomp compiler, which GSX works with. Apparently GSX is not compatible with airports compiled with P3Dv4 bglcomp. There have been changes made to taxi links, aprons and runway objects in the new SDK. So, I jumped the gun in expecting GSX to be P3Dv4 compatible.