configurator not working

[Romsie]

Hello
since my last update (FlyTampa Vienna) I cannot start the configurator.
I have de- and reinstalled the file and started it as administrator, but nothing happens, no dialogbox, only a blck screen.
What is wrong?

Thanks for your help.
With best regrds
Roman

[martin[flytampa]]

What you mean by "blck screen"? you run the Configurator and nothing pop up or you saying a black or blank screen comes up?
If nothing comes up, look in FlyTampa/scripts/ see if the correct XML files are there, just core folder and config_FT_LOWW.xml if you installed only Vienna.

[metzgergva]

Hello,
I just have set up a new PC with P3DV4.5.
I did all the installations, but when the installer tried to install the configurator it gives me an error message that it cannot be downloaded from the site.
I have in the folder called "scripts" the xml documents for all airports installed. And I have copied back from my p3Dv4.4 version the two files:
FlyTampa_Configurator_Libraries_P3D
FlyTampa-Configurator

But if I click on the later nothing happens???

Any solution available to run the configurations for my airports?

[martin[flytampa]]

Did you run/install this file? https://www.flytampa.org/dwl/FlyTampa_C ... es_P3D.exe

In the folder /FlyTampa/scripts/ is there a "core" subfolder with 2 files in it?

[metzgergva]

Hello Martin,
Yes I have the latest "FlyTampa_Configurator_Libraries_P3D" and "FlyTampa-Configurator" is dated 29/07/2017. There has been no new version downloaded into P3Dv4/FlyTampa folder.

P3Dv4/FlyTampa/scripts I have a core folder with two files called "core.xml" and "global.xml" and I have .xml files for all 14 FlyTampa airports I own.


I also ran the new universal installer and re-installed all the available airports except KaiTak which I do not own. Although at the end of each install it says that it does install configurator and liberies, no change on the date on the "FlyTampa-Configurator" file.

Clicking on the "FlyTampa-Configurator" file does nothing, just will not start.

Thank you for taking care of this.

[martin[flytampa]]

Try this: temporarily move out all airport XML files from the scripts/ folder. except one, for example leave LOWW (and leave the code subfolder as well). See if the configurator works. If it doesn't exchange loww for another airport xml. if it works, quit the configurator and move one or a few xmls back in to see at which point it stops running. The Configurator is very picky with the XML files, any minor typo or wrong formatting in any xml file could have the result of it not running.

[cartayna]

Hello Martin,

There are many of us with this problem. I have a page with many followers that are having the same problem.
It happens only with the sceneries that have the "old system" of installing the sceneries, and not with the new "FlyTampa_Universal_P3D_Setup.exe". In the old ones, when it reaches the end of the installation, it cant find the configurator or libraries to donwload. i here attach a few of the ones i have that ALL have the same problem (add to this captures, one i forgot to make, EKCH).

The only way to download the configurator and libraries "old installer" is to go to this web and download it (we can now, it has been a broken link till yesterday).

Also a few of us that we had to recently reinstall for one reason or another EHAM, the dockings do not show up, no matter what you press on the configurator, they just dont show up.

Cheers and hope this is of use.

All the best
Javier
@ GSX2 Cartayna Files.

[martin[flytampa]]

The old Installer downloading the Configurator/Libraries should be working again now. I did a test install of EHAM and checked the Safegates worked here (leaving the default option "safegate type1 A (FSX/P3D)"

[metzgergva]

Hello Martin,
I have done as you proposed and put in the .xml files one by one back in. At the end it is the config_FT_EHAM.xml which stops the configurator to open up.

[shuband]

I've not had issues with the configurator in 4.5, BUT Amsterdam will not load for me in 4.5. It routinely gets hung up and I have to force quit the sim with the task manager. I'm going back to 4.4 until 4.5 is a bit more stable.

[metzgergva]

Try this: temporarily move out all airport XML files from the scripts/ folder. except one, for example leave LOWW (and leave the code subfolder as well). See if the configurator works. If it doesn't exchange loww for another airport xml. if it works, quit the configurator and move one or a few xmls back in to see at which point it stops running. The Configurator is very picky with the XML files, any minor typo or wrong formatting in any xml file could have the result of it not running.

Hello Martin,
I have done as you said and as in my posting above I could identify the EHAM.xml to be the bad file that blocks it all. What can I do now to get the configuration for EHAM working like all other airports.
BTW: Congratulations on KLAS!

[martin[flytampa]]

Try this: temporarily move out all airport XML files from the scripts/ folder. except one, for example leave LOWW (and leave the code subfolder as well). See if the configurator works. If it doesn't exchange loww for another airport xml. if it works, quit the configurator and move one or a few xmls back in to see at which point it stops running. The Configurator is very picky with the XML files, any minor typo or wrong formatting in any xml file could have the result of it not running.

Hello Martin,
I have done as you said and as in my posting above I could identify the EHAM.xml to be the bad file that blocks it all. What can I do now to get the configuration for EHAM working like all other airports.
BTW: Congratulations on KLAS!

I am not sure. I had a quick look at your attached EHAM xml the other day and didn't see anything wrong with it.

[emilios[flytampa]]

Can you please grab the attached archive, unzip, and drop both 'scripts' and 'images' folders into your "P3D\FlyTampa\" folder and replace all.

[deverette]

I had the same issue above and narrowed it down to the EHAM xml as well. Replacing the xml and images in the above linked archive fixed the problem. Odd as when I compare the original xml and the one in your archive, they're identical.