Still have problem with gsxL2 when an update is done!!!

[grandfred29]

hello

i am tired to have these problems when you update gsx, i install this update because have this message when i start a scenario so i did it but now, and since the first time i use GSXL2 i have the problem when i request the jetway, she go straight to the right with sode connection lost.

two screens just before and just after request.

i am fed up !

Each time i must uninstall gsx and reinstall it to resolve that, boring!

[grandfred29]

i ve just tried at the same place with the default sode jetway, and in this case there is no problem

[grandfred29]

in the attachment i have put a part of the sode.log, as you can see when the problem occur some red lines appear in the log...

[grandfred29]

So... nothing for help me Umberto?

[virtuali]

It's impossible to help you considering you haven't provided anything about your configuration, for example you haven't said which simulator you use ( the precise, exact version ), to understand if you are using PBR or not.

The SODE error log indicates it cannot find the jetway.cfg file in the FSDT_SODE_JW_JBTC_43_20 folder but, of course, the file is there so, the only possible explanation is your simulator configuration files are being reset by other add-ons to a previous version, one before GSX was installed, so neither GSX nor SODE can find the required Simobjects.

[grandfred29]

i use w10 1903 up to date, the last version from p3dv4.5

the problem exist before gsxl2 bring PBR texture

The problem doesn't exist when i use default sode jetway

It exist when gsxl2 change default jetway by there own in default airport

the problem is like the screenshot under

and no there is no addon who change anything, maybe the update of gsx itself because i don't have any problem with the update 2.6.1, problem restart with 2.6.2

thanks

[virtuali]

i use w10 1903 up to date, the last version from p3dv4.5

Please post your complete SODE log, ZIP it and Attach it to a post.

[grandfred29]

Oh sorry but it s too late for now, just perform a full uninstall/reinstall of my fsdt addon.

Now gsx work well on default airport, can't try my other payware airports because i forgot to save my config before uninstall

So i ll post my sode.log next time i ll have the problem.

thanks

[grandfred29]

good day

problem return since this evening after just checked live update

one file downloaded python27.zip

you asked me the sode log last time, so check the attachment please.

thanks for your help

[grandfred29]

So...can i expect a solution or at least an answer from you Umberto ?

[grandfred29]

no answer today ! like other days

please could you separate adon manager.exe like you did by the past?

The only thing i can do for resolve the problem is uninstall gsx and addon manager but when i do that i need reinstall all my fsdt addon and it is boring because all the .exe aren't on my laptop

Or please fix this jetway problem

thanks

[virtuali]

The problem doesn't have anything to do with the Addon Manager or the Live update or GSX. It seems there's a problem with SODE itself, not reading all the addon folders if some of your addons uses this form:

<Path>.</Path>

to specify a scenery path in the add-on.xml

None of our products uses this syntax, but if you have an add-on that does, it might prevent SODE from reading all simobjects folders, which seems be the problem in your case, since the error relates an object which we surely install.

Do you have any of these add-ons ?

[grandfred29]

Yes i use this méthod for my addons but in this case, i have the problem with FT eham which use cartayna config for the jetway

Now i don t have any problem with gsx if and only if the jetway are animate from sode

[grandfred29]

fortunately for me on my second pc I was able to find a setup file addonmanager.exe 4.0.0.6 which solved my problem until next time ...

Thank you for believing a little more in your users in the future

[virtuali]

fortunately for me on my second pc I was able to find a setup file addonmanager.exe 4.0.0.6 which solved my problem until next time ... Thank you for believing a little more in your users in the future

Nothing in the old Addon Manager could possibly have "fixed" this, since it has downloaded and installed exactly the same files as the new one (they are downloaded from the same server).

Maybe it did some extra cleanup that we do when some wrong Windows compatibility settings are found that would have been done just the same as reinstalling GSX with the latest installer so no, as I've said, the cause of your problem didn't had anything to do with GSX.