Sorry for the spam but SOLVED! You were right in that there was a SODE conflict somehow! Thank you for your work and assistance, sir, a true gentleman.
LOL no problem... Thanks Masterhwak for reminding me of the existance of this always forgotten page for me! Ok I tend to assume, since i have been dealing with this for almost a year now, that most of you know the basics of GSX, and since EGLL was done in the very beginning it has no mention whatsoever of removing the SODE default jetways. Also because at the time of creating that configuration, there were none. I have a radiant new v5 for EGLL ready for publication as soon as the new great update is published for it has been designed with some of the "goodies" of this new future 2.6 version. I will make a note of this in the new instructions. But, lets review the 3 basic rules of installing a configuration:
1. A configuration that is replacing an existing Sode jetways of an airport. You must of course set to .off that .xml instruction that is placed in the C:\ProgramData\12bPilot\SODE\xml folder. In the case of EGLL you have 4 sodes.. turn them all to .off as to make sure none interfere in the GSX jetway configuration. EGLL-LIB.. (2 of them) and EGLL-OBJ (2 of them). setting to .off, means changing the file extensions from .xml to .off.
2. A configuration that is replacing the CTRL-J jetways (this was the actual EGLL before placing the SODE jetways). This configuration comes with some exclusions. You can import mine or simply place my .ini file in the GSX folder and run a "COMPILE" in the GSX Control Panel.
3. A configuration with none of those, this is done by placing my .ini file in the GSX folder and it usually involves touching certaing files that involve fixed jetways. in EGLL, there is also a bit of this, since we remove some fixed jetways that are not operational. you have a note of this in the EGLL instructions.
There is also the fact that certain sceneries have various AFCAD files (the floor plan that sets the taxi ways, the parkings, etc of a scenery) depending usually on a configurator, such as EGLL has.. (It actually has 6 possible AFCADS: Europier or not, and each of those, with 3 runway configurations)... thus I always give you the corresponding .ini file for the runway or other configuration you have chosen for that scenery.
Hope this works for you guys. If you sitll have any problems with EGLL please report it.