GSXL2 Isn't functioning properly

[AaronMyers]

Your error seems to indicate something like you switching from parking to parking too fast, or trying to apply multiple changes to lots of jetways without waiting for all of them to be recreated and then changing another setting in the mean times so, the editor was probably confused by all these overlapping commands.

Don't go too fast, especially if you have many jetways to change at the same time.

No other thoughts?

[virtuali]

Try to use a default airplane when customizing the parking.

[AaronMyers]

Try to use a default airplane when customizing the parking.

I just tried the default Maule with the same result. Every time I click the Apply button the following error is logged:

Traceback (most recent call last):
  File ".\GSX\parkingDialog.py", line 1123, in onApply
AttributeError: 'ParkingDialog' object has no attribute 'jetwayName1'

[virtuali]

Are you using an .INI file you were already working on, or are you starting from scratch ?

[AaronMyers]

Are you using an .INI file you were already working on, or are you starting from scratch ?

Totally from scratch. I have been unable to create a single exclude on any third party airport.

[virtuali]

Totally from scratch. I have been unable to create a single exclude on any third party airport.

I assume you have run the Live Update before posting ?

[AaronMyers]

Of course I have. Plus, it has run again in the 2-3 times I've tried uninstalling and reinstalling GSX.

[virtuali]

Ok, try Live Update again now, we made an small update that should fix it.

[AaronMyers]

Ok, try Live Update again now, we made an small update that should fix it.

Well, I am indeed able to click apply now after checking the exclude box. I am able to compile and was able to confirm the jetway disappears at the gate now. Next issue is when I go back into the customize option there is no second tab for the jetway to customize it. When clicking on any of the customize buttons (customize parking, customize jetway, etc) the main window goes away and no customization options pop up. It basically locks up because after that I can no longer call up any window related to GSX.

The log file doesn't have anything after clicking the customize button but it does have the following entries for basically all of my add-on sceneries, I'm not sure if it is related. KDEN from Flightbeam is what I'm testing now, but the same entry exists for all my add-ons.

Code: [Select]

Loading addon KDEN
Addon KDEN not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 79, in loadAddons
  File "<string>", line 37, in importAndCreateInstance
ImportError: No module named KDEN
https://i.imgur.com/HMto1XV.jpg

[flyboy53]

rule number one.. Extension 2 you have to pay for..
Rule number two, you need to register it in addon config in the sim menu

[AaronMyers]

Thanks, but fully paid for, fully registered.

[virtuali]

rule number one.. Extension 2 you have to pay for.. Rule number two, you need to register it in addon config in the sim menu

This is not relevant. If he didn't register GSX Level 2, the user interface would look different.

[virtuali]

The log file doesn't have anything after clicking the customize button but it does have the following entries for basically all of my add-on sceneries, I'm not sure if it is related. KDEN from Flightbeam is what I'm testing now, but the same entry exists for all my add-ons.

That's not an error, it's just an indication KDEN is not installed in Couatl (which is normal if you use the updated version that doesn't use Couatl anymore). To you have something else that might look like an error at the end of the log ?

[AaronMyers]

The log file doesn't have anything after clicking the customize button but it does have the following entries for basically all of my add-on sceneries, I'm not sure if it is related. KDEN from Flightbeam is what I'm testing now, but the same entry exists for all my add-ons.

That's not an error, it's just an indication KDEN is not installed in Couatl (which is normal if you use the updated version that doesn't use Couatl anymore). To you have something else that might look like an error at the end of the log ?

I don't see anything else that stands out. I've attached the full log file for reference.

[virtuali]

I see you use the default Maule, which is unsupported. Try to customize the parking with a supported airplane.