Jetways don't move **SOLVED**

[fipsi]

I just noted that in your AFCAD weren't any jetways added to the gates, weird because I have never worked with AFCADs.However, I've put one jetway to a gate and I'm going to test now whether it works or not. If not, I'll do your tip.

[fipsi]

Here, I have your AFCAD, maybe you can fix it.

[virtuali]

I just noted that in your AFCAD weren't any jetways added to the gates, weird because I have never worked with AFCADs.

Sorry, but that's not the case, our AFCAD contains 42 jetways and they all work so, you must have modified it with some utility that somewhat corrupted it.

[virtuali]

Here, I have your AFCAD, maybe you can fix it.

No, that's NOT our AFCAD, yours is 58K in length, the one that comes with Zurich is 39K in length so, you obviously modified it adding some stuff, and lost the jetways in the process for some reasons, maybe not using a native FSX AFCAD editor, or one configured to run in FS9 mode.

The original AFCAD that comes with Zurich is also downloadable from here:

http://www.fsdreamteam.com/download/setup/afd/ZurichX/scenery/APX_LSZH.BGL

This is the place were our installers, including GSX, download it from to be sure it's always updated. If you ran the GSX installer with Zurich installed, and had a different AFCAD, it will create a backup of your existing file, replacing with our version.

So, the only explanation is that, you modified the AFCAD *after* installing GSX, never installed GSX or Zurich again, and so your modified file is still there.

[fipsi]

I have NOT edited any file!


1. Why should I edit an AFCAD, though they're all available on web? And NO, I didn't change/replace any AFCAD or other file, as said above.

2. If I had edited your AFCAD, then I had seen that there aren't any jetways anymore, whether a gate has got a theoretical jetway or not is quite simple indicated and easy to see.

I don't know what your updater downloaded and installed, the only thing I know, it was wrong.

[virtuali]

I have NOT edited any file!

Whether you say you modified or not, fact is is not the file we distribute with Zurich. This is not something that can be argued: the file included in our installer and the online version which the installer downloads are both 39K, your file is 58K, so it's not what we install.

1. Why should I edit an AFCAD, though they're all available on web? And NO, I didn't change/replace any AFCAD or other file, as said above.

But the file is not what we distribute with Zurich so, it might have been corrupted in some way on your system, or replaced by another product, I don't have any idea, the only thing sure, it's not the file we distribute with the Zurich installer.

2. If I had edited your AFCAD, then I had seen that there aren't any jetways anymore, whether a gate has got a theoretical jetway or not is quite simple indicated and easy to see.

You are saying there are no jetways in the AFCAD you posted, I haven't check this, maybe there are, but if they are associated with a different gate number, they WILL appear, but will not move.

I don't know what your updater downloaded and installed, the only thing I know, it was wrong.

Nothing in our updater is "wrong", because if it was everybody would have the same problem.

The download URL is not the only way to get a copy of the AFCAD. There's ANOTHER copy in the installer, which is used in case there's no internet connection available or both servers are down and that copy, if you use Zurich 2.5 or later installer, is identical to the online version, and of course they are both 38K

So, there are no way, even if the servers were down, you would end up with the wrong (58k) file you posted, since both the online and the offline version are the same 39K file.

Which leaves only one option, that the file has been altered on your system.

Whether you did it intentionally or not, or it has been corrupted for any other reason, like a problem with the file system, it's not really relevant, fact is the the scenery doesn't have this problem, all our files are correct (both online and offline) so the issue was never related to Zurich scenery to begin with, but it's something that happened on your system.

[fipsi]

I replaced the AFCAD staying in the Zurich/scenery folder with the one that is downloadable by the link. You were right, the new one just has 38kb in size, that's weird, I mean, you only can possibly the one who had delivered the wrong AFCAD since I haven't touched the files which became installed by your install wizard.

Anyway, it's working stable and correctly again and that's all that counts at the moment.

But still, how can I be the only one customer who had a wrong AFCAD? I bought Zurich together with GSX and since I had the problem, I reinstalled Zurich one or maybe twice. I get your idea that it's basically not possible to get a wrong file by the seller, as first, I'm a single one who reported this issue and secondly, you said that all your files are up to date and all right, which means, not corrupted or anything similiar.

How can that happen, though?

[virtuali]

I replaced the AFCAD staying in the Zurich/scenery folder with the one that is downloadable by the link. You were right, the new one just has 38kb in size, that's weird, I mean, you only can possibly the one who had delivered the wrong AFCAD since I haven't touched the files which became installed by your install wizard.

I've checked the AFCAD and sorry, no, it hasn't been delivered by us, this is sure, and it's easy enough to prove it:

I decompiled it, and it contains the signature of the AFX editing program, which we don't use, since we compile our .BGL with the BGLCOMP that comes with the FSX SDK.

It doesn't have jetways, yet is larger in size, so it's not our file, it's likely a file made starting with our own, with some addition (because it's larger) edited with AFX and saved back, and for some reason it lost jetways, possible it was also edited with a non-FSX editing utility and then re-edited with AFX.

The only possible explanation, other than you edited it, is that you downloaded a file made for our Zurich scenery made by someone else, and forgot about it.

[fipsi]

That would explain why the size is larger, but in this case, unfortunately, I didn't add this file and so I couldn't have forgotten about it.


I'm not a developer, so it's just an assumption, maybe your couatl engine has done some changes by creating mistakes.   

[virtuali]

That would explain why the size is larger, but in this case, unfortunately, I didn't add this file and so I couldn't have forgotten about it.

If you forgot about it, it's obvious you can't say for sure you haven't replaced that file, that's the whole point of the meaning of the word "forgot"...

Either you accept the possibility you did it and forgot about this, or accept the very unlikely (but still theoretically possible) chance that a local file corruption of your file in your system, resulted in an otherwise perfectly legal AFCAD, just with no jetways and with the AFX signature to begin with.

I'm not a developer, so it's just an assumption, maybe your couatl engine has done some changes by creating mistakes.   

That your are not a developer should be reason enough not launch yourself into these assumptions, that have no technical basis whatsoever.

The Couatl engine does NOT modify any AFCAD. First, it doesn't need to, and it couldn't do it even if it wanted, because .BGL can't be rewritten while FSX is running.

Which is why we use an INSTALLER that runs when FSX is not, to install an AFCAD. And as I've said and as you already got proof of (by launching it) the installer correctly gets the ONLY version of the AFCAD we have, which is the 38K one.

You can try running as many times as you wish, it will always get the same 38K version, try if you want.

So, please, just stop continue arguing that 58K file might have come from us, because it's hasn't, and stop saying the "corruption" has been "caused" by any of our products or installers, because it clearly hasn't, and this has been easily proven both by the fact you are the only one with this problem, and by the fact that, when you launched the installer, you got the correct file.

There wasn't any doubt about this, that's the ONLY file you can get from our installer, since we don't have any other version.

The problem has been solved by running the installer, which obviously contained the correct version of our file, so there's no need to continue arguing, which means the topic is closed.